• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 204
  • Last Modified:

Cannot Connect to Terminal server, server has lost is (listener) definition and now doesnt give access to RDC anymore


My server was allowing Terminal Service connection (win 2k server) in application mode.
Then I ghost it on an other server with more power, Now im unable to connect thru Terminal server.

Ive check almost everything but i cannot find the way to solve the problem,

When i go in - Terminal Service Manager, I see all my servers.
They all have after the server name "(listener)" exept for my server were talking about.

Im sure that is why I cannot connect thru my server... also I receive this message :

"The client could not connect to the Terminal server. The server may be too busy. Please try connecting later"

Ive got no firewall
Ive got all the rights
Ive check if It was still on port 3389, I am !
I have re-install the Terminal Service module in Add/remove prog.
I have Unable and delete my connection / reboot / re-create it !

Im out of idea and ressources... please help me ! Thanks,

1 Solution
Make sure the service is running under services.msc on the server itself.  then make sure it is set to start it.

Also try netstat -a to see if the server is listening on 3389 (it can be changed in registry)
I ran into this before... it ended up being an id that got corrupted. this created entries in the application event log, and when i searched by the ID I found a link to the solution.  so check the event log on the problem server and google the event ID, and you should be able to find your answer.
deewaveAuthor Commented:
Registry was corrupt !
I had to install fresh new registry for term services .reg files.
deewaveAuthor Commented:
This is now solve.

It was a problem in the registry.
I had to call Microsoft and they send me a files.reg to fix it.
Thanks to all.

PAQed with points refunded (250)

Community Support Moderator

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

Tackle projects and never again get stuck behind a technical roadblock.
Join Now