Remote Desktop: Brand new 64-Bit upgraded to Pro refuses all Login Attempts. Old Win-7 machines work correctly.
<!-- @page { margin: 0.79in } P { margin-bottom: 0.08in } --> I just purchased a brand new Gateway computer with 64-Bit Win-7 home pre-installed. I used “Windows Anytime Upgrade” to upgrade the OS to Win-7 Pro so that I could use remote desktop and have the ability to control this computer remotely from my Dell (master-control) Workstation. This new computer can connect to the Dell workstation and to my ancient legacy Gateway workstation; however, neither legacy machines can connect to this brand new Win-7 installation. I have an ancient 10-year old 32-Bit Gateway workstation that I upgraded to 32-Bit Win-XP Pro. This computer can connect to the Dell, and the Dell can connect to this workstation with no problems. The new Gateway can connect to this ancient GW workstation; however, this ancient 32-Bit workstation cannot even “see” the new GW computer on the network much less connect to it. I have a 5-year old Dell workstation that originally came with 32-Bit Win-XP Pro installed. I purchased a boxed-set: “64-Bit Win-7 Pro”, and installed it on my second hard drive (no upgrade) in a dual-boot configuration. Both OS installations work perfectly. This is my master computer. This computer can connect to the ancient 32-Bit Gateway, but it can not connect to the brand new 64-Bit one. I expect to be able to control the other two computers from this Dell. I can not, even individually. Additional Info: 1. I can “ping” the new Gateway computer from either old computer. 2. On the Dell, if you click “Control Panel\All Control Panel Items\Network Map”, the new Gateway computer is listed. This is the only place where the new computer is listed on the Dell. The Dell does not “see” the new Gateway in other displays. 3. On the Dell, if you open Remote Desktop and try to connect to the new Gateway, You get the error “Your Credentials Did not Work”, and on the second line “The credentials that were used to connect to GW64-W7 did not work. Please enter new credentials”. The connection succeeded, but the log-in failed. 4. On the new Gateway (only), open “Control Panel\All Control Panel Items\System”, and click Remote Settings. Under Remote Desktop, there is a little yellow caution symbol with the warning message: “You must enable the Windows Firewall exception for Remote Desktop”. This error message is bogus. Yes, has been enabled for home/work and disabled for public. This indicates something is wrong, but not what is actually wrong. 5. I have did my best to configure both 64-Bit Pro OS's identically, except for unique identifiers. It has been checked over and over. I have followed instructions from zillions of blogs. No success. I have been fighting problem this since forever. Could the MS Upgrade to Pro been faulty? The Pro boxed set worked. Any Ideas? Keith.
July 25th, 2010 6:23am

check if: 1. the account has password 2.the language you type is the same as password language if all its OK then try write the account name like name of computer you connect to \name of account
Free Windows Admin Tool Kit Click here and download it now
July 25th, 2010 1:39pm

<!-- @page { margin: 0.79in } P { margin-bottom: 0.08in } --> Thanks I tried your suggestion. That did not help. 1. All machines are password protected. For my account, I use the same password on all machines. 2. The language is the same on all machines. 3. I tried your suggestion “name of computer you connect to \ name of account ”. I got the same result that I got when I did not use the “name of computer you connect to”. 4. Note that if I connect a keyboard and monitor directly to the computer and login directly, everything works perfectly with the exact same credentials that fail using Remote Desktop. 5. I am not on a Domain. I am NOT using “Homegroup”. I am using “Workgroup”. All Google results said do not use homegroup, use workgroup. The Dell does “connect” to the Gateway as I get a login window generated by the remote computer; however, my "valid" log-in credentials are rejected by the remote computer. If you Google “Your Credentials Did not Work”, you get tons and tons of responses, and I tried tons and tons of recommended fixes. One of those Google responses was “Microsoft Answers”, with someone having a similar problem as mine. MS Answers said to contact this forum for help. I used the same Google search to set up the 64-Bit Windows-7 Remote Desktop installation on the Dell. In that case, the recommended fixes "worked". On the Gateway, they do not work. This problem is obviously a networking “security feature” designed into Windows-7 that “breaks” Remote Desktop operation under some unknown conditions. Thanks.
July 26th, 2010 6:53am

