local policy doesn't permit logon interactively error

[jeff]

Hi, this is a repost of a message below, because I wasn't
getting a solution and people might have skipped over the
issue.

for you reference you can read the most recent chain of
messages below.

thanks for your posts!

----start message chain----------

yes,
it is a member of administrators, remote desktop users,
and users.

i don't intentionally have a firewall, but before i
upgraded from win 2k to win xp, i was running the free
version of zone alarm, a software firewall that i
uninstalled prior to installing xp.

any clue on how i can "lock" the host so it will accept
incoming connections? my shutdown menu only offers turn
off, stand by, or restart and my logoff menu only offers
switch user or logoff, when i ctrl-alt-del, i get task
manager, but no option to lock computer.

 

[Sooner Al]

That error is referenced in the XP Pro Resource Kit.

http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/pree_rem_ocqv.asp

This Google search result may help...

http://groups.google.com/groups?as_...SO-8859-1&as_ugroup=*.work_remotely&lr=&hl=en

 

[jeff]

thanks,
I followed all of the instructions listed there and it
still didn't work.

just for the sake of argument, I tried connecting the
other direction...from the desktop to the laptop. and
guess what? it worked completely.

so...what is it about my desktop that won't accept
incoming remote desktop connections? could it be that i
purchased the o/s from an, ahem, online auction? the one
on my laptop was oem with the system.

looks like i might need to fork over the dough for a new
version of XP for my desktop???

any ideas?

 

[David Jones]

Can you test this on the same LAN, with a known IP
address, and see if you get this error?

If you get this particular error, it means one of the
following:

The account you are using does not have a password (and
needs one to be able to log in via RD).

The account you are using is not a member of either the
Remote Desktop Users group or the Administrator group.

The account you are using does not have the "Allow logon
through Terminal Services" right (it must have this right
to log on via RD).

If you create another account and use that account to log
on, are you successful?

You can also open gpedit.msc, expand Computer
Configuration->Windows Settings->Security Settings->Local
Policies->User Rights Assignment, find "Allow logon
through Terminal Services" and add the account to see if
that was the problem.

 

[jeff is elated!]

David, you are my savior!

Just as you said, I needed to allow connection through
terminal services, and "whoosh" I was off to the remote
desktop races!
I don't know how I can possibly thank you enough, I have
been working on this issue for over 12 hours, and now it
is solved!!!

For anyone else in this situation, please follow David's
advice regarding setting the right to allow logon through
Terminal Services.

Yipee, now that I have RD working, I am a happy camper.

Thanks a million, David Jones. I owe you big, big, BIG
time!