Re: "Classic logon" screen in XP does not remeber the user name

John.

Yes that is the behavior to be expected when you use RDP to access a Windows
XP Pro workstation [not for W2003 Server though]. Usually if I do that I get
a notice that a user is currently logged on and I will log them off or lock
their session [can't remember which one] if I logon with RDP.

Steve


"John N" <JohnN@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7A0A261F-E663-4426-9FB4-17224175C1EA@xxxxxxxxxxxxxxxx
Hi Steven:

Thanks for your reply. Usually I get automatic notificaton of your
responses, and this time I did not, so I am sorry that there has been a
few
days lapse here. I probably forgot to mark the "Notify me of replies" box
last time.

I checked the setting you mentioned, and it does not appear that is the
problem, as there was no check in that box at all. When I am at the
server,
and log onto a workstation, that workstation immediately goes to a locked
login screen. During that time, you can work from the server and access
that
workstation, but you cannot have a person on the server and a person on
the
workstation at the same time. I assumed that you could have concurrent
usage
like you can in PCAnywhere, but it does not appear to be the case with
Remote
Desktop. So perhaps, there is no problem at all, but just the way it is
designed to work.

Thanks again for your help.



--
John N


"Steven L Umbach" wrote:

The screensaver is probably configured to lock the computer after a
period
of idle time as a security measure if a user did not manually lock the
computer using Control-Alt-Delete - lock computer. Try going to Control
Panel/display - screen saver and uncheck "on resume password protect".

Steve


"John N" <JohnN@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8F96E4AE-9E8C-4477-8C83-926FA752221D@xxxxxxxxxxxxxxxx
Steven:

Once again, your suggestions worked just fine. Thanks.

As a follow up, after I logged onto the workstation from the server,
and
then logged off, I went to the workstation. There was a message on it
that
the workstation was locked and could only be unlocked by the
administrator.
This message however, does not show up on the server when I log onto
the
server from my home. So there must be a setting that I could change so
my
workstation does not "lock".

Again, any help you could give would be most appreciated.

John N
--
John N


"Steven L Umbach" wrote:

Hi John.

To access a computer via RDP you need the user right for allow logon
through
Terminal Services on the computer you are trying to access. Try adding
your
user account to the Remote Desktop Users group which should show as
being
included for the user right for allow logon through terminal services.
You
could also try adding your user account to that user right. Note that
sever
user right have a corresponding "deny" user right and these override
an
"allow" user right so make sure that there are no users/groups listed
in
deny logon through Terminal Services that could be causing you to get
that
message. When you are done configuring Local Security Policy run the
command
gpupdate /force on your server.

Steve


"John N" <JohnN@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:399F56C1-6625-4A1E-AE87-03EF58C37372@xxxxxxxxxxxxxxxx
Hi Steven:

Thank you very much, your suggestion worked just fine. In
retrospect,
I
think that I turned changed that feature myself, and didn't know
that
would
be the subsequent result. I was trying to configure a remote
desktop
connection. Would you be willing to help me with that, since you
seem
to
know about the "interactive" features?

If so, here goes.

I have a home computer and connect to my office computer via "Remote
Desktop". My office computer is a server, and it manages about 6
workstations. What I was trying to do, was to connect to the office
server,
and then, activate the "Remote Desktop" on the server, to get to the
workstations. I almost made it, as I get to the login screen of the
workstation, but when I try to login, it gives me the error,

"Local security policy does not allow interactive login on this
machine".

So that is why I was working with the "interactive" settings in the
security
policy, which I then turned off the feature to retain the last used
user
login name.

If you have any ideas about how to get past my security policy not
allowing
the interactice login, I would appreciate it.

Best regards

John N
--
John N


"Steven L Umbach" wrote:

There is a setting in security policy that controls that. You can
open
Local
Security Policy via secpol.msc and go to local policies/security
options -
interactive logon: do not display last user name. If you set that
to
disabled you should se the last logon name again. If you can not
change
that
setting that means it is being enforced by a domain level Group
Policy.

Steve


"John N" <JohnN@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:24D9AF93-C4B9-4293-A809-DE98799F66E9@xxxxxxxxxxxxxxxx
I am using Windows XP Pro SP2. My workstation is part of a local
network
and
the Administrator "user name" is password protected. I use the
classic
view.

When I boot my computer or change users, it comes back up with a
"Log
on
to
Windows" screen, asking for a user name and a password. In the
past,
the
user name of "Administrator" would be remembered, and all I would
have
to
do
is type in the password, and continue. Now, it does not remember
the
user
name, and the user name and password fields are both blank.

I would like to get back to it retaining the user name last used.

The only thing I have done with my computer recently, is I tried
to
set
up
a
VPN connection, which I could not get to work. So perhaps it
might
be
something with that?

Thanks for any help you can give.
--
John N











.

Relevant Pages