client could not connect to remote computer

  • Thread starter Thread starter Fiona
  • Start date Start date
F

Fiona

I have terminal services installed on a Windows 2003 server. When I try to
connect inside the network, responds there are no terminal servers
available, when I try to connect outside the network using the ip, I cannot
connect. "client could not connect to remote computer." I have set up
terminal services many times before without any problems. Am I missing
something on Windows 2003?
 
Is there anything in the EventLog on the TS?
Can you ping the server from the client?
Have you checked if the server is listening on port 3389 (with the
command netstat -an on the console)?
 
Unfortunately, my Chinese is no longer what it used to be :-)
If you want more help, could you please perform the simple tests that
I describe in my first post an post the results here (not as screen
dumps)?

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*
 
It is hard to translate from Chinese Terms into English Terms

Here is the "translated" error message.
\\myServerName rights permission history/record service not yet running or
\\myServerName cannot be accessed.



"Vera Noest [MVP]" <[email protected]> ¦b¶l¥ó
¤¤¼¶¼g...
Unfortunately, my Chinese is no longer what it used to be :-)
If you want more help, could you please perform the simple tests that
I describe in my first post an post the results here (not as screen
dumps)?

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*
 
Back
Top