Windows 7 64 bit cannot Remote Desktop to other Windows 7 computers
I have a 64 bit Windows 7 desktop at home, as does another employee here. I have a Windows 7 32 bit laptop here at work as does the other employee. Neither of us can Remote Desktop from those Windows 7 64 bit home computers into our laptops. However, both of us can Remote Desktop into our laptops just fine using Windows XP computers. I have the following settings on our work Windows 7 32 bit computers: System Properties Remote Tab: Allow connections from computers running any version of Remote Desktop is checked Under Select Users... our user names are listed Obviously those settings are fine since we have no problem Remote Desktop-ing in from XP computers. Using our home Windows 7 64 bit computers, we have tried to connect using the static assigned IP address as well as the computer name, neither works. None of the below articles addressed the issue nor did they help: http://windows.microsoft.com/en-US/windows7/Remote-Desktop-Connection-frequently-asked-questions http://windows.microsoft.com/en-US/windows7/Set-up-a-remote-connection-to-your-workplace-using-VPN http://windows.microsoft.com/en-US/windows7/Why-can-t-I-connect-to-a-network I am at a loss where to go from here. Any suggestions? Thank you.
February 23rd, 2011 10:21am

This stuff might have been tried but i'll say it anyway. Are the windows XP computers at work also? If so, then one thing that may be an issue is the static IP address on the laptops. Do they connect to the internet when at home, through your router? What im thinking is that your home computers are on a different network range than your work computers. If ive not already went over things that have been tried, then either your home PC needs to be on the same range as your laptop, or if your laptop is setup for work using wireless then use ethernet with DHCP enabled at home and disable the wireless when at home. Or if its setup through ethernet for work , then configure the wireless to use DHCP at home. If all that has been done, what actually happens when you try to connect does it have a specific error?
Free Windows Admin Tool Kit Click here and download it now
February 23rd, 2011 10:36am

This stuff might have been tried but i'll say it anyway. Are the windows XP computers at work also? If so, then one thing that may be an issue is the static IP address on the laptops. Do they connect to the internet when at home, through your router? What im thinking is that your home computers are on a different network range than your work computers. If ive not already went over things that have been tried, then either your home PC needs to be on the same range as your laptop, or if your laptop is setup for work using wireless then use ethernet with DHCP enabled at home and disable the wireless when at home. Or if its setup through ethernet for work , then configure the wireless to use DHCP at home. If all that has been done, what actually happens when you try to connect does it have a specific error? The XP computers that we use to Remote Desktop in are at home also. So that says the problem lies within the Windows 7 64 bit computers. But what setting! Where! I don't have the error messages we get right now: will record that tonight from home and post here. Thanks.
February 23rd, 2011 12:43pm

Here is what happens when I try to connect to my work Windows 7 32 bit computer via my home Windows 7 64 bit computer. Remember, entering these SAME CREDENTIALS via a Windows XP computer works fine. I get the message "The identity of the remote computer cannot be verified. Do you want to connect anyway?" (This does not happen with an XP computer). It shows a certificate that is "not from a trusted certifying authority." It asks "do you want to connect despite these certificate errors?" (This does not show up with an XP computer). I say "yes" and I also install the certificate to make it trusted. I get the message "The connection was denied because the user account is not authorized for remote login." Now remember, I HAVE INDEED set myself as an authorized remote user on the work Windows computer and my user name and password (credentials) work FINE using a Windows XP computer. To verify, on my work computer that I am trying to Remote Desktop in to, under Control Panel / System Properties / Remote tab / Remote Desktop, I have chosen "Allow connections from computers running any version of Remote Desktop." Under "Select Users" my user name is there and it says I have access. Now what?
Free Windows Admin Tool Kit Click here and download it now
February 24th, 2011 10:32am

Hi, I suggest adding the user account to the administrators group and Remote Desktop users group on your work laptops. Click Start -> Right click the computer and choose Manger -> Choose Local users and Group -> users. In the right pane, double click the account which you login with remote. On Member Of Tab, add the two groups. Also please refer to the following link and disable firewall or security software on both sides to check the result. http://www.davidmoore.info/2009/12/02/running-32-bit-remote-desktop-connection-on-windows-64-bit/ Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. Best Regards, NikiPlease remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
February 25th, 2011 5:29am

