VPN clients getting the same IP address as internal machines

[Newbie]

We have a problem with our W2000 RAS server. Our Linksys router is our DHCP
server and we've got some machines with static IP addresses. VPN clients
connecting to the W2000 RAS server occasionally get assigned the same IP
address as one of the internal static IP machines. This means that the RAS
server machine thinks that packets destined for an internal machine get
routed to the VPN client. I think this is why I can't ping the RAS server
from the internal machine with the duplicate IP.

I've set up a DHCP relay on the RAS server, so I'd have thought that the VPN
clients would get their IP from the Linksys router also.

Is there any way to partition the IP address space that the RAS server uses
otherwise, to avoid collisions with the internal machines (192.168.1.*).

Ta,
JF

 

[Newbie]

I think I've answered my own question. The RAS server wasn't configured to
use DHCP to assign IP addresses. It was configured to use a static pool that
conflicted with our internal static IP addresses. Switching this over to
DHCP seems to be assigning VPN clients IP addresses from our DHCP range.

 

[Robert L [MS-MVP]]

Thank you for sharing your experience with us.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
I think I've answered my own question. The RAS server wasn't configured to
use DHCP to assign IP addresses. It was configured to use a static pool that
conflicted with our internal static IP addresses. Switching this over to
DHCP seems to be assigning VPN clients IP addresses from our DHCP range.

 

[Newbie]

Hmm, there's still something not quite right though.

The first machine to connect this morning got 192.168.1.115, then I
connected and got 192.168.1.117, which looks OK as these are from the (>100)
DHCP pool.

However, the RAS server itself has 192.168.1.115 associated with it's PPP
adapter, so the machine attached via the VPN first as 192.168.1.115 can't
see anything on the internal network. I guess because the RAS server isn't
passing replies back to it?

JF

Thank you for sharing your experience with us.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
I think I've answered my own question. The RAS server wasn't configured to
use DHCP to assign IP addresses. It was configured to use a static pool that
conflicted with our internal static IP addresses. Switching this over to
DHCP seems to be assigning VPN clients IP addresses from our DHCP range.