Getting "The client could not establish a conection to the remote computer" message.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We recently moved our Terminal Services from an NT4 Server to a W2K Server. This error is only occurring from the two clients that we ran the previous version of Terminal Services Client on. All of the new clients [that did not have NT4 TS clients previously installed] are running RDP 5.1 and are working beautifully.
 
Have you tried removing the MSLicensing registry key from
those clients to see if that helps?

Are there any eventlog entries on the terminal server that
would indicate a problem with these client's connections?

-M
-----Original Message-----
We recently moved our Terminal Services from an NT4
Click to expand...
Server to a W2K Server. This error is only occurring from
the two clients that we ran the previous version of
Terminal Services Client on. All of the new clients [that
did not have NT4 TS clients previously installed] are
running RDP 5.1 and are working beautifully.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

MAC RDP Time Zone Incorrect 0
RDP client on Wyse terminal session 1
Local client printers not available in terminal services 1
RDP keeps dropping 5
client could not establish a connection 3
Event ID: 1004 The terminal server cannot issue a client license. 2
Terminal Clients Error Message 3
New remote client not ablelogin W2K Terminal services after AD upg 11

Back
Top