Terminal Services REMOTE ADMIN PROBLEM

Hi all,

I have a W2K network which has 4 W2K Advanced Servers.
One Server is a Terminal Services running in application
mode with the Licensing Server installed. I also have
all the servers in Remote Admin mode (except the
application mode one obviously). I also have a W2K
advanced server running Microsoft Exchange 5.5 (which is
also in remote admin mode). A while back I could access
the exchange server remotely to perform admin tasks and
now all of a sudden I can not connect anymore. I was
wondering if anyone has any ideas on how to fix this so I
can connect to it again. Appreciate any help.

Luis

So what happens when you try to connect? Do you get an error message?
Have you checked if there are old disconnected sessions occupying
your 2 concurrent connections?

--
Vera Noest
MCSE, CCEA, MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please answer in newsgroup ---

"Luis Jesus" <luis.jesus@saint-gobain.com> wrote in news:0e8c01c33fed
$96c70410$a501280a@phx.gbl:

> Hi all,
>
> I have a W2K network which has 4 W2K Advanced Servers.
> One Server is a Terminal Services running in application
> mode with the Licensing Server installed. I also have
> all the servers in Remote Admin mode (except the
> application mode one obviously). I also have a W2K
> advanced server running Microsoft Exchange 5.5 (which is
> also in remote admin mode). A while back I could access
> the exchange server remotely to perform admin tasks and
> now all of a sudden I can not connect anymore. I was
> wondering if anyone has any ideas on how to fix this so I
> can connect to it again. Appreciate any help.
>
> Luis

Hi thanks for you quick reply.

There are no disconnected sessions.
Here are the two errors messages it gives me:
EVENT ID: 7024, The Terminal Services Licensing service
terminated with service-specific error 29.
EVENT ID: 29, The description for Event ID 29 in Source
(TermServLicensing) cannot be found. The local computer
may not have the necessary registry information or
message DLL files to display messages from a remote
computer. The following information is part of the event
(it ends here)

Im just wondering if this has anything to do with the
licensing service. All of a sudden it stopped allowing
access. This is exactly what shows up when I try to
connect "The client could not connect to the terminal
server. The server may be too busy. Please try connecting
later"

Luis

>-----Original Message-----
>So what happens when you try to connect? Do you get an
error message?
>Have you checked if there are old disconnected sessions
occupying
>your 2 concurrent connections?
>
> --
>Vera Noest
>MCSE, CCEA, MVP - Terminal Server
>http://hem.fyristorg.com/vera/IT
> --- please answer in newsgroup ---
>
>"Luis Jesus" <luis.jesus@saint-gobain.com> wrote in
news:0e8c01c33fed
>$96c70410$a501280a@phx.gbl:
>
>> Hi all,
>>
>> I have a W2K network which has 4 W2K Advanced
Servers.
>> One Server is a Terminal Services running in
application
>> mode with the Licensing Server installed. I also have
>> all the servers in Remote Admin mode (except the
>> application mode one obviously). I also have a W2K
>> advanced server running Microsoft Exchange 5.5 (which
is
>> also in remote admin mode). A while back I could
access
>> the exchange server remotely to perform admin tasks
and
>> now all of a sudden I can not connect anymore. I was
>> wondering if anyone has any ideas on how to fix this
so I
>> can connect to it again. Appreciate any help.
>>
>> Luis
>.
>