Re: DHCP Client roaming issues
From: Erik Tamminga (anonymous_at_discussions.microsoft.com)
Date: 06/05/04
- Previous message: Keppy: "Re: Problem with 1 of 4 computers using MN-500 Router"
- In reply to: Phillip Windell: "Re: DHCP Client roaming issues"
- Next in thread: Phillip Windell: "Re: DHCP Client roaming issues"
- Reply: Phillip Windell: "Re: DHCP Client roaming issues"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 4 Jun 2004 23:56:02 -0700
Hi,
A "release/renew after it is moved" doesn't work. The renew process takes longer and the host presents it's old ip address.
The only way we got things working after the move is to:
- manually remove the lease from old scope in the w2k3 dhcp server and create a reservation in the new scope.
- The host get's his new assigned address.
- Remove the reservation so the host get's a dynamic assigned address from that scope.
Additional info: server is a Windows 2003 standard server and clients are windows 2000 professional. All networks are connected via the same cisco 3550-emi network and all client vlan-interfaces use ip helper-addresses to forward the requests to the dhcp server.
Regards,
Erik
----- Phillip Windell wrote: -----
It won't get a new address until the least expires. I believe the default is
8 days unless you change it. Since the client checks with the DHCP Server
at 50% of the lease period, it won't get a new address for 4 days.
The problem is that you aren't supposed to unplug a machine and move it to a
different subnet without turning it off. So either turn it off or do a
"Release/Renew" after it is moved.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"Erik Tamminga" <anonymous@discussions.microsoft.com> wrote in message
news:36BE61EF-F60A-4AD8-A7E8-761D9A98A2A5@microsoft.com...
> Hi,
>> We've setup a new network with three vlans. The first vlan contains
> all of our servers, the second and third vlans contain our two
> different usergroups.
>> When user A connects to the second vlan he gets an (correct)
> ip-address from our dhcp server in the server vlan. (our routers have
> setup ip helper-addresses).
> When user B connects to the third vlan he also gets an (correct)
> ip-address from our dhcp server in the server vlan.
>> Now when user A moves his machine (without turning it off, just
> disconnecting and reconnecting the cable) from vlan two to vlan three,
> he doesn't get a new ip-address and continues to use the old address.
> We do not see the machine requesting a new address via the standard
> discover-offer-request-ack dhcp sequence.
>> When user A releases his address prior to moving the machine
> everything works fine. Releasing the address once connected to the new
> network does NOT resolve the problem.
>> Any hints on how to solve this?
>> Regards,
>> Erik
>
- Previous message: Keppy: "Re: Problem with 1 of 4 computers using MN-500 Router"
- In reply to: Phillip Windell: "Re: DHCP Client roaming issues"
- Next in thread: Phillip Windell: "Re: DHCP Client roaming issues"
- Reply: Phillip Windell: "Re: DHCP Client roaming issues"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|