EMERGENCY - Unable to Log into a Windows 2003 standard server

Our company has a Windows 2003 standard server and we were having some
problems with the Internet. There were some modifications made by an
assistant of mine. When we rebooted the server, it takes long time
connecting to the network. When the Login screen appears in the screen I
login as administrator to the local machine, the domain, etc and this is what
happens. As soon as I hit the enter key it looks as if the profile was being
loaded into the system but in a short period of time the Login screen appears
again.

I try to log into the system using the safe mode and the encountered the
same thing. I tried to use the last good known configuration and the same
outcome.

This is an emergency please help me how to solve this problem.

Thank you in advance for your help!

See if you can access it from another computer on the network via Computer
Management to view the event logs to see if the problem is reported. Ask the
assistant what he did for any clues. If the user logging on does not have
proper ntfs permissions to the user profile or system files behavior such as
you see can happen. You might be able to view and change ntfs permissions
remotely. Check that system and administrators have full control to the
\winnt folder structure and that the administrator has full permissions to
his profile folder. Also check that there are not "deny" permissions for the
everyone or users groups.

Other possibilities are a virus infection. You can use msinfo32 and Under
view you can select remote computer. Then you can view services and
processes on the remote computer. If you have network access to the computer
you can use the psexec tool from SysInternals to access it's command prompt
remotely where you might be able to run a virus detection and removal tool
such as McAfee Stinger or Trend Micro Sysclean [with the pattern file] after
you copy them over via the administrator share. If you do not have any
remote access, using Recovery Console may be an option to attempt repairs
starting with checkdsk. --- Steve

http://www.sysinternals.com/ntw2k/freeware/psexec.shtml -- Psexec
http://vil.nai.com/vil/stinger/ -- McAfee Stinger
http://www.trendmicro.com/download/dcs.asp -- Trend Micro Sysclean
http://support.microsoft.com/default...;EN-US;q249321 -- another
potential fix?
http://support.microsoft.com/default...b;en-us;229716 -- Recovery
console

"DMI" <(E-Mail Removed)> wrote in message
news6317C6A-A5A6-42AF-9604-(E-Mail Removed)...
> Our company has a Windows 2003 standard server and we were having some
> problems with the Internet. There were some modifications made by an
> assistant of mine. When we rebooted the server, it takes long time
> connecting to the network. When the Login screen appears in the screen I
> login as administrator to the local machine, the domain, etc and this is
> what
> happens. As soon as I hit the enter key it looks as if the profile was
> being
> loaded into the system but in a short period of time the Login screen
> appears
> again.
>
> I try to log into the system using the safe mode and the encountered the
> same thing. I tried to use the last good known configuration and the same
> outcome.
>
> This is an emergency please help me how to solve this problem.
>
> Thank you in advance for your help!
>

I am not able to connect from another computer. I can't even ping the
server's IP from another computer. Any other ideas?

Thank you very much for your help!

"Steven L Umbach" wrote:

> See if you can access it from another computer on the network via Computer
> Management to view the event logs to see if the problem is reported. Ask the
> assistant what he did for any clues. If the user logging on does not have
> proper ntfs permissions to the user profile or system files behavior such as
> you see can happen. You might be able to view and change ntfs permissions
> remotely. Check that system and administrators have full control to the
> \winnt folder structure and that the administrator has full permissions to
> his profile folder. Also check that there are not "deny" permissions for the
> everyone or users groups.
>
> Other possibilities are a virus infection. You can use msinfo32 and Under
> view you can select remote computer. Then you can view services and
> processes on the remote computer. If you have network access to the computer
> you can use the psexec tool from SysInternals to access it's command prompt
> remotely where you might be able to run a virus detection and removal tool
> such as McAfee Stinger or Trend Micro Sysclean [with the pattern file] after
> you copy them over via the administrator share. If you do not have any
> remote access, using Recovery Console may be an option to attempt repairs
> starting with checkdsk. --- Steve
>
> http://www.sysinternals.com/ntw2k/freeware/psexec.shtml -- Psexec
> http://vil.nai.com/vil/stinger/ -- McAfee Stinger
> http://www.trendmicro.com/download/dcs.asp -- Trend Micro Sysclean
> http://support.microsoft.com/default...;EN-US;q249321 -- another
> potential fix?
> http://support.microsoft.com/default...b;en-us;229716 -- Recovery
> console
>
> "DMI" <(E-Mail Removed)> wrote in message
> news6317C6A-A5A6-42AF-9604-(E-Mail Removed)...
> > Our company has a Windows 2003 standard server and we were having some
> > problems with the Internet. There were some modifications made by an
> > assistant of mine. When we rebooted the server, it takes long time
> > connecting to the network. When the Login screen appears in the screen I
> > login as administrator to the local machine, the domain, etc and this is
> > what
> > happens. As soon as I hit the enter key it looks as if the profile was
> > being
> > loaded into the system but in a short period of time the Login screen
> > appears
> > again.
> >
> > I try to log into the system using the safe mode and the encountered the
> > same thing. I tried to use the last good known configuration and the same
> > outcome.
> >
> > This is an emergency please help me how to solve this problem.
> >
> > Thank you in advance for your help!
> >
>
>
>

