Windows Firewall not allowing Remote Desktop
Get answers from your peers
along with millions of IT pros who visit Spiceworks.
Join Now
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). Popular Topics in General Windows
TEST YOUR SMARTS
Which of the following retains the information it's storing when the system power is turned off?
Submit »
88% of IT pros got this right.
Challenge
×
8 Replies· · ·
Poblano
OP
landicechan
Jan 30, 2019 at 02:32 UTC
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?
0
· · ·
Jalapeno
OP
Jason Palmisano
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
I'm updating the PC to 1809 now... we'll see what that does!
0
· · ·
Poblano
OP
landicechan
Jan 30, 2019 at 03:22 UTC
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?
0
· · ·
Datil
OP
Pete ITProFL
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
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?
1
· · ·
Jalapeno
OP
Jason Palmisano
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
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.
0
· · ·
Tabasco
OP
Agle Utah
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
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.
0
· · ·
Pure Capsaicin
OP
dbeato
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
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.
0
· · ·
Chipotle
OP
Matt_Mueller
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.
So, Windows Firewall or hardware firewall....
0
This topic has been locked by an administrator and is no longer open for commenting. To continue this discussion, please ask a new question. |