RE: "You do not have access to logon to this Session" from remote



All,

Apparently today MS fixed the license clearinghouse, I was able to get W2K3
TS licenses issued, installed, TSLS running on W2K3 member server, however,
this did not fix my problem. Ideas??

I've done this:

On my W2K domain controller which was my primary TSLS, I stopped the LS
service, then added the registry key pointing the discovery of the LS to one
of my W2K3 member servers where I added my W2K3 TS client licenses (registry
change on W2K DC per 239107 ( http://support.microsoft.com/kb/239107/ )
Establishing preferred Windows 2000 Terminal Services license server). This
per the suggestions I need a W2K3 TSLS which can serve licenses for both the
W2K and W2K3 servers.

After this, on both the original W2K DC (no LS running) and member servers,
my single W2K3 LS is discovered by all systems by using the TSLS admin tool,
however I still get the same "You do not have access to logon to this
Session" after logging in remotely.

How can I trace the true cause of the problem? Is this best answered by a
MS support call?

Many thanks to all who have helped!

Ronan M


"Patrick Rouse" wrote:

> Is your TSLS on a 2000 Server? If yes, then 2003 terminals servers can't
> recognize that server, as they require a 2003 TSLS.
>
> http://www.workthin.com/tsls2k3.htm
>
>
> --
> Patrick Rouse
> Microsoft MVP - Terminal Server
> http://www.workthin.com
>
>
> "Ronan M" wrote:
>
> > Hello,
> >
> > I have a small W2K AD domain and W2K/W2K3 member servers. My DC has the TS
> > license server. After having upgraded DC and member servers to (nearly) the
> > latest critical service packs / hotfixes, and subsequently installing Citrix
> > presentation server 4.0 in my domain, I have been unable to remotely connect
> > using TS, getting the error dialog above after I login using GINA as domain
> > admin or any other user.
> >
> > I do not have any GPOs I have explicitly added that would affect TS access,
> > I suspect if anything either Citrix installation caused an issue or by
> > incorrectly installing software on a member TS server (eg by not using
> > add/remove programs or the change user/install in cmd shell) I inadvertently
> > caused this myself.
> >
> > In any case I've tried deactivating and reactivating my TS license server.
> > On a member TS server (w2K3) I'm trying to access, I get this in system event
> > log:
> >
> > Event Type: Warning
> > Event Source: TermService
> > Event Category: None
> > Event ID: 1010
> > Date: 7/14/2005
> > Time: 1:17:36 PM
> > User: N/A
> > Computer: myW2K3server
> >
> > Description:
> > The terminal server could not locate a license server. Confirm that all
> > license servers on the network are registered in WINS/DNS, accepting network
> > requests, and the Terminal Server Licensing Service is running.
> >
> > However, I know the license server can be seen and DNS is OK. Using the
> > domain admin account to logon remotely I should think this should work but to
> > be sure I added domain admin and other users to the RDP-Tcp connection
> > Permissions settings tab in TS configuration (still no luck).
> >
> > Using the TS license admin tool on the member server -- this tool "sees" the
> > license server (DC) with the licenses (unissued/used).
> >
> > During the course of my attempts to repair I may have damaged things further
> > by changing the licensing type from one type to another just to see if I
> > could get it working - I now have it set to per-User.
> >
> > How can I trace this issue to determine the problem? Is there a registry
> > setting that might help?
> >
> > Could the TS licence server (on DC) have a corrupt database? If so, how to
> > tell, and how to reset?
> >
> > THANK YOU
> > Ronan
> >
> >
> >
.



Relevant Pages

  • Re: Terminal Server Complains No License Server, but License Server Says,"Yes, I gave out Licenses"
    ... servers do not automatically discover a license server that is ... on second connection you get a permanent ... > there is no TSLS, and that the grace period is going to expire. ...
    (microsoft.public.windows.terminal_services)
  • Re: License for a member server
    ... Make sure that the SBS 2003 server is the Licensing Computer. ... click License Site Settings. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: "You do not have access to logon to this Session" from remote
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... > to get W2K3 TS licenses issued, installed, TSLS running on W2K3 ... > preferred Windows 2000 Terminal Services license server). ... If yes, then 2003 terminals ...
    (microsoft.public.windows.terminal_services)
  • Re: How to add a user with very limited rights
    ... The Windows Server 2003 External Connector license is an optional ... An EC license is not applicable to Web Edition or Windows Small Business ... For more information about External Connector License, ...
    (microsoft.public.windows.server.sbs)
  • Re: Shutdown hangs...
    ... Server shutdown operation is very slow and the SBS 2003 CAL Licenses ... >> license folder from scan. ... >> - An antivirus program deletes or quarantines the license store file. ...
    (microsoft.public.windows.server.sbs)