Try booting into safe mode with networking and see if you can gain access
from a remote computer while in that mode. If still a no go try booting into
Recovery Console and run the chkdsk command to check and repair folder/file
corruption possibly. You also can use listsvc to see if necessary services
are running. If some are not, you can use enable to try and start it. If you
are unsure of necessary services you can try to compare to services running
on a like configured server/computer. You are at a huge disadvantage if you
can not connect to the computer remotely. Another option that very likely
may help is to try an in place upgrade of the operating system, though if
you have a recent backup of the System State or ASR I would try to restore
that first. To do a in place upgrade you would need to boot from the install
cdrom. The downside is that you would have to reinstall all critical updates
for Windows 2003 when done. See the link below if you are interested in that
as an option. The KB link if for W2K but it works the same for Windows 2003.
Of course do not select any option to format! --- Steve

http://support.microsoft.com/default...;en-us;Q306952
http://support.microsoft.com/default.aspx/kb/292175
http://www.microsoft.com/downloads/d...displaylang=en
-- Windows 2003 Server Security guide has a chapter on services to refer to
in you want to know if a service is needed.

"DMI" <(E-Mail Removed)> wrote in message
news:3CEB1AC7-1B08-437D-9247-(E-Mail Removed)...
>I am not able to connect from another computer. I can't even ping the
> server's IP from another computer. Any other ideas?
>
> Thank you very much for your help!
>
> "Steven L Umbach" wrote:
>
>> See if you can access it from another computer on the network via
>> Computer
>> Management to view the event logs to see if the problem is reported. Ask
>> the
>> assistant what he did for any clues. If the user logging on does not have
>> proper ntfs permissions to the user profile or system files behavior such
>> as
>> you see can happen. You might be able to view and change ntfs permissions
>> remotely. Check that system and administrators have full control to the
>> \winnt folder structure and that the administrator has full permissions
>> to
>> his profile folder. Also check that there are not "deny" permissions for
>> the
>> everyone or users groups.
>>
>> Other possibilities are a virus infection. You can use msinfo32 and Under
>> view you can select remote computer. Then you can view services and
>> processes on the remote computer. If you have network access to the
>> computer
>> you can use the psexec tool from SysInternals to access it's command
>> prompt
>> remotely where you might be able to run a virus detection and removal
>> tool
>> such as McAfee Stinger or Trend Micro Sysclean [with the pattern file]
>> after
>> you copy them over via the administrator share. If you do not have any
>> remote access, using Recovery Console may be an option to attempt repairs
>> starting with checkdsk. --- Steve
>>
>> http://www.sysinternals.com/ntw2k/freeware/psexec.shtml -- Psexec
>> http://vil.nai.com/vil/stinger/ -- McAfee Stinger
>> http://www.trendmicro.com/download/dcs.asp -- Trend Micro Sysclean
>> http://support.microsoft.com/default...;EN-US;q249321 --
>> another
>> potential fix?
>> http://support.microsoft.com/default...b;en-us;229716 --
>> Recovery
>> console
>>
>> "DMI" <(E-Mail Removed)> wrote in message
>> news6317C6A-A5A6-42AF-9604-(E-Mail Removed)...
>> > Our company has a Windows 2003 standard server and we were having some
>> > problems with the Internet. There were some modifications made by an
>> > assistant of mine. When we rebooted the server, it takes long time
>> > connecting to the network. When the Login screen appears in the screen
>> > I
>> > login as administrator to the local machine, the domain, etc and this
>> > is
>> > what
>> > happens. As soon as I hit the enter key it looks as if the profile was
>> > being
>> > loaded into the system but in a short period of time the Login screen
>> > appears
>> > again.
>> >
>> > I try to log into the system using the safe mode and the encountered
>> > the
>> > same thing. I tried to use the last good known configuration and the
>> > same
>> > outcome.
>> >
>> > This is an emergency please help me how to solve this problem.
>> >
>> > Thank you in advance for your help!
>> >
>>
>>
>>

