How to find out what's blocking a Remote Desktop connection

Question

1.00/5 (1 vote)

See more:

I had two workstations set up to allow Remote Desktop connections via specific ports, both from within my lan and from outside. Both were working perfectly. I did a clean re-install of Windows 10 on one of them and now cannot get Remote Desktop to connect from outside. Registry is configured properly, firewall rule is identical to the working workstation, and connections work from within the lan, just not from outside. Any thoughts on how to determine what's blocking the connection?

Posted 5-Nov-15 9:14am

mlowry

Add a Solution

Comments

Suvendu Shekhar Giri 5-Nov-15 15:34pm

Check this, if it helps-
RDC not connecting outside network [^]

Sergey Kizyan 6-Nov-15 14:42pm

Can you ping computer from external network? Is it visible?

mlowry 6-Nov-15 16:12pm

Thanks for the reference to the outside port scanning tool. It confirms no response on the specified port, and good response on the working system. Firewall is configured with port open. Netstat -a confirms port is listening, but for some reason the outside world isn't being responded to.

2 solutions

Solution 1

Windows have different rules depending on the origin of the incoming request.
Every service that listen to the network have a setting for your private/secure network and another one for public/insecure network.
You have to check the firewall and router too.

Posted 5-Nov-15 9:53am

Patrice T

Updated 5-Nov-15 10:53am

v2

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

mlowry · Accepted Answer · 2015-11-06T11:19:00

Solution 3

The solution was simple (stupid): when I reinstalled I neglected to re-establish the fixed IP address, so the port forwarding in the router no longer could connect to my machine from outside. When I set the correct IP address, everything works fine.

Posted 6-Nov-15 11:19am

mlowry