Seemingly out of the blue I've found myself no longer able to RDP to a particular system [either externally or over the local network] unless I completely disable the Windows/Defender Firewall.
Previously, the Firewall was enabled with "Remote Desktop" as an 'Allowed App' through the Firewall. I'm not sure if a Windows Update changed this functionality.
I haven't found anything online that speaks to this -- it all talks about HOW to enable RDP and how the Firewall blocks it unless you allow Remote Desktop. If I disable the Firewall, RDP immediately works.
Any ideas??!
Windows 10 1803 [for now].
- Show off your IT IQ. Take the Challenge »
- Outlook 2019 Desktop Signature Seems Corrupted
- Powershell script to reboot everyday except for the last day of the...
- Sonicwall Netextender 10.2.315 + RDP on RDP'd machine google maps b...
- ROM
- CPU
- RAM
- GPU
8 Replies
Probably an update remove the rule or the settings been reset. I believe what you need to do is just allow RDP app again in windows firewall setting. Are you able to do that?
- I've "reset to default" the firewall settings. No fix.
- I've disabled the firewall and re-enabled. No fix.
- I've disallowed and re-allowed RDP through firewall. No fix.
- I changed the RDP port. No fix.
I'm updating the PC to 1809 now... we'll see what that does!
3. I've disallowed and re-allowed RDP through firewall. No fix. --> Even if you allowed in the classic firewall settings for all network [Domain, Private, Public] type, still not able to remote access? If disable the firewall service completely, it fix the problem?
IT Professionals of Florida, Inc. is an IT service provider.
Windows firewall or network firewall? Are you allowing the correct port and protocol [tcp/udp] on the correct network profile [public, private, domain] and is the network profile registering correctly?
Can you wireshark the connection and verify what ports are being used? The fact that turning off the firewall makes it work is a pretty good indicator that your problem lies in a faulty setting.
petegaughenbaugh wrote:
The fact that turning off the firewall makes it work is a pretty good indicator that your problem lies in a faulty setting.
Totally agree! It's just that... I, originally, didn't change anything!
I'll run through some of those suggestions after the system finishes updating to v1809.
It takes a moment, but since it's not opening the RDP port using the "program" wizard, the best solution is probably to open port 3389 specifically, using manual settings in the GUI, or better, powershell commands to do this. It only takes a few minutes.
Jason Palmisano wrote:
Seemingly out of the blue I've found myself no longer able to RDP to a particular system [either externally or over the local network] unless I completely disable the Windows/Defender Firewall.
Previously, the Firewall was enabled with "Remote Desktop" as an 'Allowed App' through the Firewall. I'm not sure if a Windows Update changed this functionality.
I haven't found anything online that speaks to this -- it all talks about HOW to enable RDP and how the Firewall blocks it unless you allow Remote Desktop. If I disable the Firewall, RDP immediately works.
Any ideas??!
Windows 10 1803 [for now].
Allow port 3389 through the firewall and that would be it, from private, public and domain networks. If public allows it, then your network card is set to the public network category and that's probably why. You need to open port 3389 in the correct network zone your card is marked as.
So, Windows Firewall or hardware firewall....
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.