TS is "too busy"

What are some steps to get rid of the following error message:

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

TS has been working for months and has decided to stop working lately.

Thanks in advance.

JK

Gizmo
Tue Jul 08 17:27:54 CDT 2003

Hi JKinSD

Is this in Apps mode ?

If so then as only have two connections both must be still in a connected
mode cos remote pc got disconnected unexpectedly i.e didnot log off
properly. If in front of server just need to ' disconnect sessions ' in TS
manager on server. If working remotely, out of hours, I have '
psshutdown.exe ' sitting on C drive and I VPN, map a drive to C$ and run
psshutdown from command prompt with R switch which reboots the server,
ressetting TS.


"JKinSD" <jkurth@nospam.krns-inc.com> wrote in message
news:eYwNkgZRDHA.4024@tk2msftngp13.phx.gbl...
> What are some steps to get rid of the following error message:
>
> "The client could not connect to the Terminal Server. The server may be
too
> busy. Please try connecting later."
>
> TS has been working for months and has decided to stop working lately.
>
> Thanks in advance.
>
> JK
>
>

Gizmo
Tue Jul 08 17:35:12 CDT 2003

Will add also that there are other ways to connect to server (backup dialup,
other third party remote connections, some free) and as long as ISA
configured to let in these would save a reboot.


"Gizmo :-)" <dontwant@anymorespam.com> wrote in message
news:eMBxsAaRDHA.2432@TK2MSFTNGP10.phx.gbl...
> Hi JKinSD
>
> Is this in Apps mode ?
>
> If so then as only have two connections both must be still in a connected
> mode cos remote pc got disconnected unexpectedly i.e didnot log off
> properly. If in front of server just need to ' disconnect sessions ' in TS
> manager on server. If working remotely, out of hours, I have '
> psshutdown.exe ' sitting on C drive and I VPN, map a drive to C$ and run
> psshutdown from command prompt with R switch which reboots the server,
> ressetting TS.
>
>
> "JKinSD" <jkurth@nospam.krns-inc.com> wrote in message
> news:eYwNkgZRDHA.4024@tk2msftngp13.phx.gbl...
> > What are some steps to get rid of the following error message:
> >
> > "The client could not connect to the Terminal Server. The server may be
> too
> > busy. Please try connecting later."
> >
> > TS has been working for months and has decided to stop working lately.
> >
> > Thanks in advance.
> >
> > JK
> >
> >
>
>

JKinSD
Wed Jul 09 09:20:18 CDT 2003

Thanks to all for responding to this.

The server is in apps mode, I cant and dont want to just restart the server
and have it magically work. It is in production nearly 24 hours a day.

I restarted the MTA Stacks which I was told a long time ago should fix this
but that only works 50% of the time.

I did just recently install SP4 so I applied those registry changes and have
yet to restart the Server. Thanks again.

JKinSD


"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@pacbell.net>
wrote in message news:3F0B6975.2895E3F1@pacbell.net...
> Did you load SP4? I had this occur right after the install of SP4. It's
a
> "normal" sbs issue.
>
http://www.smallbizserver.net/sbs2000/Terminal_Server_keeps_indicating_that_
the_TS_server_is_busy.aspx
>
>
>
> JKinSD wrote:
>
> > What are some steps to get rid of the following error message:
> >
> > "The client could not connect to the Terminal Server. The server may be
too
> > busy. Please try connecting later."
> >
> > TS has been working for months and has decided to stop working lately.
> >
> > Thanks in advance.
> >
> > JK
>