Ok, i'll do my best here to prevent tons of unecessary questions :)
OS: Windows 2003 Server - Standard - R2
IP Address: 10.199.25.14
Scope 1: 10.199.28.0 / 24
Scope 2: 10.199.29.0 / 24
Scope 3: 10.199.30.0 / 24
Scope 4: 10.199.31.0 / 24
Scope 5: 10.199.32.0 / 24
DHCP Server is assigned to VLAN 100
Distribution Switch: Catalyst 4506
VLAN 100 - 10.199.25.0 / 24 - Infrastructure Servers
VLAN 101 - 10.199.28.0 / 24 - Developer
VLAN 102 - 10.199.29.0 / 24 - QA
VLAN 103 - 10.199.30.0 / 24 - Operations
VLAN 104 - 10.199.31.0 / 24 - Tech Support
VLAN 105 - 10.199.32.0 / 24 - General Users
IP Helper Address: 10.199.25.14 (assigned to VLAN's 101-105)
Pretty straightforward ey? VLAN 100 is for all my infrastructure
servers. the remaining VLAN's handle all the users segments. All works
well. Desktops/Laptops get their appropriate IP address based on the
VLAN they are assigned to and the Scope that is associated with a
Now, here is where the problem crops up:
1. Laptop A in VLAN 101 currently has an IP address of 10.199.28.50.
All is well.
2. User has a meeting and takes Laptop A, shutdowns the OS. He walks up
to the 15th floor, plugs into another port that is assigned on VLAN 102
(10.199.29.0 / 24)
3. User boots up Laptop A, and it still get's his old IP address of
10.199.28.50 from VLAN 101.
4. I run an ipconfig /release. I get 0.0.0.0 (expected response)
5. I run an ipconfig /renew and I STILL GET 10.199.28.50 from VLAN 101,
although im plugged into a port that is assigned to VLAN 102
(10.199.29.0 / 24).
How is the Laptop able to get an IP address from a VLAN that is he is
not physically/logically connected? He is connected to VLAN 102
(10.199.29.0 / 24) but get's his old IP address from VLAN 101
(10.199.28.0 / 24). WTF?
The only way to force the laptop to get a valid IP that corresponds to
the current VLAN/subnet it's connected to, is to exclude it's old
address from the DHCP Server and then do an ipconfig /release and
/renew. Only then is it forced to get a new IP address that corresponds
to it's current VLAN/subnet.
It looks like the DHCP requests are somehow spanning or being
broadcasted across multiple VLANs, thus it's getting to the DHCP server
and allowing it to give the laptop it's old IP address, although the
request came from a completely different VLAN/subnet than it's old IP
I have looked EVERYWHERE on the internet for similar issues, and while
I found a few similar posts, the issue always turned out to be
something like the person didn't have IP helper assigned properly or
the DHCP server was having issues, yada yada.
Any help is greatly appreciated as this problem is starting to become
an issue as users tend to move around the office quite frequently.