Windows 2000 Pro - Workstation service won't start.

[Anil]

Windows 2000 Pro - 5.00.2195 Service Pack 4 - Workstation
service won't start. The event log has the
message "Initialization failed because the requested
service redirector could not be started. ". I do not know
when exactly this started to happen. But, my hunch is on
one of those worms (which was detected and supposedly
cleaned a few months ago). Though the current AV software
does not indicate any virus/worm, I have a feeling that
some files and registry might have gotten screwed up. What
is the easiest way fix this? I can't really spend time in
backing up applications and reinstalling the OS again, and
then applying all patches!!!

The basic problem I have is that I can't map n/w drives.
All the other applications, which I use on a daily basis,
seem to run without any problems.

TIA

Regards,
Anil

 

[Steven L Umbach]

You could try to unistall Client for Microsoft Networks in your adapter properties,
reboot and then reinstall to see if it helps. If that does not work try booting into
safe mode with networking to see if it helps. If that does work then you have a
problem with a startup application/service/driver. Make sure that tcp/ip netbios
helper service is started. It would not hurt to run System File Checker as in sfc
/scannow to check your protected files. An in place upgrade of the operating system
probably would fix it and while it should preserve your data and applications it
would require you to first install the service pack and then all critical
pdates. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q292175
http://support.microsoft.com/default.aspx?scid=kb;EN-US;313222 --- may help to try
this with the" /areas services " option.

 

[Guest]

Steve,

Appreciate the prompt response. I will try the suggested
options.

Thanks and regards,
Anil

-----Original Message-----
You could try to unistall Client for Microsoft Networks in your adapter properties,
reboot and then reinstall to see if it helps. If that does not work try booting into
safe mode with networking to see if it helps. If that does work then you have a
problem with a startup application/service/driver. Make sure that tcp/ip netbios
helper service is started. It would not hurt to run System File Checker as in sfc
/scannow to check your protected files. An in place

upgrade of the operating system