So you do not think this is a Remote Desktop Connection configuration and instead must be configured on the VPN server?
Remote Desktop Connection VPN - Remote Server
Currently, for our users to access a remote server (135...), from their home office location, users first fire up a VPN connection to the corporate network, which assigns a VPN IP address of 192.... Following this connection, the user then Remote Desktop connects to a computer on the corporate network (192...). Once remote desktop is connected, the user then launches a remote desktop connection to the (135.) computer.
I am looking for a way of shortening this connection to the remote server (135...).
So from the remote home office the user would connect to VPN as normal, but then be able to launch a remote desktop connection directly onto the 135... computer therefore bypassing the need to connect to a PC in the corporate network first.
3 answers
Sort by: Most helpful
-
-
MotoX80 35,706 Reputation points
2021-03-26T16:23:43.387+00:00 Did you try to connect directly to the 135 server? You didn't say what error you are getting. Can you get thru the firewalls and connect to the port?
Open a Powershell window on the client and test connectivity.
Test-NetConnection -ComputerName 135.nnn.nnn.nnn -CommonTCPPort RDP
-
Peter Sheerin 1 Reputation point
2021-03-26T16:33:29.88+00:00 WARNING: TCP connect to (135... : 3389) failed
WARNING: Ping to 135... failed with status: TimedOutComputerName : 135...
RemoteAddress : 135...
RemotePort : 3389
InterfaceAlias : WiFi
SourceAddress : 192.168.0.98
PingSucceeded : False
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded : FalseThanks for your support Moto..