Re: Odd Workstation Service Problem
- From: "cmsix" <cmsix@xxxxxxxxx>
- Date: Thu, 22 Jun 2006 20:17:29 -0500
--
"Chuck" <none@xxxxxxxxxxx> wrote in message news:4gkh92lsk0envnr43ussbfgl314vu6knbk@xxxxxxxxxx
On Tue, 20 Jun 2006 19:26:14 -0500, "cmsix" <cmsix@xxxxxxxxx> wrote:
"Chuck" <none@xxxxxxxxxxx> wrote in message
news:i31f92luk0u3vdji7n6mood7992t283ckk@xxxxxxxxxx
On Mon, 19 Jun 2006 22:49:53 -0500, "cmsix" <cmsix@xxxxxxxxx>
wrote:
"Chuck" <none@xxxxxxxxxxx> wrote in message
news:svld92d57kijm7vbvgcjibgn35u1jrvjkq@xxxxxxxxxx
On Mon, 19 Jun 2006 09:54:40 -0500, "cmsix" <cmsix@xxxxxxxxx>
wrote:
"cmsix" <cmsix@xxxxxxxxx> wrote in message
news:uEyRClpkGHA.4596@xxxxxxxxxxxxxxxxxxxxxxx
One of my computers fails to start the workstation service.
It is running XP Home with SP2. Of course the services that
depend
on it - Alerter, Computer Browser, Messenger, Net Logon, and
Remote
Procedure Call (RPC) Locator can't start either.
Naturally, when I try to look at the "Entire Network" in My
Network
Places I get an error:
Unable to browse the network.
The network is not present or not started.
The thing that's so odd is that I have a mapped drive on the
machine
that works even after rebooting both machines. I can ping it by
IP
address, and can browse the internet with no trouble from it.
Here's what the Event Viewer shows me about it:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 6/17/2006
Time: 11:23:19 PM
User: N/A
Computer: BOZOASUS
Description:
The Workstation service terminated with the following error:
The specified module could not be found.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
I tried sc query Workstation and got:
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:
The specified service does not exist as an installed service.
This had put me at a dead end, because I don't know what module
it's
talking about and I don't know the filename of the workstation
service.
Anyone have any clues for me?
I've since learned that the correct name for the service is
lanmanworkstation. I still can't get it to start.
If I'm asking in the wrong group, someone please let me know and
point
me to the right one if you know it.
Try running the Network Setup Wizard. If it doesn't run
successfully, you
should get messages in the Event Log.
<http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html>
http://nitecruzr.blogspot.com/2005/05/using-network-setup-wizard-in-windows.html
<http://support.microsoft.com/?id=258701>
http://support.microsoft.com/?id=258701
And please, if you're going to have a signature, post at the
bottom.
<http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting>
http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#TopPosting
The Network Setup Wizard runs and completes. It closes when I click
Finish and makes no complaints.
I do get error messages in the system event log and I still get an
error when I try to start the Workstation Service. The Workstation
Service gives a popup Error 126 when I try to start it, same as it
did
before I ran the Network Setup Wizard again.
File and Printer sharing is installed.
To my mind the Network is functioning. The machine can browse the
Internet and my other machine can access both it's drives via a
mapped
drive.
My problem seems to be that lanmanworkstation won't run and
therefore
the Computer Browser and other dependancies can't run. I realize
that
something is keeping it from being to run but I'm still lost.
After running the Network Setup Wizard again the text of the error
log
is the same as I sent in the first post.
Thanks for the help so far.
cmsix
OK, a 126 is
The specified module could not be found.
Let's try SFC.
<http://support.microsoft.com/?id=310747>
http://support.microsoft.com/?id=310747
After that, the NSW again.
--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from
experience.
My email is AT DOT
actual address pchuck mvps org.
Okay, I don't mind doing it again, but SFC is the first thing I
tried. I'm about to go to bed anyway so I'll start it and see what
it has to say in the moring.
I ran sfc /scannow again and got no complaints. After that I tried the
Network Setup Wizard again and got no changes. I can still surf the
internet and can still access the mapped drives on the problem machine
but lanmanworkstation still won't start and of course the dependancies
can't run.
It occurs to me that the problem isn't worth looking for if I can
restroe functionally another way. Do you think that upgrading to XP
Pro would fix the problem on the way? Doing that would be less of a
hassle than a clean reinstall.
One other thing I should mention is that on a slow night I installed
the ipv6 thing. I don't know whether it has anything to do with this
problem or not. I did notice that after getting rid of it I have some
miniport drivers in the device manager with yellow dots and big black
exclamation marks in them.
cmsix
IPV6 has been found to cause problems with Windows Networking in various ways.
If I was looking for something to do before flatten and pave (install XP Pro),
I'd put removal of IPV6 at the top of my list.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html
Then, I'd check for LSP / Winsock / TCP/IP corruption.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
OTOH, upgrading to XP Pro should have nothing to do with a solution.
Reinstallation of XP Home (if that's what you have) will do equally as well. A
client running XP Home should do quite well for you.
It's your network. This would be my course of action though:
1) Remove IPV6.
2) Check for LSP / Winsock / TCP/IP corruption.
3) Re install XP Home (flatten and pave).
4) Upgrade to XP Pro.
--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
I did both. I installed xp Home again over the faulty installation and it cured most of the problems, but I still couldn't browse the network.
That particular machine is using a Western Digital Raptor for the boot drive and I had a new 250 GB drive I wasn't using so I installed XP Pro on it. The disk I had wouldn't do an upgrade.
So now I can dual boot by changing one bios setting. Strangely, the XP Pro wouldn't install to the SATA drive at all, even after I installed the special drivers with the quick fingered F6 run around.
Still it's better than my Fedora troubles - I still can't get it going.
Thanks for all your help. Even though I didn't get the thing back into the shape I thought I should be able to, I didn't lose any files and I learned a lot.
cmsix
MCP Windows 98 Specialist
.
- Follow-Ups:
- Re: Odd Workstation Service Problem
- From: Chuck
- Re: Odd Workstation Service Problem
- References:
- Odd Workstation Service Problem
- From: cmsix
- Re: Odd Workstation Service Problem
- From: cmsix
- Re: Odd Workstation Service Problem
- From: Chuck
- Re: Odd Workstation Service Problem
- From: cmsix
- Re: Odd Workstation Service Problem
- From: Chuck
- Re: Odd Workstation Service Problem
- From: cmsix
- Re: Odd Workstation Service Problem
- From: cmsix
- Re: Odd Workstation Service Problem
- From: Chuck
- Odd Workstation Service Problem
- Prev by Date: Odd Sharing Violation
- Next by Date: Re: Odd Workstation Service Problem
- Previous by thread: Re: Odd Workstation Service Problem
- Next by thread: Re: Odd Workstation Service Problem
- Index(es):
Relevant Pages
|
Loading