RRAS & DHCP: Why Does Router Remember Old MAC Address?

[Guest]

I have a RRAS server set up to let DHCP provide addresses for incalling clients. But the default router remembers the MAC address of the previous owner of the newly-assigned address.

Result: I dial up, try to ping things on a different subnet, and the target device replies go to the wrong MAC address. The packet thus never reaches my RRAS server (or the client).

What's up? Shouldn't RRAS nudge the default router when a call comes in (or perhaps when it first runs and fetches the DHCP address block), and advertise that there's a new owner for that IP address?

 

[Kadirvel C Vanniarajan [MSFT]]

Check the arp cache on the router to see if there is a mapping for the IP
address to the MAC address of the earlier owner. If so, delete the same.
arp -a can be used to display the arp cache. Better yet, have IP address
reservation at the DHCP for the clients connecting in and configure static
IP pool with the RRAS server. This way, there won't be conflict between the
ip address assigned to the machines on the LAN and the remote clients.

--
Kadir

(e-mail address removed) [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

I have a RRAS server set up to let DHCP provide addresses for incalling

clients. But the default router remembers the MAC address of the previous
owner of the newly-assigned address.

Result: I dial up, try to ping things on a different subnet, and the

target device replies go to the wrong MAC address. The packet thus never
reaches my RRAS server (or the client).

What's up? Shouldn't RRAS nudge the default router when a call comes in

(or perhaps when it first runs and fetches the DHCP address block), and
advertise that there's a new owner for that IP address?