0

I want to connect from home to office Windows Server using the Remote Desktop Connection (Microsoft) client. The server's RDP port is non standard one - my admin claims that opening a standard port of 3389 is insecure.

  1. When I connect my laptop to the network using my cellphone it works like charm - I connect successfully and it works.

  2. At home I have landline with public, static IP plus ASUS Wireless Router. Unfortunately bdzionk - each time I get timeout.

I am trying to pinpoint the problem and tried to connect to a friends workstation using standard port of 3389 and I was able to connect.

Apparently my home router or a network provider do block RDP connections on non-standard ports (other services work as expected).

How to better diagnose and solve the problem? How to determine whether there is a problem with Asus router or my network provider?

4
  • Enable upnp on your router to see if this changes anything. Also try port forwarding the relevant ports.
    – NiallUK
    Commented Mar 26, 2020 at 14:38
  • Does port forwarding has anything to do with connecting as client? I do not have anything in router logs. UPnP and port forwarding would be relevant if I would be setting up a server. Any relevance to client connection? Commented Mar 26, 2020 at 14:46
  • @PawelDebski - Port Forwarding is only required to open incoming traffic on a port to a specific machine on your network.
    – Ramhound
    Commented Mar 26, 2020 at 17:51
  • That's exactly what I thought. Still seeking solution. Commented Mar 26, 2020 at 17:56

0

You must log in to answer this question.

Browse other questions tagged .