<!-- @page { margin: 0.79in } P { margin-bottom: 0.08in } --> Last week, on my Dell machine, I created a “WindowsImageBackup”, my first. Today, I just found something new and very disturbing! The WindowsImageBackup folder did not contain one backup image; the back-up program created two distinct backup images! The two sub-folders under WindowsImageBackup were named: Dell-64 and Dell-W7. Dell-64 is what I originally named the system installation when I installed Windows-7 from a disk. Dell-W7 is that which I renamed the installation later on to clear up confusion on my network. The name “Dell-64” should no longer exist anywhere in my Dell system, but it does live on, hidden, somewhere. Somewhere Windows 7 stored the the original name and did not change it when I commanded it to change the system names. Two different computer names should never be allowed, but Win-7 does allow it. I changed the system names on my brand new Gateway as well to GW64-W7 from what it was at installation. I will be creating a “WindowsImageBackup” on that machine later today to see if 64-Bit Windows 7 recreates that unacceptable situation. This situation could really be the cause that screwed up networking with the Gateway machine but did not affect the Dell. The question now is how do I find out where Dell-64 is stored and buried on my Dell system and delete the superfluous instance without destroying anything? I may have to repeat the process on the 64-Bit Gateway as it may be the root cause of my broken Remote Desktop.
Free Windows Admin Tool Kit Click here and download it now
July 27th, 2010 12:48am

Hi Keith, Please take the following steps to troubleshoot our issue: 1. Open Credential Manager and clear the Remote Desktop related information 2. Type the name of the user that you want to add in the Remote Desktop Users dialog box 3. Verify the Remote Desktop related services: remote desktop configuration remote desktop services Remote Desktop Services UserMode Port Redirector 4. Please temporary disable the antivirus and firewall on the computers. Please let us know if you have installed the certifications for Remote Desktop. If so please remove the certifications and reinstall when you try to connect via Remote Desktop. a) Click Start, in the Start Search box enter “mmc”. b) Click File->Add/Remove Snap-in. c) Add Certificates for “My User Account”. d) Find the certificate which is issued to the other computer. By default it is installed in Intermediate Certification Authorities\Certificates. Right-click and choose All Tasks->Export, save it as a backup. e) Remove the certification. regards, Sabrina
July 28th, 2010 11:35am

<!-- @page { margin: 0.79in } P { margin-bottom: 0.08in } --> Hi Sabrina: THanks for the reply. On the remote computer, under Credential Manager, Nothing had been established. Nothing to undo. On the local computer, under Credential Manager, everything had ancient and invalid values. They were ALL deleted. We have moved forward. I now can display the picture from the remote computer account on the local computer; however, I cannot log in. It understands my log-in name; however, it does not understand my password. What does the following mean? I do not have a clue. Verify the Remote Desktop related services: remote desktop configuration remote desktop services Remote Desktop Services UserMode Port Redirector On the remote system, anti-virus software has been totally removed until the network problem has been solved. I am now running Windows Firewall. This has been turned OFF. Click System->Remote Settings and the System Properties window opens. At this point under Remote Desktop, the Yellow caution message is still being displayed: You must enable the Windows Firewall exception from Remote Desktop. What exactly does this mean? On the computer that works, this warning message does not exist. Thanks, Keith.
Free Windows Admin Tool Kit Click here and download it now
July 30th, 2010 9:11am

Well, I finally identified the Remote Desktop problem in Windows-7. What a nightmare! We are talking workgroups not domains. With virgin OS installations, two 64-Bit Win-7 computers with unique computer names and identical user ID's can Remote Desktop into each other with no problems. Change both names to another set of unique computer names while retaining the same user-ID's, the Win-7 database becomes totally corrupted and totally unusable breaking Remote desktop operation. I was never able to circumvent the problem by simply debugging and fixing my Windows-7 installation(s), using the debugging techniques that most professional system developers use. Database corruption is spread all over the place! This problem does not exist with 32-Bit XP or any earlier NT releases. Note Remote Desktop is only broken between two 64-Bit Win-7 machines. Between a 64-Bit Win-7 machine and an XP machine, things still function in both directions. When I changed the user-ID on my Gateway machine, Remote Desktop suddenly started to function again. There should never be any constraints on user ID's on different computers, as they cannot be controlled in the industry. Windows-7 has created a naming constraint!
July 31st, 2010 8:10am

Has this been made public? Are you the only person who knows this? I have not been able to force the connection between a Win 7 Ultimate 64-bit computer and Win 7 Home Premium 64-bit computer. And I have treid what I thought was everything. I have done a lot of tourbleshooting, but do not believe that I have changed the names of the computers. But if I have, does this mean I broke my remote Desktop Connection? How can I repeat your actions and get a successful connection? And my thanks to MicroSoft for yet another beautiful piece of software...
Free Windows Admin Tool Kit Click here and download it now
September 2nd, 2010 8:55pm

Not sure what the OP's issue was but changing the name of a windows does not break RDP, atleast not for us, we rename all new dell boxes and more than once in some cases. as for win 7 Ult to 7 HP Home version do not have the option to allow inbound RDP connections, I think you can do outbound connections, but I do not run home version of OS's so I can not say for sure.
September 2nd, 2010 9:35pm

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

Other recent topics Other recent topics