Discussion Locked

Windows 98 & 2000 PC's cannot find DHCP

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have been experiencing problems which seem only to relte to our Win 98 & 2000 PC's. They will be working fine, and then will not be able to log onto the network. When logging on a message appears saying "No Domain ontroller could be found". When I assign a static address for them they log on fine. Any help would be appreciated.

13 replies

by bryan bowers

You should make an entry for your WINS server on the DHCP server. Also, does the machine have an valid TCP/IP address or is it blank?

by 4runner

In DHCP Manager look at your WINS/NBT Node type. If it is set to Hybrid (0x8) go ahead and change it to Mixed (0x4). Another thing to check is the broadcast routine on the switch/hub. Also ensure that Port Fast is enabled on the ports the clients are plugged into. Also isolating W2K and W98 clients by putting them on their own segment would be the last resort. Good Luck

by guy

I would check the clients by running IPCONFIG on W2K or winipcfg on 98. My point are they getting an autonet automatic IP address ? 169.254.x.y.? If so perhaps set the DHCP leases to about 8 days rather than the default of 3 days.

by todd

I had a similiar issue, that drove me nuts. Apparently what had happened, in my case, was a surge had altered the settings inside of one of my routers and enabled DHCP. I had DHCP running on an NT box also, and what had happened, was occasionally, Iwould get an off the wall IP address assigned to some of the work-stations.
If the workstation found the router as the DHCP server, it would get an odd IP, if it found the NT server, it would work fine.
Look to see if IP's are assigned, if so, check and see what the IP of the DHCP server it used is the correct one. If not, then you may have another device on the network acting as a DHCP. Disable DHCP in this device.

by tony

If you recently installed Active Directory on a Win2000 server, you have to go into AD and authorize the dhcp or it will be shut down by AD.

by jrm

I had the same problem and it was because a Linux machine running Samba had started DHCP service "vuluntarily".

So when NT server was busy, Linux machine gave a promptest leasing offer so in a few hours the whole segment stopped working.

Solution: we decide to divide the IP segment between NT and Linux machines so to give the NT server some relief (if you cannot against Linux...)

Maybe you have more than one machine acting as a DHCP server. Just pause your NT DHCP service and thenipconfig /release, ipconfig/renew and ipconfig/all, from your NT client PC (or winipcfg from w9x). You will see offending DHCP server IP, then nbtstat -A [the.bad.guy.IP] and go and hunt it!

Regards,

Julio

This discussion is closed to new replies.