similar to: nmap not scanning networks?

Hi all, I had nForce3 motherboard that has broken. Than I bought nForce4 motherboard. I connected old hard disk to this new nForce4 motherboard. For net and sound support I download drivers from nvidia.com site. This driver asks kernel source to be on local disk and gcc compiler. After I installed kernel source and gcc, driver is successfully installed. >From that point (but maybe it is

> From: Zoran Kolic <kolicz@eunet.yu> > Subject: about nmap > To: freebsd-security@freebsd.org > Message-ID: <20040808053526.GA652@kolic.net> > Content-Type: text/plain; charset=us-ascii > > Dear all! > Last evening I've noticed that > my 5.2 box had strange result > about nmap search. One port is > randomly open when I look from > user account.

Dear All Please be informed that I have installed CentOS 5.2 on my client but it does not have nmap command . Can you please do me favor and let me know what is the equivalent of nmap command on CentOS 5.2 ? Thank you in advance -------------- next part -------------- An HTML attachment was scrubbed... URL:

In CentOS 4 does anyone know the switches to get NMAP to reveal the MAC of the host being scanned ? I cant seem to find it and i am using nmap-4.20 - i am sure this was available somehow on older releases. thanks

Hey Y'all, I just set up a new old machine on my network. I did a net install of CentOS 6.7 on it replacing an outdated copy of Win XP. Of course I'm now in the throws of configuring the machine to be a useful member of society. [mlapier at peach ~]$ nmap -sn 192.168.15.0/24 Starting Nmap 5.51 ( http://nmap.org ) at 2015-08-23 20:12 EDT Nmap scan report for 192.168.15.1 Host is up

Dear All Can you please do me favor and let me know how can I solve my problem with nmap , as described below : "My CentOS server can ping the network element , but when I try to scan its open ports to see which ones are open at now the nmap cannot distinguish them and returned as they are being filtered : #nmap -sS -p 20-80 172.18.0.1 Can you please let me know how can I modify my nmap

Exhausted mirrors and had the following errors. (2/10): nmap-frontend-4.0 100% |=========================| 29 kB 00:00 http://apt.sw.be/redhat/el4/en/i386/dag/RPMS/nmap- frontend-4.01-1.2.el4.rf.i386.rpm: [Errno -1] Package does not match checksum Trying other mirror. (3/10): libpng-devel-1.2. 100% |=========================| 169 kB 00:00 (4/10): nmap-4.01-1.2.el4 100%

I have a CentOS 4.2 machine. lokkit shows that a firewall is enabled, and it is customized to allow SSH, Web, and DNS traffic only. But if I run nmap against the server IP (from my home machine, outside the local network) it shows over 1000 open ports. Am I not understanding nmap, or is there something seriously wrong here? Here is a small snip of the nmap output (I can include it all if

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As you all may know Fyodor of nmap fame has terminated SCO's rights to distribute namp with its products. See: http://www.smh.com.au/articles/2004/02/27/1077676955381.html I know this is off-topic, but I am interested in opinions on the subject of SCO using Samba in it's products while they declare the GPL is unconstitutional and invalid.

Dear all! Last evening I've noticed that my 5.2 box had strange result about nmap search. One port is randomly open when I look from user account. From root everything looks as expected. The comp is most time out of internet. The last thing was adding "expect" package. I am not paniced, could be hiting... Or something in "expect" package... It is random port from 53000 to

I guess this is an FYI Running NMAP (protocol detection, common ports) against my UIP200's causes them to reboot. firmware BS4.56. Be careful where you point that thing. -Nate

Greetings, I am running into *possible* Samba/Firewall issues. Our Samba v3.0.11 server is also running iptables. In our log.nmbd file we have noticed the following: [2005/09/27 15:43:41, 1] libsmb/cliconnect.c:cli_connect(1313) Error connecting to 130.xx.xx.xx (Connection refused) [2005/09/27 15:50:21, 0] libsmb/nmblib.c:send_udp(790) Packet send failed to 130.xx.xx.xx(138) ERRNO=Operation

I made the following adjustments to /etc/shorewall/common.def (1.3.13 with all relevant patches). ############################################################################ # Shorewall 1.3 -- /etc/shorewall/common.def # # This file defines the rules that are applied before a policy of # DROP or REJECT is applied. In addition to the rules defined in this file, # the firewall will also define a

Hello! Does dovecot support i18n'd search? Alex.

Hello Daniel, At the moment we are preparing the patch for disassembling microMIPS 16 bit instructions and it will be on Phabricator tomorrow or on Wednesday. Functionality is implemented in MipsDisassembler::getInstruction where first two bytes are read and decodeInstruction is called with DecoderTableMicroMips16 and only if it fails we read 4 bytes and call decodeInstruction with

Here are my preliminary tests: 5.2.18 is vulnerable (stock Redhat 3.0.3) 5.3.12 does not appear vulnerable (stock Redhat 4.0, I think) Dave G. <daveg@escape.com> http://www.escape.com/~daveg

Full_Name: Zoran Bosnic Version: 2.4.0 OS: Windows XP SP2 Submission from: (NULL) (212.235.140.146) This is a problem that occurs in R GUI Script Editor and is connected to Windows regional settings. Since I live in Slovenia, my computer has a keyboard with additional slovenian international characters. I am therefore using Windows XP SP2 with Input Language (=Keyboard Locale, Control

I'm quite happy to see 9.1 out and want to ask polite and benevolent question: regarding times on the site, are iso and img files the same as 2 weeks ago? To remind noble readers. I installed on my computers what was release at that time and got it up and working perfectly. In other words, is it the same file? Best regards and happy new year Zoran

This patch adds the seatbelts which _only_ kill parent sshd procs... -RMallory (eg: when you ssh into a machine and pkgadd the new openssh, it will not kill your current (or anyone else's sshd session) onanother_note: the buildpkg.sh could use some exec_prefix functionality... to deal with ./configure --prefix= --exec_prefix=/usr *** bak/opensshd.in Fri Oct 19 13:36:24 2001 ---

It might sound stupid, but I'd like to know if there's any difference. Are those 3 line the same? WITH_KMS=YES WITH_KMS="YES" WITH_KMS=yes Best regards Zoran