remote desktop locking out local user

HI,
After I remote to various machines on my network, users
will call to say they can't log in locally, that the
error says something about only an administsrtor can log
in, or that they don't have the rights to login. I have
them reboot, but what a pain in the butt? Why does the
terminal service not TERMINATE? It's as if I'm still
conected to their PC as admin, and it takes a reboot to
terminate the connection. (Or someone with admin rights
to unlock the PC. I've searched the knowledgebase - any
suggestions?
Thanks,
Lissa

Do you logout versus disconnect?

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...

"Lissa" <anonymous@discussions.microsoft.com> wrote in message
news:e61401c3f0f7$9cc991f0$a301280a@phx.gbl...
> HI,
> After I remote to various machines on my network, users
> will call to say they can't log in locally, that the
> error says something about only an administsrtor can log
> in, or that they don't have the rights to login. I have
> them reboot, but what a pain in the butt? Why does the
> terminal service not TERMINATE? It's as if I'm still
> conected to their PC as admin, and it takes a reboot to
> terminate the connection. (Or someone with admin rights
> to unlock the PC. I've searched the knowledgebase - any
> suggestions?
> Thanks,
> Lissa

Yes, I log off when I'm done. I would only disconnect if I needed services to continue running as admin with no interruption, correct? It doesn't happen all the time, but with over 200 Users, I want to return the PC to a usable state, back at the ctrl-alt-del screen
To have them call in that they are refused entry on the PC, and that they have to literally shut off the PC to get back in, is inconvienent and time consuming for both parties
Thanks,
Lissa