'nmap -sU -p 67 192.168.1.*' produces the following results.
Starting nmap V. 3.10ALPHA4 ( www.insecure.org/nmap/ )
Nmap run completed -- 256 IP addresses (0 hosts up) scanned in 46.453
seconds
'nmap -sU -p 67 10.0.0.*' produces the following results:
Starting nmap V. 3.10ALPHA4 (
Lewis [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: HELP! dhcp server not talking to clients
I have dhcp set up on my linux box to serve a Win2000 box, a Win98 box,
a WinXP box, and networked HP LJ1200. It works fine, until I try to
upgrade the kernel from 2.4.18 to 2.4.20 (from
Doh! I bet this is the problem. I have a linksys router/switch that I
bet is the culprit. Don't know why I didn't think of it before. I can't
think of how to fix it until I get home, though. The weird thing is that
this has only been a problem when my linux box went down with kernel
problems.
On Tue, Dec 17, 2002 at 06:00:36PM -0600, Charles Lewis wrote:
Doh! I bet this is the problem. I have a linksys router/switch that I
bet is the culprit. Don't know why I didn't think of it before. I can't
think of how to fix it until I get home, though. The weird thing is that
this has only
I have dhcp set up on my linux box to serve a Win2000 box, a Win98 box,
a WinXP box, and networked HP LJ1200. It works fine, until I try to
upgrade the kernel from 2.4.18 to 2.4.20 (from an earlier thread). The
machine locks up after a few minutes, so I go back to 2.4.18, and all my
machines
hey charles, are you sure another machine isn't running a dhcpd? i
sure don't see 192 addresses in your config... try installing nmap
and then doing
# nmap -sU -p 67 host
for all the suspect hosts.
hth
sean
On Mon, Dec 16, 2002 at 11:53:00PM -0600, Charles Lewis wrote:
I have dhcp
sean finney [EMAIL PROTECTED] writes:
hey charles, are you sure another machine isn't running a dhcpd? i
sure don't see 192 addresses in your config... try installing nmap
and then doing
# nmap -sU -p 67 host
for all the suspect hosts. =20
IIRC, the 192.168.1.0/24 network is what
7 matches
Mail list logo
