Problems Staying Connected to Terminal Services

[Jennifer]

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!

[Mr. Mike]

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.

Post by Jennifer
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!

[Vera Noest [MVP]]

The MS04-032 Security update caused quite a few issues.
Apart from the ones mentioned in KB 840987, check these:

891577 - A Terminal Services session to a Windows 2000-based
computer stops responding if a user logs off after the user quits a
16-bit Windows program
http://support.microsoft.com/?kbid=891577

891566 - You can no longer enumerate 16-bit programs that run in
separate NTVDMs after you apply the security update that is
mentioned in Microsoft Security Bulletin MS04-032 on a computer
that runs Windows XP or Windows 2000
http://support.microsoft.com/?kbid=891566

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Post by Mr. Mike
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.

Post by Jennifer
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!