13 replies
by bryan bowers
by numbies
by 4runner
by numbies
by guy
by numbies
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 numbies
by tony
by numbies
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
by numbies
by numbies
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending