This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 70%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPS%3C/text%3E%3C/svg%3E)
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.
That would be a question for your network and server support teams. It would all depend on the VPN/firewall software and network configuration. They may not want to allow that access due to security reasons.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 97%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGH%3C/text%3E%3C/svg%3E)
Hi,
Thank you for posting your query. According to your description, more details would be grateful.
Please verify your Firewall settings. This will affect the performance.
Hi,
We are looking forward to your reply and ready for help.
So you do not think this is a Remote Desktop Connection configuration and instead must be configured on the VPN server?
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
WARNING: TCP connect to (135... : 3389) failed
WARNING: Ping to 135... failed with status: TimedOut
ComputerName : 135...
RemoteAddress : 135...
RemotePort : 3389
InterfaceAlias : WiFi
SourceAddress : 192.168.0.98
PingSucceeded : False
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded : False
Thanks for your support Moto..
Sorry, can't help you. Your network and security teams likely have the networks locked down to prevent that access. You need to talk to those folks.