VPN connects but no RDP

[AndrewFram]

I have several users running XP Pro and Vista who have complained about this problem:

We have a windows 2003 server running MS Routing and Remote Access. A user at home will use the MS VPN client and connect successfully. But they will not be able to connect to computers once connecting to the network. Pinging hostname OR IP times out, remote desktop will eventually say "can't connect", and internal websites do not load.

Then they disconnect the VPN connection, reconnect, and then everything works fine. Sometimes they have to disconnect and reconnect two or three times, but without changing any settings, it will suddenly work.

What might cause this?

 

[Grenage]

Does the problem continue if the users try an alternative VPN client, such as 'The Shrew'?

"We can categorically state that we have not released man-eating badgers into the area" - Major Mike Shearer

 

[AndrewFram]

I do not seem to have this problem if I use the Sonicwall VPN client and connect to our sonicwall device.

However, the other users are unwilling to use any other client other than MS.

 

[drummelhart]

make sure wins is running, and configured on the server

 

[AndrewFram]

Turns out a two or three of the IP addresses in the Routing/Remote Acess static pool had been assigned to some other computers.

When a VPN connection was given one of those IP addresses, the conflict prevented it from working. Disconnecting and reconnected issued a new IP, and then it would work.

 

[brianinms]

The address pool for remote vpn users should be different than the internal subnet.