I am not able to repair the system by using the instructions listed below.
It does not give me the repair option. I Talked to my assisstant and he run
the lspfix at the server. He tlod me that everything was fixt by removing
the MSWSOCK.DLL and the WINRNR.DLL.

I still do not have access to the server and I can not access the server
remotely.

Thank you for your help and please try to continue to help me.

"Steven L Umbach" wrote:

> Try booting into safe mode with networking and see if you can gain access
> from a remote computer while in that mode. If still a no go try booting into
> Recovery Console and run the chkdsk command to check and repair folder/file
> corruption possibly. You also can use listsvc to see if necessary services
> are running. If some are not, you can use enable to try and start it. If you
> are unsure of necessary services you can try to compare to services running
> on a like configured server/computer. You are at a huge disadvantage if you
> can not connect to the computer remotely. Another option that very likely
> may help is to try an in place upgrade of the operating system, though if
> you have a recent backup of the System State or ASR I would try to restore
> that first. To do a in place upgrade you would need to boot from the install
> cdrom. The downside is that you would have to reinstall all critical updates
> for Windows 2003 when done. See the link below if you are interested in that
> as an option. The KB link if for W2K but it works the same for Windows 2003.
> Of course do not select any option to format! --- Steve
>
> http://support.microsoft.com/default...;en-us;Q306952
> http://support.microsoft.com/default.aspx/kb/292175
> http://www.microsoft.com/downloads/d...displaylang=en
> -- Windows 2003 Server Security guide has a chapter on services to refer to
> in you want to know if a service is needed.
>
> "DMI" <(E-Mail Removed)> wrote in message
> news:3CEB1AC7-1B08-437D-9247-(E-Mail Removed)...
> >I am not able to connect from another computer. I can't even ping the
> > server's IP from another computer. Any other ideas?
> >
> > Thank you very much for your help!
> >
> > "Steven L Umbach" wrote:
> >
> >> See if you can access it from another computer on the network via
> >> Computer
> >> Management to view the event logs to see if the problem is reported. Ask
> >> the
> >> assistant what he did for any clues. If the user logging on does not have
> >> proper ntfs permissions to the user profile or system files behavior such
> >> as
> >> you see can happen. You might be able to view and change ntfs permissions
> >> remotely. Check that system and administrators have full control to the
> >> \winnt folder structure and that the administrator has full permissions
> >> to
> >> his profile folder. Also check that there are not "deny" permissions for
> >> the
> >> everyone or users groups.
> >>
> >> Other possibilities are a virus infection. You can use msinfo32 and Under
> >> view you can select remote computer. Then you can view services and
> >> processes on the remote computer. If you have network access to the
> >> computer
> >> you can use the psexec tool from SysInternals to access it's command
> >> prompt
> >> remotely where you might be able to run a virus detection and removal
> >> tool
> >> such as McAfee Stinger or Trend Micro Sysclean [with the pattern file]
> >> after
> >> you copy them over via the administrator share. If you do not have any
> >> remote access, using Recovery Console may be an option to attempt repairs
> >> starting with checkdsk. --- Steve
> >>
> >> http://www.sysinternals.com/ntw2k/freeware/psexec.shtml -- Psexec
> >> http://vil.nai.com/vil/stinger/ -- McAfee Stinger
> >> http://www.trendmicro.com/download/dcs.asp -- Trend Micro Sysclean
> >> http://support.microsoft.com/default...;EN-US;q249321 --
> >> another
> >> potential fix?
> >> http://support.microsoft.com/default...b;en-us;229716 --
> >> Recovery
> >> console
> >>
> >> "DMI" <(E-Mail Removed)> wrote in message
> >> news6317C6A-A5A6-42AF-9604-(E-Mail Removed)...
> >> > Our company has a Windows 2003 standard server and we were having some
> >> > problems with the Internet. There were some modifications made by an
> >> > assistant of mine. When we rebooted the server, it takes long time
> >> > connecting to the network. When the Login screen appears in the screen
> >> > I
> >> > login as administrator to the local machine, the domain, etc and this
> >> > is
> >> > what
> >> > happens. As soon as I hit the enter key it looks as if the profile was
> >> > being
> >> > loaded into the system but in a short period of time the Login screen
> >> > appears
> >> > again.
> >> >
> >> > I try to log into the system using the safe mode and the encountered
> >> > the
> >> > same thing. I tried to use the last good known configuration and the
> >> > same
> >> > outcome.
> >> >
> >> > This is an emergency please help me how to solve this problem.
> >> >
> >> > Thank you in advance for your help!
> >> >
> >>
> >>
> >>
>
>
>

