clients cannot connect

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

Guest

We had to switch our windows 2000 terminal server to a completely different
hardware. After a backup restore from the old server we had to do a windows
2000 repair installation because the new server did not start in normal mode.

Everything now is working as before except the terminal service in
application mode. The problem is: there is no RDP listener thread! No service
listening to port 3389. In terminal service mangager there is only session ID
65536 with staus "disconnecting" instead of "listening".

Except basic microsoft services no other application active (no firewall etc).

Any help appreciated, urgent
Wolfgang
 
addendum:
Terminal service licence manager running on same machine with status:
activated.
Terminal service configuration RDP-session activated.
No entries in even log.
 
This did solve my problem!

I did read the KB270588 article before. But because it states that the
problem was solved with Windows 2000 SP2 and the registry entry was slghtly
different, I assumed that this was not our problem.
In our case the status of the connection was "disconnecting" not "down", we
used Windows 2000 SP4 installation CD and there was no key value with name
\Device\Video0. But after adding this key with the given value the problem
was gone.

Thank you for the help
Wolfgang
 
I'm glad that it solved your problem, Wolfgang, and thanks for
reporting back here. I was also a bit doubtful if it would work,
because of the SP2 reference, so your feedback is appreciated!

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
 
Back
Top