DHCP server and Windows client

[vnrusso]

Hello all.

Having read the DHCP Mini How-To and several web pages, I still can't figure this out. I have 3 machines on my hub right now: a 486 with Slackware 7.1, a P166 with Windows 98, and an Athlon 800 that dual boots Slackware 7.1 and WIndows 98 (for games). I wanted to be able to let laptops, friend's machines, etc. plug into the hub and be automagically network ready, so I'm abandoning static IP's and setting up the 486 as a DHCP server.

For some reason, though, the Windows box (the 166; I haven't tried the dual boot machine yet) gets the wrong IP address-- instead of getting 192.168.0.x with a subnet mask of 255.255.255.0, it gets 169.254.x.x with a subnet mask of 255.255.0.0

Does this sound like an error with the server or with the client? I've gone over my dhcpd.conf file about a hundred times and it looks good (I'm posting from a different machine or I'd attach it), and I don't think I need to change anything on the Windows box aside from "get an IP automatically."

Thanks in advance,

--VNR

[skweegie]

hiyas,

its most likely a problem with your server. you get the 169.254.x.x when you can't connect to or find a DHCP server so you get the default private IP# of 169.254.x.x.

you did give the DHCP sever its own static ip#, right? did you also try renewing the lease on the win box (this will most likely fail but worth a try)...

[This message has been edited by skweegie (edited 29 November 2000).]

[vnrusso]

Thanks a bunch; I didn't realize those were private IP's. After a lot of troubleshooting, I found that the problem was a not-quite-connected RJ-45 cable (had I not happened to glance up and see the light on the back of the machine blink orange when packets were sent, I _NEVER_ would have figured this one out...).

Thanks again,

--VNR