[] Error not connected to windows 2000 server

R

Roberto Escamilla

When i intented connected i receive the message
"The client could not connected to the terminal. The server may be too busy"

In event viewer (directory server) i have a message "The directory services
was unabled to find any RPC protocol failling with error 1719."

What happend or how to activate de terminal services, i cannot "telnet
furecltda 3389"

the port 3389 don't appear in netstat -na

how do to activate the 3389 and RPC protocol

I have not firewall

Thank You
 
V

Vera Noest [MVP]

Have you installed Terminal Services? In Control Panel -
Add/Remove programs - Add/Remove Windows Components.

If you did, and it isn't running at all, there should be something
in the EventLog on the server (possibly only after a reboot).
 

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

Protocol Error 0x1104 connecting to 2003 Servers 9
Can Telnet to port 3389 but can't get to logon screen 2
Remote clients immediate disconnect from TS Server 2
Termsrv not listening on 3389 0
No user can login after Win2k SP3/SP4 installation - Posting for 4th time 6
client could not connect to the terminal server. 1
Terminal Server not longer accepting connections 1
Error when starting Terminal Services 1

Top