Link to home
Create AccountLog in
Avatar of SBSWIZARD
SBSWIZARDFlag for United States of America

asked on

Cannot RDP through VPN

I have users that use RDP through a VPN connection to remote into their work machines from home and are now getting a "this computer can't connect to the remote computer" error. I've got no problems with RDP on the local network, it only seems to be happening with the VPN.
Avatar of ded9
ded9
Flag of India image

Make sure that the account you are using to connect to the remote computer is a member of the local administrators group or in the Remote Desktops Users group on the remote computer.


Ref
http://bit.ly/1abfANo




Ded9
ASKER CERTIFIED SOLUTION
Avatar of Qlemo
Qlemo
Flag of Germany image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
Avatar of SBSWIZARD

ASKER

TraceRt command is timing out after hitting the server's VPN interface. Windows Firewall is disabled. User's home network and the office network have different subnets. Using built in Windows VPN client. I am able to RDP to the server hosting the VPN connection using its hostname. Trying to connect to his office workstation gives a "could not find computer" error using its hostname and "can't connect" error using its IP address. Even stranger I was able to connect once today.
The hostname issue isn't surprising. Setting up proper name resolution with Split DNS or the like is a very advanced topic ;-).

So you are using the Windows PPTP VPN, and I suppose the connection gets an IP address of the office LAN. Is the (R)RAS server set up to allow access to the local network? (Depending on the OS, it is located at different dialogs).
I believe it is. The server is running Windows Server 2008 R2. How would I verify?
For local LAN access, see http://technet.microsoft.com/en-us/library/dd458983.aspx, point 8 .
Also check the IP pool of RRAS, and whether NAT is used (http://technet.microsoft.com/en-us/library/dd458971.aspx).
Issue has been resolved by restarting the Routing and Remove Access services on the server hosting the VPN connection. Thanks everyone for you help.
I've requested that this question be closed as follows:

Accepted answer: 0 points for SBSWIZARD's comment #a39349217

for the following reason:

ok