Problems Staying Connected to Terminal Services

G

Guest

I just completed an update (KB840987) and it has caused problems with
Terminal Services. The computer makes us reboot every morning to allow users
to remote in to the main program everyone is using on the server. In the
morning when we come in before having to reboot the error message is too many
computers connected to the network or incorrect ip. After we reboot there
are not problems until the next morning. How can I correct this problem? Or
delete the update? Has anyone run into this problem before? I am running
Windows 2000 Server Advanced...thank you!
 
G

Guest

Is your terminal server set to keep alive the sessions or disconnect? We had
a similar issue and telling the terminal server to disconnect the session
solved it. We would have many open sessions that would eventually shut down
the terminal server. Just a thought.
 

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

Losing connection each night in Terminal Server after an update 1
inoperative terminal services 10
Printing to remote location over Terminal Services 3
Terminal Server License Server 1
Terminal Services crash? or something else? 3
Restricting Terminal Services 1
terminal services printing problems 1
logout delay with Terminal services 1

Top