Hello,
For some reason I cannot connect to one of my workstations via Remote Desktop connection. I have been able to previously and don't know when the problem started. It may have been after I installed Windows Service pack number 3. During the Service Pack install it hung for a few hours before it finished. Anyway, I have checked that my firewall is turned off, enabled remote desktop, and have added a few different group members so they have remote desktop access. But, I am not able to connect. When I try, I get the following message:
"This computer cannot connect to the remote computer". Try connecting again. If the problem persists then call ME.
Have any ideas?
Thanks,
John
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
are you a Local Administrator on the pc, and also are you in the Remote Desktop Users group on the PC itself.
Set these permissions explicitly as a test.
some more settings here may be worth applying too:
http://support.microsoft.c
hth, Danny
I've got the same problem with my desktop. I connect via VPN and I can RD into other XP Pro SP 3 workstations on the LAN, but I can't connect to my own. However VNC does work. The only reason I would need the RD would be for local printing. It worked fine on SP 2, been using it for years Now nothing.
I have not found a solution for this. I suspect that somewhere during my upgrade to the latest service pack 3. It failed the first time and then I was able to get the service pack to install. Ever since then this one machine will not allow remote connections. The only answer I have is to reformat the machine and start over. Something is wrong with it. This machine works great in all other areas so I am not too concerned about it right now. But, when I get the time I will reformat the machine.
Are you still having issues? Did you resolve it? I notice we are having the same problem. I have been hammering on it for a week and nothing has resolved it. It appears to be a rogue problem. Here are some articles that helped a few computers and didn't help others.
http://support.microsoft.c
And there was an article about IRPStackSize in the registry that needed to be changed as well. I did both items and most of our machines that had problems started working.
Here is the Reghack:
[HKEY_LOCAL_MACHINE\SYSTEM
"autodisconnect"=dword:000
"enableforcedlogoff"=dword
"requiresecuritysignature"
"IRPStackSize"=dword:00000
Hope it helps.
We have been having the same problem of RDP not working after Service Pack 3 on various machines. we found the IRPStack and the manage add ons issue with sp3 and it did not fix it. I did discover though that when I turned off the firewall and turned it back on it failed with a security error (we have the firewall disabled by domain policy). After trying netsh winsock reset, I found article http://support.microsoft.c
Here is what was done that fixed it:
1. Click Start, click Run, in the Open box, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\
3. Delete the Security registry subkey, if it exists.
4. Exit Registry Editor, and then restart the computer.
Note It is important to delete the Security registry subkey if this subkey exists. This guarantees that the default security descriptor is used for starting Windows Firewall when the computer is restarted.
If you run Microsoft Component Object Model (COM), DCOM, or Microsoft COM+ applications to control the Windows Firewall service, you must also follow these steps: 1. Click Start, click Run, in the Open box, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWAR
3. On the File menu, click Export.
4. In the File name box, type C:\reg_AppID_CLSID.reg, and then click Save to save the registry file.
5. Delete the {ce166e40-1e72-45b9-94c9-3
6. On the File menu, click Import. (we did not re-import the file back in, just deleted it)
7. In the File name box, type C:\reg_AppID_CLSID.reg, and then click Open.
8. Click OK, and then exit Registry Editor.
9. Start the Windows Firewall/Internet Connection Sharing (ICS) service. To do this, type NET START SharedAccess at the command prompt, and then press ENTER.
Reboot the machine and it seems to work.
Business Accounts
Answer for Membership
by: rynoxPosted on 2008-05-13 at 18:49:50ID: 21560643
Are you connection by IP or name and can you ping that IP or name?
Weird network stuff? First thing I always do is reset the TCP/IP stack, works more often that you would think: from a command prompt > netsh int ip reset reset.log