Below is the link on how to do an in place upgrade of Windows 2003 and I
pasted the pertinent info. Follow the instructions exactly and you should
find an option to repair after the EULA agreement unless you have deeper
problems as explained in step 4. Also when you try to access the computer
from the network try to access it via it's IP address instead of name but if
you can not even ping it by IP address you are pretty much out of luck for
that. A final option may be to put the hard drive of the problem server into
another computer as a slave/secondary drive to copy needed data files off of
before doing a new install. A parallel install of the operating system on
the same computer could also be used for such. Note that if you have to go
that way, that any EFS encrypted files would be lost forever if you do not
have a backup of the user's EFS certificate AND private key in a .pfx
file. --- Steve

http://support.microsoft.com/kb/816579
http://support.microsoft.com/kb/266465 -- how to do a parallel
installation of the operating system.

An in-place upgrade is the final alternative before you have to reinstall
the operating system. Note that it takes the same amount of time to do the
upgrade as to reinstall the operating system. Also, some of your customized
Windows settings may be lost through this process.

To perform an in-place upgrade of Windows Server 2003, follow these steps:
1. Insert the Windows Server 2003 CD in the CD-ROM drive or the DVD-ROM
drive, and then restart the computer. Windows Setup begins.
2. Press ENTER (to continue) when the Welcome to Setup window appears.
3. Press F8 to accept the License Agreement.
4. Use the arrow keys to highlight the Windows Server 2003
installation that you want to upgrade, and then press R (to Repair).

Note If the Setup program does not detect a previous installation but
just continues to the partitioning screen, an in-place upgrade may not be
possible. To detect an existing installation, the Boot.ini file must be
correct, the installed registry files must be intact, and the build number
must be the same. If these are not all true, Setup will not find the
installation to do an in-place upgrade.
5. Windows Server 2003 Setup performs an in-place upgrade of the
existing installation. Follow the instructions on the screen to complete the
process.


--------------------------------------------------------------------------------


