Question Locked

DCHP Win2003 - VLANs - Wrong IP-Adresses

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

Hi @ll...

Hope, somebody can help me.

I've an Cisco network with about 10 VLANs.

VLAN 2 = Server inluding 1 DHCP Server on Windows 2003 with 2 IP ranges for VLAN 6 and 7
VLAN 6 = XP clients group 1 (172.16.4.0/24)
VLAN 7 = XP clients group 2 (172.16.2.0/24)

our Cisco Router (3750G) is configured with ip helper address.

Every client in VLAN 6 and 7 is getting the correct IP from the IP range for his VLAN.
BUT if we take a notebook from VLAN 6 to 7 or from 7 to 6 the notebook is getting or keeping the old IP address.

e.g.
Notebook 1 is in VLAN 6 and released a IP from the DHCP - 172.16.4.50
-- I take the notebook and plug it into a VLAN 7 port the client tries to get an IP address from the DHCP server. After one minute the client says that he's got an IP but he's got again 172.16.4.50 not the needed 172.16.2.xx to be able to work in this subnet.

What's wrong here - everything working well except clients changing VLANs.

I can't point where the problem is. Is it at the client, the Cisco router or the DHCP server. Hope for help... ;-)

best regards,

Reinhard

3 replies

by eurojames

1) (less recommended) - reducing lease time on address?
2) prohibiting UDL helper traffic *between* vLAN 6 & 7. Perhaps the DHCP server request is originating from the wrong subnet..

by spam

I've no traffic between 6&7

I checked all DHCP request between the client via router to the DHCP server.

When the lease has expired or the client tries the first time to get an IP address from the DCHP server everything looks great (every packet is correct - discover, offer, request and acknowledge).
When I change the VLAN and monitor the requests there are some strange effects.
First of all there are no discover or offer packets. First the client requests his old IP from the other VLAN 3 times over 14 seconds. then the client starts a discover packet BUT with a request option in the packet for the same IP address (option 50). then the clients gets an offer packet with the WRONG old IP address and a wrong old router (option 3)! The rest are standard request and acknowledge packets with the wrong IP and Gateway.
The same action I encountered on the DHCP server with the packets from the relaying router.

Is the DHCP not recognizing that the request comes from another relaying IP? The DHCP handles the request from 172.16.4.1 as it is originated from 172.16.2.1. The both scopes are in one superscope but I think this can't be the problem because "fresh" clients are handled correctly...

Best regards,

Reinhard

This discussion is closed to new replies.