• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

just installed windows 7, cannot get RDP working for the life of me

A

alyarb

Platinum Member
This was so simple under XP that it's really starting to piss me off. At first I liked the new windows firewall because it looks like you have a lot more control. Unfortunately, none of the settings appear to do anything. Of course remote desktop is enabled, yet with the default firewall rules for RDP, I cannot get a connection nor can I see my service remotely (from canyouseeme.org).

Fair enough, I'll remove that rule and just make a new rule for port 3389. Same story. can't see my service/connection refused. So I disable the firewall altogether. Same story. Connection refused. So I re-enable the firewall, set everything to default, allow remote desktop. connection refused. So then I tried changing the RDP port and made a new rule for just that port. Same story. and yes I know how to forward ports on my router.


seriously, what the hell is going on here? I even tried allowing edge traversal for the rules in the "advanced options," but there is no combination of these settings that will open port 3389 for my service. any ideas would be great.
 
Did you select the users to allow RDP for? Are you using win 7 business or ultimate? Do you have to edit any settings on your router?
 
there is only 1 user on this machine, so windows enables RDP for that user automatically when you enable remote desktop. I was able to get it working though. I think by default, even after erasing everything, windows puts a duplicate rule in the firewall and that was a problem, though i'm not sure because everything I did leading up to this was technically correct also.

now i'm wishing there was a "backup my firewall rules" button because i'm not doing this again.


and my biggest curiosity of all: disabling the firewall leaves everything closed rather than opened. how can you get around that? what if i'm on a secure LAN and want no firewall? what if i have a hardware firewall and don't care to use microsoft's? I can see this becoming a pain down the road.
 
Last edited:
alyarb said:
there is only 1 user on this machine, so windows enables RDP for that user automatically when you enable remote desktop. I was able to get it working though. I think by default, even after erasing everything, windows puts a duplicate rule in the firewall and that was a problem, though i'm not sure because everything I did leading up to this was technically correct also.

now i'm wishing there was a "backup my firewall rules" button because i'm not doing this again.


and my biggest curiosity of all: disabling the firewall leaves everything closed rather than opened. how can you get around that? what if i'm on a secure LAN and want no firewall? what if i have a hardware firewall and don't care to use microsoft's? I can see this becoming a pain down the road.
Click to expand...

Disabling the built in Windows firewall opens all ports. It does NOT block them. Zone alarm used to do this, but the Windows Firewall does not.

You're problems with RDP are unique and unusual. There was something else causing the problem that you're missing. You shouldn't need to worry about backing up the rules since they are simple and straight forward.
 
dawks said:
Disabling the built in Windows firewall opens all ports. It does NOT block them. Zone alarm used to do this, but the Windows Firewall does not.
Click to expand...

this doesn't describe the behavior i was seeing at all. i had the windows firewall service stopped and disabled too. even after a reboot. not only that but there was a yellow action triangle next to my RDP toggle (in system properties) saying "remember to open the port in windows firewall," so you're right. maybe everything is left open, but windows does not allow RDP unless the firewall is running. very uncool either way. the services need not be aware of the firewall. only the firewall should be aware of services.

turns out you are able to back up your rules though. i wonder if that works or if it's there for looks.
 
Last edited:
alyarb said:
this doesn't describe the behavior i was seeing at all. i had the windows firewall service stopped and disabled too. even after a reboot. not only that but there was a yellow action triangle next to my RDP toggle (in system properties) saying "remember to open the port in windows firewall," so you're right. maybe everything is left open, but windows does not allow RDP unless the firewall is running. very uncool either way. the services need not be aware of the firewall. only the firewall should be aware of services.

turns out you are able to back up your rules though. i wonder if that works or if it's there for looks.
Click to expand...

RDP works regardless of whether the firewall is running or not. Its reminding you to open/forward the port for a 3rd party firewall if you're running one.

When you enable remote desktop, it will automatically open the proper ports to let RDP through. The one thing that might be giving you trouble is choosing the proper RDP authentication, since Win Vista and 7 have new methods.
 
well, maybe you can help me disable the firewall. I just got home and I now see that my computer is not accepting any connections over 3389, and I do not have time to baby this thing every day.

I've selected "turn windows firewall off" for the local and public networks and it still won't connect (connection refused from canyouseeme.org). so i stopped/disabled the Windows Firewall service. same story. i want this firewall out of my life forever, so what else do I need to do?
 
This really shouldn't be difficult. There are 2 steps.

1. Enable RDP.
2. Disable firewall (although someone mentioned that enabling RDP automatically punches a hole for you - didn't realize that).

That's it.

Try to telnet on 3389 from another computer on the same subnet. If you are getting denied, something else is up. Either another firewall is running, or RDP is not properly enabled.
 
RDP times out when trying to connect, even on the LAN side. firewall is disabled. remotes enabled.

netstat -a does list 3389 as a listening port, however.
 
it sucks when there is nothing left to try. so i did a firmware reset on the router and manually enabled RDP in the reg. seems to work with the firewall down. thanks guys.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top