Strange - The client could not connect to the terminal server

[Petrica Voju]

Hardware: 2 x Xeon 2,4 G, 4 Giga Ram, Raid SCSI 5 with spare, Gigabit
Ethernet
Windows 2000 server sp4 terminal server application mode : ERP and Excel
reports
80 ..120 max. terminal users connected (LAN and WAN)

Work fine 2 years

A strange bahavior has happened in the past few months. After a variable
period which may vary from 4 hours up to a week, the server is unable to
accept remote connections anymore:" The client could not connect to the
remote computer....might be too busy to accept new connections ...please try
again later" . The connections already in place are working OK.
The only solution for the problem is the restart of the server; this is
still working; but for how long....!?

RDP listener ..OK
No entries in even log

I suspect a "hotfix" problem !??!

[mwcanton]

I am having the same problem, but it is happening after a longer period of
time. I thought it might be a 120 day license issue. Rebooting my servers
didn't solve the problem. Let me know how you make out. If I come up with
something to today I'll share it.

Post by Petrica Voju
Hardware: 2 x Xeon 2,4 G, 4 Giga Ram, Raid SCSI 5 with spare, Gigabit
Ethernet
Windows 2000 server sp4 terminal server application mode : ERP and Excel
reports
80 ..120 max. terminal users connected (LAN and WAN)
Work fine 2 years
A strange bahavior has happened in the past few months. After a variable
period which may vary from 4 hours up to a week, the server is unable to
accept remote connections anymore:" The client could not connect to the
remote computer....might be too busy to accept new connections ...please try
again later" . The connections already in place are working OK.
The only solution for the problem is the restart of the server; this is
still working; but for how long....!?
RDP listener ..OK
No entries in even log
I suspect a "hotfix" problem !??!