What are the issues with VPN and
> Remote Desktop?
Not finding the machine you're trying to connect to due to DNS not resolving the name to IP.
Mike
- posted
16 years ago
Re: mstsc
Loading thread data ...
- Vote on answer
- posted
16 years ago
Suppose I provide the IP and the port?
- Vote on answer
- posted
16 years ago
The port is not important, but the IP is. Either supply the IP (and as the IP changes) or keep DNS through the vpn active and correct.
Mike
- Vote on answer
- posted
16 years ago
I know the IP and it stays put, but I'm trying to access it via a VPN created through SonicWall.
- Vote on answer
- posted
16 years ago
My users have no issues connecting to RDP using mstsc across VPN. Are you able to connect to that box on your internal network without VPN? Is RDP enabled on that box?
Mike
- Vote on answer
- posted
16 years ago
Mike wrote: ...
That network has only the server and the system I'm trying to get to. I may have to take a laptop over and connect in order to address your question about connecting without VPN.
I did enable Remote Desktop service (to the best of my so-called ability) but I can't remember if I rebooted !8-) Is there a protocol/service/client that must be installed in the Local Area Connector? (running Windows XP sp2 on both ends). I will double check those settings.
- Vote on answer
- posted
16 years ago
You can check that RDP is active from another box by telnet'ing to the windows box port 3389 (telnet $HOST 3389).
Mike
- Vote on answer
- posted
16 years ago
Neat trick!
Sadly, C:\\>telnet 192.168.248.207 3389 Connecting To 192.168.248.207...Could not open connection to the host, on port 3
389: Connect failedanswers to a ping however.