HacksNTweaks
MIS
OK, here's the scenario:
W2K server running DHCP server and dynamic DNS (no WINS). There are 4 scopes within a superscope set up as follows:
10.2.x.x/16 (10.2.1.1 - 10.2.2.254)
10.3.x.x/16 (10.3.1.1 - 10.3.2.254)
10.4.x.x/16 (you get the idea!)
10.5.x.x/16 ("" ""
The subnets are "routed" using a Cisco layer 3 switch using IP helper address on each appropriate interface.
The clients are either W2K or XP. They pick up appropriate IP configuration information on their respective subnets and all is fine and dandy. Pretty straight forward stuff, but...
The problem:
A good number of users (laptops) must move between subnets. What's happening is that they retain their previous dynamic IP information. I've tried having them do a release before shutdown to no avail. The only thing that works is to delete the DHCP lease entry for that IP address in the scope. Then, they can pick up an address for the correct subnet. This has also happened with a DHCP configured Intel print server (don't ask the obvious question here. It has to do with the previous admin!).
Is there some setting I'm missing here, folks!?
Any help is truly appreciated!
HacksNTweaks
W2K server running DHCP server and dynamic DNS (no WINS). There are 4 scopes within a superscope set up as follows:
10.2.x.x/16 (10.2.1.1 - 10.2.2.254)
10.3.x.x/16 (10.3.1.1 - 10.3.2.254)
10.4.x.x/16 (you get the idea!)
10.5.x.x/16 ("" ""
The subnets are "routed" using a Cisco layer 3 switch using IP helper address on each appropriate interface.
The clients are either W2K or XP. They pick up appropriate IP configuration information on their respective subnets and all is fine and dandy. Pretty straight forward stuff, but...
The problem:
A good number of users (laptops) must move between subnets. What's happening is that they retain their previous dynamic IP information. I've tried having them do a release before shutdown to no avail. The only thing that works is to delete the DHCP lease entry for that IP address in the scope. Then, they can pick up an address for the correct subnet. This has also happened with a DHCP configured Intel print server (don't ask the obvious question here. It has to do with the previous admin!).
Is there some setting I'm missing here, folks!?
Any help is truly appreciated!
HacksNTweaks