Terminal Service has ended the connection

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)

We use Terminal services on a server running Windows 2000
Server. I have installed the client software on my pc at
home. When I try to open the connection, a message comes
back saying terminal server has closed the connection. I
was checking the service because I had another user who
installed the client software from home and he was issued
a temporary license. When his 90 days expired, the server
did not issue him a permanent license. I thought maybe the
problem was we were out of licenses. Well after installing
on my pc at home and not connecting, I checked the
licenses on the server and my pc was issued a permanent
license. Microsoft troubleshooting stated I could up the
concurrent connections but the setting is already at
unlimited connections. Does anyone know something I could
try or the resolution to this? The other user is also
getting the same message about closing the connection.

Thanks,

E. Rea

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)

Is there anything in the EventLog on the TS when you try to connect?
Which OS do you run on your client PC?

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

"E Rea" <anonymous@discussions.microsoft.com> wrote in
news:8aa101c4329d$5e434e20$a001280a@phx.gbl:

> We use Terminal services on a server running Windows 2000
> Server. I have installed the client software on my pc at
> home. When I try to open the connection, a message comes
> back saying terminal server has closed the connection. I
> was checking the service because I had another user who
> installed the client software from home and he was issued
> a temporary license. When his 90 days expired, the server
> did not issue him a permanent license. I thought maybe the
> problem was we were out of licenses. Well after installing
> on my pc at home and not connecting, I checked the
> licenses on the server and my pc was issued a permanent
> license. Microsoft troubleshooting stated I could up the
> concurrent connections but the setting is already at
> unlimited connections. Does anyone know something I could
> try or the resolution to this? The other user is also
> getting the same message about closing the connection.
>
> Thanks,
>
> E. Rea

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)

The two client pcs have Windows XP Pro and Windows 98. I
checked out the event log on the server and found the
following event, I'm not sure if this is directly related
to my problem but it sure sounds like it:

Event 38

Can't generate a license for client because of error.
Can't add certificate to store (error c0010020)

Any thoughts?


>-----Original Message-----
>Is there anything in the EventLog on the TS when you try
to connect?
>Which OS do you run on your client PC?
>
> --
>Vera Noest
>MCSE,CCEA, Microsoft MVP - Terminal Server
>http://hem.fyristorg.com/vera/IT
>*----------- Please reply in newsgroup -------------*
>
>"E Rea" <anonymous@discussions.microsoft.com> wrote in
>news:8aa101c4329d$5e434e20$a001280a@phx.gbl:
>
>> We use Terminal services on a server running Windows
2000
>> Server. I have installed the client software on my pc
at
>> home. When I try to open the connection, a message
comes
>> back saying terminal server has closed the connection.
I
>> was checking the service because I had another user who
>> installed the client software from home and he was
issued
>> a temporary license. When his 90 days expired, the
server
>> did not issue him a permanent license. I thought maybe
the
>> problem was we were out of licenses. Well after
installing
>> on my pc at home and not connecting, I checked the
>> licenses on the server and my pc was issued a permanent
>> license. Microsoft troubleshooting stated I could up
the
>> concurrent connections but the setting is already at
>> unlimited connections. Does anyone know something I
could
>> try or the resolution to this? The other user is also
>> getting the same message about closing the connection.
>>
>> Thanks,
>>
>> E. Rea
>.
>

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)

This means that the license certificate has been corrupted. Try
deleting the license from the client (HKLM\Software\Microsoft
\MSLicensing). If this doesn't work, you may have to deactivate
and reactivate the license server.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

<anonymous@discussions.microsoft.com> wrote in news:b4bf01c43757
$bcbc8390$a001280a@phx.gbl:

> The two client pcs have Windows XP Pro and Windows 98. I
> checked out the event log on the server and found the
> following event, I'm not sure if this is directly related
> to my problem but it sure sounds like it:
>
> Event 38
>
> Can't generate a license for client because of error.
> Can't add certificate to store (error c0010020)
>
> Any thoughts?
>
>
>>-----Original Message-----
>>Is there anything in the EventLog on the TS when you try
> to connect?
>>Which OS do you run on your client PC?
>>
>> --
>>Vera Noest
>>MCSE,CCEA, Microsoft MVP - Terminal Server
>>http://hem.fyristorg.com/vera/IT
>>*----------- Please reply in newsgroup -------------*
>>
>>"E Rea" <anonymous@discussions.microsoft.com> wrote in
>>news:8aa101c4329d$5e434e20$a001280a@phx.gbl:
>>
>>> We use Terminal services on a server running Windows
> 2000
>>> Server. I have installed the client software on my pc
> at
>>> home. When I try to open the connection, a message
> comes
>>> back saying terminal server has closed the connection.
> I
>>> was checking the service because I had another user who
>>> installed the client software from home and he was
> issued
>>> a temporary license. When his 90 days expired, the
> server
>>> did not issue him a permanent license. I thought maybe
> the
>>> problem was we were out of licenses. Well after
> installing
>>> on my pc at home and not connecting, I checked the
>>> licenses on the server and my pc was issued a permanent
>>> license. Microsoft troubleshooting stated I could up
> the
>>> concurrent connections but the setting is already at
>>> unlimited connections. Does anyone know something I
> could
>>> try or the resolution to this? The other user is also
>>> getting the same message about closing the connection.
>>>
>>> Thanks,
>>>
>>> E. Rea