"DMI" <(E-Mail Removed)> wrote in message
news:59891D12-8984-494D-A41A-(E-Mail Removed)...
>I am not able to repair the system by using the instructions listed below.
> It does not give me the repair option. I Talked to my assisstant and he
> run
> the lspfix at the server. He tlod me that everything was fixt by removing
> the MSWSOCK.DLL and the WINRNR.DLL.
>
> I still do not have access to the server and I can not access the server
> remotely.
>
> Thank you for your help and please try to continue to help me.
>
> "Steven L Umbach" wrote:
>
>> Try booting into safe mode with networking and see if you can gain access
>> from a remote computer while in that mode. If still a no go try booting
>> into
>> Recovery Console and run the chkdsk command to check and repair
>> folder/file
>> corruption possibly. You also can use listsvc to see if necessary
>> services
>> are running. If some are not, you can use enable to try and start it. If
>> you
>> are unsure of necessary services you can try to compare to services
>> running
>> on a like configured server/computer. You are at a huge disadvantage if
>> you
>> can not connect to the computer remotely. Another option that very likely
>> may help is to try an in place upgrade of the operating system, though if
>> you have a recent backup of the System State or ASR I would try to
>> restore
>> that first. To do a in place upgrade you would need to boot from the
>> install
>> cdrom. The downside is that you would have to reinstall all critical
>> updates
>> for Windows 2003 when done. See the link below if you are interested in
>> that
>> as an option. The KB link if for W2K but it works the same for Windows
>> 2003.
>> Of course do not select any option to format! --- Steve
>>
>> http://support.microsoft.com/default...;en-us;Q306952
>> http://support.microsoft.com/default.aspx/kb/292175
>> http://www.microsoft.com/downloads/d...displaylang=en
>> -- Windows 2003 Server Security guide has a chapter on services to refer
>> to
>> in you want to know if a service is needed.
>>
>> "DMI" <(E-Mail Removed)> wrote in message
>> news:3CEB1AC7-1B08-437D-9247-(E-Mail Removed)...
>> >I am not able to connect from another computer. I can't even ping the
>> > server's IP from another computer. Any other ideas?
>> >
>> > Thank you very much for your help!
>> >
>> > "Steven L Umbach" wrote:
>> >
>> >> See if you can access it from another computer on the network via
>> >> Computer
>> >> Management to view the event logs to see if the problem is reported.
>> >> Ask
>> >> the
>> >> assistant what he did for any clues. If the user logging on does not
>> >> have
>> >> proper ntfs permissions to the user profile or system files behavior
>> >> such
>> >> as
>> >> you see can happen. You might be able to view and change ntfs
>> >> permissions
>> >> remotely. Check that system and administrators have full control to
>> >> the
>> >> \winnt folder structure and that the administrator has full
>> >> permissions
>> >> to
>> >> his profile folder. Also check that there are not "deny" permissions
>> >> for
>> >> the
>> >> everyone or users groups.
>> >>
>> >> Other possibilities are a virus infection. You can use msinfo32 and
>> >> Under
>> >> view you can select remote computer. Then you can view services and
>> >> processes on the remote computer. If you have network access to the
>> >> computer
>> >> you can use the psexec tool from SysInternals to access it's command
>> >> prompt
>> >> remotely where you might be able to run a virus detection and removal
>> >> tool
>> >> such as McAfee Stinger or Trend Micro Sysclean [with the pattern file]
>> >> after
>> >> you copy them over via the administrator share. If you do not have any
>> >> remote access, using Recovery Console may be an option to attempt
>> >> repairs
>> >> starting with checkdsk. --- Steve
>> >>
>> >> http://www.sysinternals.com/ntw2k/freeware/psexec.shtml -- Psexec
>> >> http://vil.nai.com/vil/stinger/ -- McAfee Stinger
>> >> http://www.trendmicro.com/download/dcs.asp -- Trend Micro Sysclean
>> >> http://support.microsoft.com/default...;EN-US;q249321 --
>> >> another
>> >> potential fix?
>> >> http://support.microsoft.com/default...b;en-us;229716 --
>> >> Recovery
>> >> console
>> >>
>> >> "DMI" <(E-Mail Removed)> wrote in message
>> >> news6317C6A-A5A6-42AF-9604-(E-Mail Removed)...
>> >> > Our company has a Windows 2003 standard server and we were having
>> >> > some
>> >> > problems with the Internet. There were some modifications made by
>> >> > an
>> >> > assistant of mine. When we rebooted the server, it takes long time
>> >> > connecting to the network. When the Login screen appears in the
>> >> > screen
>> >> > I
>> >> > login as administrator to the local machine, the domain, etc and
>> >> > this
>> >> > is
>> >> > what
>> >> > happens. As soon as I hit the enter key it looks as if the profile
>> >> > was
>> >> > being
>> >> > loaded into the system but in a short period of time the Login
>> >> > screen
>> >> > appears
>> >> > again.
>> >> >
>> >> > I try to log into the system using the safe mode and the encountered
>> >> > the
>> >> > same thing. I tried to use the last good known configuration and
>> >> > the
>> >> > same
>> >> > outcome.
>> >> >
>> >> > This is an emergency please help me how to solve this problem.
>> >> >
>> >> > Thank you in advance for your help!
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>