Reply to: Win7 Remote Desktop help

[CheeseSlice]

Another thing i've noticed with Win7 and Win2k8 is the way NLA (network location awareness) controls the firewall policy based on whether you have a public, private or domain connection. If the connection is deemed public, it enforces the strongest firewall policy across all connections, even if some are safe networks like private or domain. I saw this when plugging a cable into a second network card on a 2008 box, the new connection was deemed public, and it immediately prevented RDP on the domain network port

you dont have more than one connection do you? even virtual ones such as vmware NAT interfaces could potentially cause this.

[Clippy]

you were probably typing in the wrong IP earlier and getting your neighbours PC

He, he, nope.

I was connecting via PC name.

[Spacecadet]

What a crock of sh!t!

Took another look at this tonight and have been able to connect straightaway!

I've not made any changes whatsoever since I last posted - guess that's Windows for you.

Just need to spend the next couple of hours downloading Windows Updates now!

Thanks for all the suggestions.

you were probably typing in the wrong IP earlier and getting your neighbours PC

[Clippy]

What a crock of sh!t!

Took another look at this tonight and have been able to connect straightaway!

I've not made any changes whatsoever since I last posted - guess that's Windows for you.

Just need to spend the next couple of hours downloading Windows Updates now!

Thanks for all the suggestions.

[gadgetman]

I used to get all sorts of such inconsistent behaviour with RDP. Thankfully working on a gig at a client that blocked the ports forced me to look elsewhere and I now exclusively use the free (and portable) version of Teamviewer.

Works really well, has way more features and is free for personal use. As I mentioned, you can even run it from a USB stick with no installation required. There's no messing about with port forwarding, firewalls, network protocols etc required.

You can also remote in via a browser.

I use it on all laptops in the house and remotely from work.

[Clippy]

on the new Win7 laptop, try going into:

Start button,
right click 'computer', select 'properties',
remote settings, remote desktop - select "allow connections only from computers running remote desktop with Network Level Authentication (more secure)".

Sometimes I find this setting is turned off on new installations.

Yup, did that.

[CheeseSlice]

on the old Win7 pc, try going into:

Start button,
right click 'computer', select 'properties',
remote settings, remote desktop - select "allow connections only from computers running remote desktop with Network Level Authentication (more secure)".

Sometimes I find this setting is turned off on new installations.

[edit] looks like you may have done this already... in which case ignore

[Clippy]

What OS is the computer you are connecting from using?

XP (and perhaps Vista?) cannot to connect to a windows 7 box by default, although it works the other way around. I believe you can get the latest remote desktop client here, that will allow the older OS to remote into windows 7.

Both units are on Win7.

My main laptop, the unit I connect from, is Win7 Ultimate and the spare PC is now Win7 Pro.

Will take a look again at this tonight.

[doodab]

What OS is the computer you are connecting from using?

XP (and perhaps Vista?) cannot to connect to a windows 7 box by default, although it works the other way around. I believe you can get the latest remote desktop client here, that will allow the older OS to remote into windows 7.

[Zippy]

As Spacecadet said, the specific port(s) need to be enabled (incoming and outgong)

[Spacecadet]

Will give it a try tomorrow - have given up for tonight.

Strange thing is, after my previous post, I rebooted my main laptop to see if that would make a difference.

Once it had re-booted, fired up Remote Desktop to connect to the spare PC and bingo, the login box came up.

Typed the password and it paused and then eventually came back with the same 'cannot connect' error message.

Most strange.


BTW, thanks for the suggestions.

Check that the user your logging in with has remote desktop rights

[Clippy]

have you tried just turning the firewall off, might as well rule it out completely

Will give it a try tomorrow - have given up for tonight.

Strange thing is, after my previous post, I rebooted my main laptop to see if that would make a difference.

Once it had re-booted, fired up Remote Desktop to connect to the spare PC and bingo, the login box came up.

Typed the password and it paused and then eventually came back with the same 'cannot connect' error message.

Most strange.


BTW, thanks for the suggestions.

[Spacecadet]

Good thinking but it already seems to be enabled.

have you tried just turning the firewall off, might as well rule it out completely

[Clippy]

windows firewall?



from Windows Firewall Quick Fixes: Windows Firewall (WF)

Good thinking but it already seems to be enabled.

[Spacecadet]

windows firewall?

I cannot use Remote Desktop to access another computer.
This happens when Windows Firewall blocks incoming traffic through TCP port 3389 on the computer you are trying to access. To use Remote Desktop to communicate with a remote computer, you must enable the predefined exception for Remote Desktop on the remote computer, which will dynamically allow incoming traffic on TCP port 3389.

To enable the Remote Desktop exception
On the remote computer, open Windows Firewall, and then click the Exceptions tab.

Select the Remote Desktop check box.

from http://technet.microsoft.com/en-us/l...0).aspx#BKMK_7