Re: Xp Client cannot connect to TS.

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Rich (Rich_at_discussions.microsoft.com)
Date: 08/20/04 

Date: Thu, 19 Aug 2004 20:09:02 -0700

This did not resolve the problem.
I checked the KB but there was nothing that helped.
I can make the RDC connection only by deleting the MSLicensing key every
morning.
They can work all day long remotely but if they log off they cannot
reconnect without deleting the MSLicensing key.
Is there anyway the remove all licenses from the TS and allow all users to
reconnect and the TS issue the licenses to the users again?
I am desperate.
Help!!

"Cláudio Rodrigues" wrote:

> The issue is licensing. Check the TS event log.
> You may need to hard code the licensing server on the TS registry.
> Also check the Microsoft KB as they may be a hotfix for that (as the
> licensing server is really flaky. :-).
>
> --
> Cláudio Rodrigues
>
> Microsoft MVP
> Windows Technologies - Terminal Services
> http://www.terminal-services.net
> "Rich" <Rich@discussions.microsoft.com> wrote in message
> news:587099BF-2FA8-449B-B8FF-0D53EA92F074@microsoft.com...
> > Two of my XP Pro remote clients computers at different locations were
> > working
> > fine using TS to connect remotely to 2003 server. The next day they they
> > could not connect to the 2003 server.
> > They received the following error message:
> > The client could not establish a connection to the remote computer
> > The most likely cause for this error are:
> > 1. Remote connections might not be enabled at the remote computer
> > 2. The maximum number of connections was exceeded at the remote computer
> > 3. A network error occurred while establishing the connection
> >
> > I checked the licenses on the 2003 server and there are extra device cals
> > available.
> > Other users at different locations can connect to the same TS without any
> > problems.
> > I ran scans for viruses and spywae on the two client machines. There were
> > no
> > viruses and very few spyware.
> > The XP client still could not connect to the TS server.
> > I did some research and found an article suggesting to delete the
> > "msLicensing" key in the XP Pro client registry.
> > HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSLicensing.
> > I was able to connect to the TS server and it worked fine after deleting
> > the
> > MSLicensing key..
> > When i logged off of the TS server, it would not allow me to reconnect
> > again. I received the same error message above.
> > If i go back in the registry and delete the MSLicensing key it would
> > connect
> > again.
> > Could someone help me to resolve this issue?
> > Thank You.
> >
> >
> >
>
>
>

Relevant Pages

  • Re: Account keeps locking out
    ... As far as deleting a user profile is concerned, ... the server kept on locking him out. ... Client accesses the internet via the server, ...
    (microsoft.public.windows.server.sbs)
  • Information on unexpected Runtime issue
    ... I recently finished a system in Access 2003 for a client and loaded it ... onto their server. ... to any other they received a run time error and the application ... I managed to solve the problem by deleting and re-creating the ...
    (comp.databases.ms-access)
  • RE: Licensing Protocol Error
    ... I've tried deleting the mslicensing key on the client and various ... suggested keys on the server. ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Strange nfs problem - Connection refused
    ... after deleting this parameter all works fine. ... Is that on the server or the client? ... the reason your client can't connect. ...
    (comp.os.linux.networking)
  • Re: Firey exchange death...
    ... Server MAPI Editor window. ... Once logged in, click MDB, and select Get Mailbox Table. ... queue directory. ... deleting, other than comparing the file sizes. ...
    (microsoft.public.exchange.admin)