Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.
One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.
Emergency: Windows Server 2003 logon then logoff how do I access the server
I'm having the same problem described here:
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_24681933.html
I have a windows server 2003 machine where when I logon it immediately logs me off.
The answer is to log into the server and use the remote registry to clear out a certain registry entry.
As I write this I'm at a clients office and have run into this. How do I log onto the server from one of the networked computers, since it logs me off as administrator immediately after I log in. The office opens in less than an hour. Safe mode and last known good gets the same result.
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_24681933.html
I have a windows server 2003 machine where when I logon it immediately logs me off.
The answer is to log into the server and use the remote registry to clear out a certain registry entry.
As I write this I'm at a clients office and have run into this. How do I log onto the server from one of the networked computers, since it logs me off as administrator immediately after I log in. The office opens in less than an hour. Safe mode and last known good gets the same result.
Who is Participating?
LVL 2
Why not use regedit.exe on an another computer and use the file->connect network registry ? Then, point it at the server that isn't keeping your session logged on and edit the registry remotely.
I suspect its a virus I have seen some really nasty virus' that reside in protected system files and as a result a windows av suite cannot even find them let alone fix/remove them the only way is to use a linux av boot cd they are not quick mind you
see
http://www.techmixer.com/free-bootable-antivirus-rescue-cds-download-list/
see
http://www.techmixer.com/free-bootable-antivirus-rescue-cds-download-list/
Not a virus. I was trying to add a backup drive and I'm pretty sure the drive letters got screwed up in the registry. I put all the drives back where they were, removing the backup drive but still have the problem. That experts problem describes my problem to a tee. How do I get into the server registry? Is there anything I can do if I boot into the recovery console?
How do I get into RDP? I'm on another computer now, but it's trying to access the server's C drive and it keeps on coming up that the network place doesn't exist.
Is there any chance I could call someone to discuss this? Windows Server is not my baliwick and this is really an emergency.
Remote Desktop Connection.. specify the hostname of the machine and credentials with appropriate permissions.. like the local admin or domain admin. Or even a lesser account.
If the drive letters were messed up bad enough Windows wouldn't be able to load properly.
If the drive letters were messed up bad enough Windows wouldn't be able to load properly.
I'm trying to login using the same user, the adminstrator, that gets knocked out whenever I log in on the server console itself.
Not that I know of. I was just brought into this.
And anyway, wouldn't it logoff those users too.
Is there any way to remove the password?
I know under XP and Vista there are programs that can wipe the password.
Is there any way to do with Windows Server 2003
And anyway, wouldn't it logoff those users too.
Is there any way to remove the password?
I know under XP and Vista there are programs that can wipe the password.
Is there any way to do with Windows Server 2003
It doesn't sound like the password is the issue since it logs you on.
Have you tried using computer management from a different computer?
Start/Run/compmgmt.msc
Action/Connect to Another Computer
type in the IP address or host name of the server
Have you tried using computer management from a different computer?
Start/Run/compmgmt.msc
Action/Connect to Another Computer
type in the IP address or host name of the server
If the remote Registry service is running you could maybe accomplish it that way too. If your the one who has to connect to resolve an issue what does logging on any locally logged on users have to do with it? Unless I'm mistaken this is a server right?
This describes the problem:
http://support.microsoft.com/kb/249321
And this is part of the solution:
http://support.microsoft.com/kb/814590
I just have to figure out how to do it on this system.
http://support.microsoft.com/kb/249321
And this is part of the solution:
http://support.microsoft.com/kb/814590
I just have to figure out how to do it on this system.
remote Desktop admin mode should be enabled by default.. it allows up to two simultaneous connections. Do you have physical access to the box?
Yes. I just did this:
net use \\remote_machine_name\IPC$
But got this message:
Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed
net use \\remote_machine_name\IPC$
But got this message:
Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed
Just read here:
http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/f95e5f0b-9805-4583-a648-92c44b85c827
It discusses assigning drive letters using diskpart. I don't have a windows server 2003 disk. I do have XP Pro. I'm wondering if there's any way I can get into the recovery console using that and somehow assign C to the boot drive
http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/f95e5f0b-9805-4583-a648-92c44b85c827
It discusses assigning drive letters using diskpart. I don't have a windows server 2003 disk. I do have XP Pro. I'm wondering if there's any way I can get into the recovery console using that and somehow assign C to the boot drive
ubadmin's post 38710939 seems to agree with the resolution in your first link.
The only reason to perform the net use command is if the server is not in a domain.
The only reason to perform the net use command is if the server is not in a domain.
rmail, can you give me specific commands that will allow me to use remote registery on the computer I am on right now?
Do I do it from a command prompt?
How do I do "file->connect network registry ? "
Thanks,
Al
Do I do it from a command prompt?
How do I do "file->connect network registry ? "
Thanks,
Al
XP instructions:
1. Click Start
2. Click Run
3. Type "regedit" (without the quotes) and press enter
4. Click on File
5. Click on Connect Network Registry
6. Type in the name of the server and press enter
*** Next step very important to preven making changes to the local registry ***
7. Scroll down to the registry for the server and find the keys you need to alter
8. Make the alterations.
9. Close Regedit
1. Click Start
2. Click Run
3. Type "regedit" (without the quotes) and press enter
4. Click on File
5. Click on Connect Network Registry
6. Type in the name of the server and press enter
*** Next step very important to preven making changes to the local registry ***
7. Scroll down to the registry for the server and find the keys you need to alter
8. Make the alterations.
9. Close Regedit
found out how to do it. command prompt: regedit. Then I went to file under regedit and clicked on "connect network registry".
But then when I try to login as administrator, I get a message: "The object with the following name cannot be found"
Wait, I think I'm in. Not sure yet.
But then when I try to login as administrator, I get a message: "The object with the following name cannot be found"
Wait, I think I'm in. Not sure yet.
OK, so I changed the drive letter and now I can access that C drive through the network. But I still can't logon. I changed the
HKLM\Software\Microsoft\Wi
Settings. But I don't think I got it right.
I just used this:
Userinit = x:\windows\system32\userin
Same result. Couldn't login. Any ideas?
HKLM\Software\Microsoft\Wi
Settings. But I don't think I got it right.
I just used this:
Userinit = x:\windows\system32\userin
Same result. Couldn't login. Any ideas?
Finally got it.
I had tried to make C: the boot device per http://support.microsoft.com/kb/223188
But that was insane. Finally I found a forum where someone said to just delete all the \DosDevices\ in the registry and let windows reassign them. That did it. The boot drive was finally C: again. But then I ran back into the userinit problem in the registry.
My registry entry looked like this: Userinit = x:\windows\system32\userin
I just changed it to Userinit = C:\windows\system32\userin
I just tried to set up a backup drive in an old server (that I hadn't set up in the first place) and suddenly I was in for six hours of fun. If anyone knows how to swear off trying to fix ancient systems please let me know. There must be a support group for that.
Thanks to all.
Al
I had tried to make C: the boot device per http://support.microsoft.com/kb/223188
But that was insane. Finally I found a forum where someone said to just delete all the \DosDevices\ in the registry and let windows reassign them. That did it. The boot drive was finally C: again. But then I ran back into the userinit problem in the registry.
My registry entry looked like this: Userinit = x:\windows\system32\userin
I just changed it to Userinit = C:\windows\system32\userin
I just tried to set up a backup drive in an old server (that I hadn't set up in the first place) and suddenly I was in for six hours of fun. If anyone knows how to swear off trying to fix ancient systems please let me know. There must be a support group for that.
Thanks to all.
Al
" If anyone knows how to swear off trying to fix ancient systems please let me know. There must be a support group for that."
ROFL
If you find one please let the rest of us know.
Glad you got it working.
ROFL
If you find one please let the rest of us know.
Glad you got it working.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
