Discussion Locked

Unexpected network failure

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have migrated from NT to 2000 and one of my win2000 prof. machines cannot log in. I have two DHCP servers running. I could see the msc2000 machine in servera's DHCP address lease but it is not in serverb DHCP address lease. When I try to add a reserve on either dhcp it says the IP address is already in use. I'm trying to use the same ip address that shows up in servera. A ipconfig in msc2000 shows no ip. I did a ipconfig /release and then tryed a ipconfig /renew and I get "Unexpected networkfailure or insufficient access". I then did a refreash on both address lease DHCP and now I cannot see msc2000 at all. When I ping msc2000 from a servera or serverb I get a "msc2000.domain.ksninc.pvt [192.168.1.118]" req. timeout
Any suggestions would be greatly appricated

4 replies

by timwalsh

First things first:

1. You cannot have 2 DHCP servers with the same scope. You have the potential of both servers issuing the same IP address to different computers.
2. You didn't see the lease info on serverb because server b didn't issue the lease.
3. If you are looking for fault-tolerance (second DHCP server in case the first fails), DHCP doesn't work the same way DNS does (both servers having copies of the same database. To have 2 DHCP servers operate correctly, you must split your scope (servera scope: 192.168.1.1 - 192.168.1.127; serverb scope: 192.168.1.128 - 192.168.1.254). The scope on each DHCP server must be large enough to handle all clients that might request a DHCP lease.
4. You cannot set up and IP address reservation using an IP address that is part of the scope (DHCP will enable the reservation, but it will also have the address available for normal lease also.
5. Fix you scopes and then try the release/renew cycle.

by jsarinana

Thanks for your help, my DHCP was broken using the migration tool did not work, I had to create it from cut and paste.

This discussion is closed to new replies.