«

Hi
I use to connect an ISA server through Terminal Services. Today when I tryed
to do it again, I started to receive an error message with the following text:

THE CLIENT COULD NOT CONNECT TO THE TERMINAL SERVER. THE SERVER MAY BE TOO
BUSY. PLEASE TRY CONNECTING LATER.

But I can´t connect to this server. Other servers are available from the
same pc.

What´s wrong?

ooops... the environment is fully W2K


"TS Error" wrote:

> Hi
> I use to connect an ISA server through Terminal Services. Today when I tryed
> to do it again, I started to receive an error message with the following text:
>
> THE CLIENT COULD NOT CONNECT TO THE TERMINAL SERVER. THE SERVER MAY BE TOO
> BUSY. PLEASE TRY CONNECTING LATER.
>
> But I can´t connect to this server. Other servers are available from the
> same pc.
>
> What´s wrong?

"TS Error" <TS > wrote in message
news:2B8A8DBC-2CCE-416A-BB49-...
> ooops... the environment is fully W2K
>
>
> "TS Error" wrote:
>
> > Hi
> > I use to connect an ISA server through Terminal Services. Today when I
tryed
> > to do it again, I started to receive an error message with the following
text:
> >
> > THE CLIENT COULD NOT CONNECT TO THE TERMINAL SERVER. THE SERVER MAY BE
TOO
> > BUSY. PLEASE TRY CONNECTING LATER.
> >
> > But I can´t connect to this server. Other servers are available from the
> > same pc.
> >
> > What´s wrong?

here's a hint:
"THE SERVER MAY BE TOO BUSY"

This means that the port is open and an ACK is received, but that the server
isn't letting you in. Could be you need to reboot the server.

....kurt

"TS Error" <TS > wrote in message
news:2B8A8DBC-2CCE-416A-BB49-...
> ooops... the environment is fully W2K
>
>
> "TS Error" wrote:
>
> > Hi
> > I use to connect an ISA server through Terminal Services. Today when I
tryed
> > to do it again, I started to receive an error message with the following
text:
> >
> > THE CLIENT COULD NOT CONNECT TO THE TERMINAL SERVER. THE SERVER MAY BE
TOO
> > BUSY. PLEASE TRY CONNECTING LATER.
> >
> > But I can´t connect to this server. Other servers are available from the
> > same pc.
> >
> > What´s wrong?

ipconfig /flushdns locally

The problem is usually the localhost if no other changes have been made to
the TS


"TS Error" <TS > wrote in message
news:E48F84CC-4F50-4720-8B89-...
> Hi
> I use to connect an ISA server through Terminal Services. Today when I
tryed
> to do it again, I started to receive an error message with the following
text:
>
> THE CLIENT COULD NOT CONNECT TO THE TERMINAL SERVER. THE SERVER MAY BE TOO
> BUSY. PLEASE TRY CONNECTING LATER.
>
> But I can´t connect to this server. Other servers are available from the
> same pc.
>
> What´s wrong?

TS Error a présenté l'énoncé suivant :
> Hi
> I use to connect an ISA server through Terminal Services. Today when I tryed
> to do it again, I started to receive an error message with the following
> text:
>
> THE CLIENT COULD NOT CONNECT TO THE TERMINAL SERVER. THE SERVER MAY BE TOO
> BUSY. PLEASE TRY CONNECTING LATER.
>
> But I can´t connect to this server. Other servers are available from the
> same pc.
>
> What´s wrong?

I had that question in my exams, with the following answers


- Administrator is on hollyday

- It was replaced by a Linux Box, and you have to use "Export X"

- Novell doesn't allow to use RDP client, take "NWADMIN"

- The server was turned of

Choose the BEST answer

Any idea ?


Olivier

--
Ceci est une signature automatique de MesNews.
Site : http://www.mesnews.net

>I had that question in my exams, with the following answers
>
>
>- Administrator is on hollyday
>
>- It was replaced by a Linux Box, and you have to use "Export X"
>
>- Novell doesn't allow to use RDP client, take "NWADMIN"
>
>- The server was turned of
>
>Choose the BEST answer
>
>Any idea ?

beats me.

Kline Sphere (Chalk) MCNGP #3

Terminal service only allows two open sessions at each
time....it might be the problem.
>-----Original Message-----
>Hi
>I use to connect an ISA server through Terminal Services.
Today when I tryed
>to do it again, I started to receive an error message
with the following text:
>
>THE CLIENT COULD NOT CONNECT TO THE TERMINAL SERVER. THE
SERVER MAY BE TOO
>BUSY. PLEASE TRY CONNECTING LATER.
>
>But I can´t connect to this server. Other servers are
available from the
>same pc.
>
>What´s wrong?
>.
>

did you hear "=?Utf-8?B?VFMgRXJyb3I=?=" <TS
> say in
news:E48F84CC-4F50-4720-8B89-:

> Hi
> I use to connect an ISA server through Terminal Services. Today when I
> tryed to do it again, I started to receive an error message with the
> following text:
>
> THE CLIENT COULD NOT CONNECT TO THE TERMINAL SERVER. THE SERVER MAY BE
> TOO BUSY. PLEASE TRY CONNECTING LATER.
>
> But I can´t connect to this server. Other servers are available from
> the same pc.
>
> What´s wrong?

I also had a problem when there was a major HW config change to the
terminal server. have a look at KB atricle Q270588

--
Neil MCNGP #30
Visit www.mcngp.com for your chance to amuse
nerd32768 and annoy the rest of us

A TS in admin mode will give an 'exceeded' error message, not the one
mentioned. A TS in application mode will connect far more than two sessions.


"Mr.Dhy" <> wrote in message
news:0a5101c4ecec$0d3683d0$...
Terminal service only allows two open sessions at each
time....it might be the problem.
>-----Original Message-----
>Hi
>I use to connect an ISA server through Terminal Services.
Today when I tryed
>to do it again, I started to receive an error message
with the following text:
>
>THE CLIENT COULD NOT CONNECT TO THE TERMINAL SERVER. THE
SERVER MAY BE TOO
>BUSY. PLEASE TRY CONNECTING LATER.
>
>But I can´t connect to this server. Other servers are
available from the
>same pc.
>
>What´s wrong?
>.
>