How to upgrade to newer version of Remot Desktop Connection

[jacksondorado]

I have two computers at home with RDC and one with one of them, I get this error message when trying to connect to a terminal server with RDC:

"The remote connection has timed out. Please try again later."

I thought I would try to upgrade the version of RDC to the latest from Microsoft but get this error when trying to install it:

"remote desktop connection cannot be installed because your operating system already has a built in version

 

[mattjurado]

If you are running XP, no need to try what you are doing, question is, why do you get that error? Where is the terminal server? Can you ping it? Can any other computers connect using remote desktop or the terminal services client?

Matt J.

Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.

 

[jacksondorado]

Good question. It's not actually my computer setup but a client's. The TS is at a remote location with an IP address and the firewall does not allow pinging.

This is the only client out of 20 that cannot connect. Everyone is at a different location. This PC has a wireless connection to the office router so I wonder if that might be the root of the problem.

 

[Ali147gta]

I suspect that the firewall at the client location perhaps does not have a rule set to allow the RDP port (I think it is 3389) to filter through ?

 

[mattjurado]

Doesn't sound that way ali, if the other 20 can connect, does this error pop up right away, or does it take awhile and then time out?

Matt J.

Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.

 

[bcastner]

Check the terminal server event logs for items like "Event ID 1004" , "The terminal server cannot issue a client license" .

If this event ID is generated when you try to logon, but there are TS Licenses avaialble, and others can logon, you can:

Delete the following registry key on the client, reboot the client (Key is regenerated), assign users "Full Control" of this registry key, then try logging on.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing