Re: Newbie: "You do not have access to logon....."

From: Vera Noest [MVP] (Vera.Noest_at_remove-this.hem.utfors.se)
Date: 08/11/04


Date: Wed, 11 Aug 2004 05:42:50 -0700

No, you don't need a LS yet. Not *all* connection problems are
license-related, although it certainly seems so, if you read the
newsgroups :-)

This sounds more like a permission problem.
Have you made your users members of the local Remote Desktop Users
group?

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

John <John@NoSpam_SensorySIMS.com> wrote in
news:vctih01astha2168be2sbupjpfaljs3ct4@4ax.com:

>
> We recently setup a new W2K3 Standard server. Played with
> Remote Desktop access without a hitch. Successfully logged in
> with both RD Client and RD Web from variety of client Windows
> PCs. We've been only using the local Administrator account
> during our early stages.
>
> Then we turned on TS in the server, everything looks good. We
> have not setup the LS yet, figuring we had 120 days grace.
>
> We can't get past "You do not have access to Logon to this
> session".
>
> What are we missing?
>
> Do we have to have a LS up and running during the 120 day grace?
>
> Any comments are appreciated.
>
> John@NoSpam_SensorySIMS.com
> (please remove "NoSpam_" from return address to respond
> directly)



Relevant Pages

  • where are sshd log files located?
    ... but recently I started having connection problems from my work ... I am trying to locate the ssh server's ... laptop to the server within my home network. ... firewall/router but port forwarding is enabled. ...
    (SSH)
  • Re: SuperSocker Bind Failed on port TCP:1433 Error
    ... > We have a lot of connection problems lately. ... Bind failed on TCP port 1433. ... > We have a couple of IP Addresses configured on that server for SSL ... > the last entry is the SuperSocket Info: Bind failed on TCP port 1433. ...
    (microsoft.public.sqlserver.server)
  • Re: TcpClient read/write timeouts do not timeout
    ... read/write problems or connection problems? ... The server sees the connection. ... Writeshould end because there's NO server and because the timeout ...
    (microsoft.public.dotnet.languages.csharp)
  • Synchronisation Problems
    ... Our clients are consistantly having connection problems, with connections dropping and not reconnecting, delays, outlook claiming to be not responding etc. ... Server is not as yet running antis as it is a fresh install still and has never behaved. ... We had the same issue with a trial version of Win2k3 and Exchange 2k2 combo. ...
    (microsoft.public.exchange.clients)