Problem with local policy while connecting to a terminal server

[robert]

Hi all,

I would have posted this under win2003 terminal services .. but there
is no such group, but I figured this was as good.

I have win2003 standard server (MachineA) into which I normally connect
remotely via terminal services. I normally use the administrator
account, which worked fine. This was until we intalled SBS, on another
machine(MachineB), and added MachineA to the domain. I was then still
able to logon to terminal services, but only with the domain admin
account, not the machine local admin account. When I try and logon with
MachineA's local account, I get the infamous "The local policy of this
system does not permit you to logon interactively." message.

I have subsequently removed "MachineA" from the domain, and switched
off the SBS server (it was causing DNS problems which I didn't have
time to sort out). We re-instated the old DHCP/DNS server, and
everything else seems to be working, except that we still cannot logon
to MachineA via TS, receiving the same error blurb about local
policies.

I have checked the local security policy of MachineA and the
administrator group is still included under "Allow logon through
termincal services". I even tried to add the administrator user
directly without any success.

I'm guessing that adding "MachineA" to the domain has messed with
something, as this was when the problem started, the question is ..
"WHAT".

Please help, this is getting nasty, and I think I'm about to be lynched
by the developers, as this is a server they access regularily.

Robert

 

[Vera Noest [MVP]]

Have you checked membership of the local Remote Desktop Users group
on the TS?
And checked the rdp-tcp connection permissions? You could try to
set them back to the default permissions.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

(e-mail address removed) wrote on 07 jun 2006 in
microsoft.public.win2000.termserv.clients:

 

[robert]

Hi Vera,

I solved the problem - the local security policy was set up to deny
terminal services access to the administrator group (must have been
something that adding to the domain did)

Thanks for your suggestions anyway, at least I've learned a little bit
more now

Robert

 

[Vera Noest [MVP]]

OK, I'm glad that you found the cause and that the problem is solved.
Thanks for reporting back here!
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*