Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Remote Desktop problem

Status
Not open for further replies.

jrp611

MIS
Oct 10, 2005
66
US
When trying to connect to a server via my windows xp pro I get this error message.
This computer can't connect to the remote computer

"The problem might be due to low virtual memory on your computer, Close your other programs and then try connection again."

I have checked the memory that was not the problem

have closed all the un-needed programs and still will not connect to the servers.

Any one have any thoughts or a fix for the problem.
thanks for the help
 
Can you connect via Safe Mode With Networking





Remote Desktop is described in detail in the Help and Support program under this heading "Remote Desktop overview".

280828 - How a Remote Desktop Connection Affects Windows XP Professional

The Features of the Remote Desktop Client in Windows XP

289289 - Remote desktop connection "The local policy of this system does not permit you to logon interactively"
 
jrp611,
Go to C:\Windows\System32 and check the version of mstsc.exe by right-clicking it selecting properties. Check this on both the XP workstation and on the server.

The standard that comes installed with both OS's is version 5.1.2600.2180, so if you're seeing a higher number, then you've installed the updated 6.0 version from Microsoft. It's usually a good idea to make sure you have the same version on both computers.

When I searched around on the net, I saw a few hits that mentioned a problem with thin client software. Not sure if you have that installed or not, but worth a mention...

~cdogg
"Insanity: doing the same thing over and over again and expecting different results." - Einstein
[tab][navy]For posting policies, click [/navy]here.
 
After checking all the setting I looked at any new patches that might have been added. and found 3 patches added so I uninstalled the patched and found one of the patches was giving me the trouble. and the next step is to reinstall the patches one at a time to see what is giving me the trouble. You would think MS would have checked there patches before they send them out.

thanks for the help
 
Let us know when you catch the culprit patch, good work, and good luck.
 
I have a similar problem. My Laptop has Windows XP MCE SP2 and desktop has XP Pro SP2. I can connect remotely to my laptop but can't connect Remote Desktop from Laptop to Desktop. The error message is "Can't connect to remote computer, try to connect again or contact computer owner or Administrator. MSTSC.exe on both is version 6. On both computers I have an account in my name as administrator and enabled for Remote Desktop Connection.
 
drrks,

Have you tried the suggestions already posted in this thread, what about Safe Mode With Networking?

Are there any clues in the Event Viewers of either machine?

Are there any firewalling interference, be aware that some antivirus software has hidden firewalling components.
 
drrks said:
I have a similar problem.

Do you? The error you listed doesn't say anything about being low on virtual memory. Are you seeing that error?

I recommend you start a new thread and reference this one if you need to.

~cdogg
"Insanity: doing the same thing over and over again and expecting different results." - Einstein
[tab][navy]For posting policies, click [/navy]here.
 
strange thought. Are you connecting with machine name or IP?
If machine name, switch to the ip address instead. Maybe its a DNS problem.
 
After trying all of the commands that were posted on the site,still could not get this patch to work. So I backed up all the data and rebuilt the computer from the start. Then loaded all the upgrades and patches to the computer. After the patches were added then installed the new remote desk top and this time it took it. I think there was a problem in the registry or a system file.

Thanks for the help.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top