Link to home
Start Free TrialLog in
Avatar of crdixon
crdixon

asked on

Can't connect to a Windows 7-64 Professional using RDP

I have three computers that were purchased with Win 7 home premium. All three have been upgraded to Win7 Pro. The two running win7-32 Pro I can RDP into no problem. The one running Win 7-64 pro I can't. The one Win-7-64 PC also has a monitor running an HDMI connection to a 1080p HDTV and has an ATI Mobility Radeon HD4330 display adapter. I can use logmein no problem on this machine. I should also add that prior to upgrading to Win7-64 Pro, i attempted to install the RDP service service via this link which didn't work either. Although the installation of that hack acted like it would work because at the end of the install it tests that the correct ports are listening.

https://www.experts-exchange.com/questions/26433170/How-to-grant-RDP-connection-privilege-on-Windows-7-Home.html?sfQueryTermInfo=1+10+30+7+home+premium+rdp+window 

I checked the version of the termsrv.dll file and it seems to be ok (termsrv.dll version=6.1.7600.16385)
ASKER CERTIFIED SOLUTION
Avatar of koquito
koquito

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of crdixon
crdixon

ASKER

It was the windows firewall rules. Usually I think when you enable the Remote control settings, it automatically adjusts the fireall rules for you. I've never had to manually adjust a windows firewall rule to make RDP work before and I've used RDP on literally hundreds of PC's. I guess that hack I installed to get the RDP serer work on a Home Premium machine was the culprit. I feel pretty silly for not checking that for myself but sometimes it is the obvious that eludes us!  Thanks!
Avatar of crdixon

ASKER

There was nothing in any of the event logs on either the client or server PC, but the RDP firewall rule was the culprit.
Glad you got it figured out :)