[THIN] Re: MSTSC Issue

  • From: Greg Reese <gareese@xxxxxxxxx>
  • To: thin@xxxxxxxxxxxxx
  • Date: Fri, 17 Apr 2009 11:03:09 -0500

it's crazy how much I hear that lately.

On Fri, Apr 17, 2009 at 11:00 AM, <christopher.walter@xxxxxxx> wrote:

>  Yes your right, forgot in Windows 2003 “Allow logon to Terminal services”
> replaced the need for Allow logon locally for Terminal services.  Guess I
> secretly still wish I could go back to NT4.
>
>
>  ------------------------------
>
> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
> Behalf Of *Joe Shonk
> *Sent:* April 17, 2009 11:50 AM
>
> *To:* thin@xxxxxxxxxxxxx
> *Subject:* [THIN] Re: MSTSC Issue
>
>
>
> The “Allow logon locally” is console access only.
>
>
>
> Joe
>
>
>
> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
> Behalf Of *christopher.walter@xxxxxxx
> *Sent:* Friday, April 17, 2009 5:10 AM
> *To:* thin@xxxxxxxxxxxxx
> *Subject:* [THIN] Re: MSTSC Issue
>
>
>
> Check your user rights again.  Your users need access to “Allow logon to
> Terminal services” and “Allow logon locally”.  If this isn’t the issue then
> check the Eventlog for errors, possibly with the domain or network.
>
>
>
> Chris
>
>
>  ------------------------------
>
> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
> Behalf Of *Doug Rooney
> *Sent:* April 16, 2009 6:30 PM
> *To:* thin@xxxxxxxxxxxxx
> *Subject:* [THIN] MSTSC Issue
>
>
>
> Hello to all, this question is directed to my fellow MSTSC administrators,
> or anyone who might know the answer.
>
> I just built a new Windows 2003 server for a terminal server, it is in the
> same OU as the others, it is as far as I can tell an exact duplicate of
> server #2 except for the obvious, name, IP …
>
> The issue is, users can log into the other servers just fine, but if they
> try to log into the new server, they get that wonderful MS message telling
> them that they do not have permission to log into this server. Basically it
> reads: *"To log on to this remote computer, you must be granted the allow
> log on through terminal services right.  By default, members of the remote
> desktop users group have this right.  If you are not a member of the remote
> desktop users group or another group that  has this right, or if the remote
> desktop user group does not have this right, you must be granted this right
> manually."**
> *Well of course the users are part of the Remote Users Group, I have
> looked over the permissions very carefully, but do not find the problem, and
> of course Admins have no problem logging in.
>
>
>
> Any help would be very much appreciated.
>
> Thank You
>
> ~Doug Rooney
> Sonoma Tilemakers
> IT Manager
> 7750 Bell Rd.
> Windsor Ca, 95492
> (707) 837-8177 X11
> (707) 837-9472 FAX
> it@xxxxxxxxxxxxxxxxxxxx
>
>
>
> ************************************************
>
> For Archives, RSS, to Unsubscribe, Subscribe or set Digest or
>
> Vacation mode use the below link: //www.freelists.org/list/thin
>
> Follow ThinList on Twitter http://twitter.com/thinlist
>
> Thin List discussion is now available in blog format at:
> http://thinmaillist.blogspot.com
>
> Thinlist MOBILE Feed http://thinlist.net/mobile
>
> ************************************************
>
>
>
>
>
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>

Other related posts: