can't login, just returns back to name and password screen

I have a server that when I go to log in, I type the name and password, then
when I click OK, it just returns me to that screen with the password deleted.
it's not kicking back the message that either the username or password is
bad, just returns me to the login screen. Sadly the only way to log into it
is through the console, which it's not letting me do. Did a service maybe
get hosed and i need to power it down?

 

Hello Rich,

Try rebooting the server and try again, that may help

--
Isaac Oben [MCTIP:EA, MCSE]
"Rich" <Rich@discussions.microsoft.com> wrote in message
news:82BE3A6C-9BB9-452F-984B-F2CF9848B248@microsoft.com...
>I have a server that when I go to log in, I type the name and password,
>then
> when I click OK, it just returns me to that screen with the password
> deleted.
> it's not kicking back the message that either the username or password is
> bad, just returns me to the login screen. Sadly the only way to log into
> it
> is through the console, which it's not letting me do. Did a service maybe
> get hosed and i need to power it down?

 

The prior administrator of the server disabled the shutdown from the login
screen, so i'll have to ungracefully shut it down :-( I can't think of
anything else to do though.

"Isaac Oben [MCITP,MCSE]" wrote:

> Hello Rich,
>
> Try rebooting the server and try again, that may help
>
> --
> Isaac Oben [MCTIP:EA, MCSE]
> "Rich" <Rich@discussions.microsoft.com> wrote in message
> news:82BE3A6C-9BB9-452F-984B-F2CF9848B248@microsoft.com...
> >I have a server that when I go to log in, I type the name and password,
> >then
> > when I click OK, it just returns me to that screen with the password
> > deleted.
> > it's not kicking back the message that either the username or password is
> > bad, just returns me to the login screen. Sadly the only way to log into
> > it
> > is through the console, which it's not letting me do. Did a service maybe
> > get hosed and i need to power it down?
>
>

 

"Rich" <Rich@discussions.microsoft.com> wrote in message
news:EC9EB587-7F6E-4EB5-9E6E-2B1EAD4385B3@microsoft.com...
> The prior administrator of the server disabled the shutdown from the login
> screen, so i'll have to ungracefully shut it down :-( I can't think of
> anything else to do though.

No he didn't. That is the way the Server OS's are. The workstation OS's
are the opposite.

Why not try a different account?

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

 

I've tried 6 different accounts, both local and domain, and all of them
behave the same way as if something is wrong with the login process. you
click ok after typing in your name and password, then it just returns you
right back to that screen, but without the password.

"Phillip Windell" wrote:

> "Rich" <Rich@discussions.microsoft.com> wrote in message
> news:EC9EB587-7F6E-4EB5-9E6E-2B1EAD4385B3@microsoft.com...
> > The prior administrator of the server disabled the shutdown from the login
> > screen, so i'll have to ungracefully shut it down :-( I can't think of
> > anything else to do though.
>
> No he didn't. That is the way the Server OS's are. The workstation OS's
> are the opposite.
>
> Why not try a different account?
>
> --
> Phillip Windell
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
>

 

"Rich" <Rich@discussions.microsoft.com> wrote in message
news:82BE3A6C-9BB9-452F-984B-F2CF9848B248@microsoft.com...
>I have a server that when I go to log in, I type the name and password,
>then
> when I click OK, it just returns me to that screen with the password
> deleted.
> it's not kicking back the message that either the username or password is
> bad, just returns me to the login screen. Sadly the only way to log into
> it
> is through the console, which it's not letting me do. Did a service maybe
> get hosed and i need to power it down?

This almost always happens when the machine is unable to locate the file
userinit.exe, either because it is not where it should be or because the
registry reference pointing to it is incorrect. Here is how you can fix it:
1. Working from a networked machine, open the server's registry and check
this key:
HKLM/Software/Microsoft/Windows NT/Current Version/Winlogon/Userinit
Does it point to c:\Windows\system32?
2. Run a console session (cmd.exe) from a networked machine, using
psexec.exe (www.sysinternals.com).
3. Make a note of the system drive letter. What is it? Drive F: perhaps?
4. Does the file F:\windows\system32\userinit.exe exist?
5. If the system drive letter is something other than C:, do this:
6. Open the server's registry and navigate here:
HKLM\SYSTEM\MountedDevices
7. Rename DosDevices\F: to DosDevices\C:. If DosDevices\C: already exists,
rename it to a free drive letter.
8. Reboot the machine.

Note that basic cause of the problem is either due to malware/virus action
or to partition manipulation. If you have not manipulated your partitiones
in some way then you must check the machine for malware.

 

Thanks Pegasus, I will check this stuff out.

If the file is there and all that, is there anything outside of a reboot
that would reinitialize the login process, like restarting a service or
something? The users aren't having any problems accessing resources on the
server, its just we can't actually log onto the server itself.

"Pegasus [MVP]" wrote:

>
> "Rich" <Rich@discussions.microsoft.com> wrote in message
> news:82BE3A6C-9BB9-452F-984B-F2CF9848B248@microsoft.com...
> >I have a server that when I go to log in, I type the name and password,
> >then
> > when I click OK, it just returns me to that screen with the password
> > deleted.
> > it's not kicking back the message that either the username or password is
> > bad, just returns me to the login screen. Sadly the only way to log into
> > it
> > is through the console, which it's not letting me do. Did a service maybe
> > get hosed and i need to power it down?
>
> This almost always happens when the machine is unable to locate the file
> userinit.exe, either because it is not where it should be or because the
> registry reference pointing to it is incorrect. Here is how you can fix it:
> 1. Working from a networked machine, open the server's registry and check
> this key:
> HKLM/Software/Microsoft/Windows NT/Current Version/Winlogon/Userinit
> Does it point to c:\Windows\system32?
> 2. Run a console session (cmd.exe) from a networked machine, using
> psexec.exe (www.sysinternals.com).
> 3. Make a note of the system drive letter. What is it? Drive F: perhaps?
> 4. Does the file F:\windows\system32\userinit.exe exist?
> 5. If the system drive letter is something other than C:, do this:
> 6. Open the server's registry and navigate here:
> HKLM\SYSTEM\MountedDevices
> 7. Rename DosDevices\F: to DosDevices\C:. If DosDevices\C: already exists,
> rename it to a free drive letter.
> 8. Reboot the machine.
>
> Note that basic cause of the problem is either due to malware/virus action
> or to partition manipulation. If you have not manipulated your partitiones
> in some way then you must check the machine for malware.
>
>
>

 

"Rich" <Rich@discussions.microsoft.com> wrote in message
news:A85BBA88-8B79-4032-B47E-4D82F8ED0AA9@microsoft.com...
> Thanks Pegasus, I will check this stuff out.
>
> If the file is there and all that, is there anything outside of a reboot
> that would reinitialize the login process, like restarting a service or
> something? The users aren't having any problems accessing resources on
> the
> server, its just we can't actually log onto the server itself.

Sorry, you will have to reboot the machine. There is a weekend coming -
plenty of opportunities!

 

That's what I figured.

If only my company was a M-F , we're 7 days a week, 20 hours a day. no
sleep for the weary, haha. thanks for the help. everything checked out ok,
looks like it just needs a reboot. hopefully a psshutdown reboots it
gracefully.

"Pegasus [MVP]" wrote:

>
> "Rich" <Rich@discussions.microsoft.com> wrote in message
> news:A85BBA88-8B79-4032-B47E-4D82F8ED0AA9@microsoft.com...
> > Thanks Pegasus, I will check this stuff out.
> >
> > If the file is there and all that, is there anything outside of a reboot
> > that would reinitialize the login process, like restarting a service or
> > something? The users aren't having any problems accessing resources on
> > the
> > server, its just we can't actually log onto the server itself.
>
> Sorry, you will have to reboot the machine. There is a weekend coming -
> plenty of opportunities!
>
>
>

 

"Rich" <Rich@discussions.microsoft.com> wrote in message
news4C472FB-7D06-4623-9B96-F6086DCE4081@microsoft.com...
> That's what I figured.
>
> If only my company was a M-F , we're 7 days a week, 20 hours a day. no
> sleep for the weary, haha. thanks for the help. everything checked out
> ok,
> looks like it just needs a reboot. hopefully a psshutdown reboots it
> gracefully.

Psshutdown is a great tool. On the other thand you now have a native tool,
shutdown.exe, to reboot your server. And don't count your chickens before
they're hatched!

By the way, did you isolate the problem? Incorrect system drive letter?

 

I always forget about the baked-in shutdown.exe, so used to psshutdown.

The file was there and located at the correct path according to the
registry. The event logs didnt say anything really other than a machine
check event. I did notice the server has been up for a LONG time, maybe
something just got hosed.

"Pegasus [MVP]" wrote:

>
> "Rich" <Rich@discussions.microsoft.com> wrote in message
> news4C472FB-7D06-4623-9B96-F6086DCE4081@microsoft.com...
> > That's what I figured.
> >
> > If only my company was a M-F , we're 7 days a week, 20 hours a day. no
> > sleep for the weary, haha. thanks for the help. everything checked out
> > ok,
> > looks like it just needs a reboot. hopefully a psshutdown reboots it
> > gracefully.
>
> Psshutdown is a great tool. On the other thand you now have a native tool,
> shutdown.exe, to reboot your server. And don't count your chickens before
> they're hatched!
>
> By the way, did you isolate the problem? Incorrect system drive letter?
>
>
>

 

"Rich" <Rich@discussions.microsoft.com> wrote in message
news:B3202A45-4AF9-431B-A5D0-CA17EC4F8D55@microsoft.com...
>I always forget about the baked-in shutdown.exe, so used to psshutdown.
>
> The file was there and located at the correct path according to the
> registry. The event logs didnt say anything really other than a machine
> check event. I did notice the server has been up for a LONG time, maybe
> something just got hosed.
>

I assume your problem is now resolved.

 

Not yet, still waiting for a window to restart it

"Pegasus [MVP]" wrote:

>
> "Rich" <Rich@discussions.microsoft.com> wrote in message
> news:B3202A45-4AF9-431B-A5D0-CA17EC4F8D55@microsoft.com...
> >I always forget about the baked-in shutdown.exe, so used to psshutdown.
> >
> > The file was there and located at the correct path according to the
> > registry. The event logs didnt say anything really other than a machine
> > check event. I did notice the server has been up for a LONG time, maybe
> > something just got hosed.
> >
>
> I assume your problem is now resolved.
>
>
>