"LRW" <(E-Mail Removed)> quoted and wrote:
> From home I tried that using the public IP (I'll do it to the gateway
> IP from inside the network when I go to work today,) and got the
> following:
>
> PORT STATE SERVICE
> 67/tcp closed dhcpserver
> 67/udp open dhcpserver
>
> Does that mean that the router which is likely the DSU/CSU a previous
> post mentioned (I'll have to investigate the meaning of that on the
> 'net later today,) is acting as a DHCP server? Is what's giving
> internal IP addresses to the machines inside the network?
If that's the public IP, it shouldn't be running a dhcpserver, but the
results merely indicate that the port is open. The -p67,68 option to nmap
will show that it's also got a port open as dhcpclient, so that it's getting
the public IP from your ISP's dhcpserver. To really see what's going on, use
the "-sV" option. See the nmap man page for more information.
> OK this is interesting, although I'm not sure what it means. I'm
> pasting the results below.
> Allow me to babble a moment to see if I'm getting this OK....
> Since the default gateway internal IP has an open DHCP port, and the
> public IP shows the same closed/open tcp/udp, does that mean that the
> piece of hardware the fractional T1 is plugged into is indeed serving
> as router/IP assigner (if that's not a redundant statement. I guess
> not since they're often two different items.)
[ relocated ]
> Interesting ports on 192.168.1.1:
> PORT STATE SERVICE
> 67/tcp closed dhcpserver
> 67/udp open dhcpserver
....
> Host 192.168.1.255 seems to be a subnet broadcast address (returned 1
> extra pings). Still scanning it due to ping response from its own IP.
> Interesting ports on 192.168.1.255:
> PORT STATE SERVICE
> 67/tcp closed dhcpserver
> 67/udp open dhcpserver
The interface 192.168.1.1 is in all likelihood the source of your DHCP
addressing since it's the only host address with a positive response. The
..255 is a broadcast address, so it's the same response (logical OR of all
polled addresses) as the other. The fact that 192.168.1.1 is the only box on
the subnet returning an open port 67 is definitive; that's where your LAN
DHCP addresses are coming from, at least for all machines on the subnet that
are configured as DHCP clients. Again, "-sV" will be helpful.
> Now, all these other machines with visible port 67's, is that good or
> bad? I notice that my own PC is not among them. What does this mean,
> really?
> Interesting ports on SHIPPING (192.168.1.156):
> PORT STATE SERVICE
> 67/tcp closed dhcpserver
> 67/udp closed dhcpserver
It means that nmap polled the port and got no response. You would get the
same "closed" result from any port that nmap polled that had no
client/server process running. As an educational exercise, simply run
"nmap -sV -sSU 192.168.0.0/24" and see the results for each machine. Someday
when you have the time and wish to really start understanding your network,
use the "-p1-65535" to see everything on each machine. You'll probably want
to redirect the output to a file for later review.
In the list of polled IPs, you say that your "own PC is not among them";
does that include 192.168.1.244 for which there is no name resolution?
tony
--
use hotmail for any email replies
-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----