Hi, I suggest adding the user account to the administrators group and Remote Desktop users group on your work laptops. Click Start -> Right click the computer and choose Manger -> Choose Local users and Group -> users. In the right pane, double click the account which you login with remote. On Member Of Tab, add the two groups. Also please refer to the following link and disable firewall or security software on both sides to check the result. http://www.davidmoore.info/2009/12/02/running-32-bit-remote-desktop-connection-on-windows-64-bit/ Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. Best Regards, Niki Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. All user accounts in our company are administrator accounts. Sorry I just assumed this would be understood, my bad for not stating it clearly. And I already stated that the user name is in the Remote group. I am an IT manager, not a layman. That is why this is so perplexing. Even people with much much much more knowledge than I have so far have no solution for this problem. And so I go on and on researching on the internet, hoping somewhere someone has had the same problem and found the answer. Onward!
Free Windows Admin Tool Kit Click here and download it now
February 25th, 2011 12:50pm

Hi, Typically, there are two settings that must be configured before establishing Remote Desktop sessions. The first one is that remote connections must be enabled. The other one is users must be granted permission to connect to the server. Now please perform the following steps to check the permission: Step 1: Allow logon through Terminal Services ------------------------------------------- To connect to terminal server properly, users need to be granted the "Allow logon through Terminal Services" right. If the server is a domain controller, users also need to have "Allow logon locally" right. 1. Logon as administrator, click Start -> Run, type "rsop.msc" in the text box, and click OK. 2. Locate the [Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment 3. Check the "Allow log on locally" item to see whether this policy is defined. If so, the "Source GPO" column displays the policy that defines this policy. Please ensure "Administrators", "Remote Desktop Users", "Backup Operators", "Account Operators", "Print Operators", "Server Operators" are granted this right. If it is different, please configure the corresponding policy to grant the permission. 4. Check the "Allow log on through Terminal Services" item to see whether this policy is defined. If so, the "Source GPO" column displays the policy that defines this policy. Please ensure "Administrators", "Remote Desktop Users", and any other desired users are granted this right. If it is different, please configure the corresponding policy to grant the permission. 5. Check the "Deny log on locally" item to see whether this policy is defined. If so, the "Source GPO" column displays the policy that defines this policy. Please ensure that the user or any user groups that remote user belongs to is not included in this right. If so, please modify the corresponding policy to remove them. 6. Check the "Deny log on through Terminal Services" item to see whether this policy is defined. If so, the "Source GPO" column displays the policy that defines this policy. Please ensure that the user or any user groups that remote user belongs to is not included in this right. If so, please modify the corresponding policy to remove them. 7. After that, use gpupdate /force command to apply the policy. Step 2: Allow logon to Terminal Server ------------------------------------ To grant a user these permissions, start either the Active Directory Users and Computers snap-in or the Local Users And Groups snap-in, open the user's properties, click the Terminal Services Profile tab, and then click to select the Allow logon to Terminal Server check box. Step 3: Check TS permission ---------------------------- 1. Open the Terminal Services Configuration snap-in. 2. Right click the Rdp-Tcp item, and click Properties. 3. In the Permissions tab, click "Advanced". 4. By default, administrators group and Remote Desktop Users group have been granted the permissions. You can also add other users and groups and grant them the corresponding permissions. Also, if the account is in domain, please use domain\username to login. If it is a local account, please use .\username to login. Regards, NikiPlease remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
March 2nd, 2011 10:11pm

Dumb question - is this done on the host pc? What is done on the client pc? Thanks.pit
Free Windows Admin Tool Kit Click here and download it now
June 4th, 2011 9:08pm

Dumb question - is this done on the host pc? What is done on the client pc? Thanks.pit
June 4th, 2011 9:08pm

Dumb question - is this done on the host pc? What is done on the client pc? Thanks.pit
Free Windows Admin Tool Kit Click here and download it now
June 4th, 2011 9:08pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics