lord_moose
07-31-02, 10:21 AM
OK, here's the situation I'm looking at and would appreciate any help you guys have to offer.
Windows 2000 mixed network. I have 2 DHCP servers servering different subnets on different sides of a router. DHCP server (a) has a scope of 192.168.5.1 -> 192.168.6.254. DHCP server (b) has a scopt of 192.168.7.150 -> 192.168.7.220.
Everything works fine, users on subnet (a) can see resources on subnet (b) and vice-versa. The problem is (exclusively) when a user on scope (b) shuts down and moves over to the same side of the router as scope (a). Their computer drops it's lease and leaves the IP at 0.0.0.0 and mask at 0.0.0.0. The lease on server (b) is not released and the client will not pick up a lease from server (a) [who's subnet it is now on].
Usually the computer needs to be rebooted a random number of times and/or remove the NIC. Then it will pick up a lease from scope (a) and everything is happy.... until this happens again.
Any ideas would be totally appreciated.
Thanx all!!
Windows 2000 mixed network. I have 2 DHCP servers servering different subnets on different sides of a router. DHCP server (a) has a scope of 192.168.5.1 -> 192.168.6.254. DHCP server (b) has a scopt of 192.168.7.150 -> 192.168.7.220.
Everything works fine, users on subnet (a) can see resources on subnet (b) and vice-versa. The problem is (exclusively) when a user on scope (b) shuts down and moves over to the same side of the router as scope (a). Their computer drops it's lease and leaves the IP at 0.0.0.0 and mask at 0.0.0.0. The lease on server (b) is not released and the client will not pick up a lease from server (a) [who's subnet it is now on].
Usually the computer needs to be rebooted a random number of times and/or remove the NIC. Then it will pick up a lease from scope (a) and everything is happy.... until this happens again.
Any ideas would be totally appreciated.
Thanx all!!