Double check the config of the VLANs. They may not be made clearly
distinctive and there becomes "bluring" as to which subnet is on the
particular wire. This can cause the Client or the DHCP Server (or both) to
become confused as to just which subnet they are actually dealing with.
It is usually best if the DHCP Server has only one Nic, only one IP#, and
sits cleanly on only one segment (no frame tagging on that wire).
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
The views expressed are my own (as annoying as they are), and not those of
my employer or anyone else associated with me.
-----------------------------------------------------
"jason" <(E-Mail Removed)> wrote in message
news:47CFEF92-5B61-4EF6-833A-(E-Mail Removed)...
> I've got a 2003 server running DHCP on our server farm vlan and have
> iphelper
> configured in the switch for the clients to find it. When I install a
> client
> for the first time on one of our 14 subnets, the client finds the dhcp
> server, gets an address and everything is fine.
>
> If I take one of those clients to another vlan, it will not release the
> old
> address even after forcing it with ipconfig /release , /renew. if I give
> that
> same client a static for the new vlan it works fine. Interestingly
> enough,
> if I come back after its had the static for a day or so and do a
> release/renew, it grabs a new address from the subnet just fine.
>
> I've checked my dhcp config over and over and have no idea what's causing
> this.
> Anyone have any ideas?
>
Similar Threads
Linear Mode
