xp home "net start workstation" failure

[user_x]

one of my pc's is invisible to my home network (though I
CAN ping it's IP - not \\computername). I've traced this
problem (so far) to a failure of the "net start
workstation" service..which I understand is used to make
the PC visible on an MS network (computer name, file &
printer sharing etc.)

In my computer admin screen, it says the service is set to
manual (not auto). When I try to manually run the command,
I get an error 2250, and it says to type helpmsge 3547.
When I do that, it says a "service specific error ***
occurred" & to refer to documentation (?)

I've tried scanning/replacing my system files with the MS
utility included with XP. No dice.
Questions - what is the actual file name(s) used by
the "net start workstation" service command, and can I
manually replace them...and how?
Again, the network is OK at the IP level - can ping in and
out of all PCs using IPs. But the one PC is not visible
in any network neighborhood, and it's not able to see any
of the others. Ideas?

[Ken Wickes [MSFT]]

The workstation service should be set to automatic.

2250 is ERROR_NOT_CONNECTED, but I don't know what that means in your
situation.

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"user_x" > wrote in message
...
> one of my pc's is invisible to my home network (though I
> CAN ping it's IP - not \\computername). I've traced this
> problem (so far) to a failure of the "net start
> workstation" service..which I understand is used to make
> the PC visible on an MS network (computer name, file &
> printer sharing etc.)
>
> In my computer admin screen, it says the service is set to
> manual (not auto). When I try to manually run the command,
> I get an error 2250, and it says to type helpmsge 3547.
> When I do that, it says a "service specific error ***
> occurred" & to refer to documentation (?)
>
> I've tried scanning/replacing my system files with the MS
> utility included with XP. No dice.
> Questions - what is the actual file name(s) used by
> the "net start workstation" service command, and can I
> manually replace them...and how?
> Again, the network is OK at the IP level - can ping in and
> out of all PCs using IPs. But the one PC is not visible
> in any network neighborhood, and it's not able to see any
> of the others. Ideas?

[user_x]

- any idea what executable the command line utilizes (net
start workstation)? I have a feeling that I may have
corrupted fles (executable or maybe dlls) - would like to
replace them (extract from original xp disk) prior to
looking elsewhere. No hardware conflicts - all devices
seem to work fine.

>-----Original Message-----
>The workstation service should be set to automatic.
>
>2250 is ERROR_NOT_CONNECTED, but I don't know what that
means in your
>situation.
>
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>"user_x" > wrote in message
...
>> one of my pc's is invisible to my home network (though I
>> CAN ping it's IP - not \\computername). I've traced this
>> problem (so far) to a failure of the "net start
>> workstation" service..which I understand is used to make
>> the PC visible on an MS network (computer name, file &
>> printer sharing etc.)
>>
>> In my computer admin screen, it says the service is set
to
>> manual (not auto). When I try to manually run the
command,
>> I get an error 2250, and it says to type helpmsge 3547.
>> When I do that, it says a "service specific error ***
>> occurred" & to refer to documentation (?)
>>
>> I've tried scanning/replacing my system files with the
MS
>> utility included with XP. No dice.
>> Questions - what is the actual file name(s) used by
>> the "net start workstation" service command, and can I
>> manually replace them...and how?
>> Again, the network is OK at the IP level - can ping in
and
>> out of all PCs using IPs. But the one PC is not visible
>> in any network neighborhood, and it's not able to see
any
>> of the others. Ideas?
>
>
>.
>

[Ken Wickes [MSFT]]

I'm not sure what you mean. net start workstation uses
\windows\system32\net.exe

I kind of doubt the files themseleves are corrupted.

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"user_x" > wrote in message
...
> - any idea what executable the command line utilizes (net
> start workstation)? I have a feeling that I may have
> corrupted fles (executable or maybe dlls) - would like to
> replace them (extract from original xp disk) prior to
> looking elsewhere. No hardware conflicts - all devices
> seem to work fine.
>
> >-----Original Message-----
> >The workstation service should be set to automatic.
> >
> >2250 is ERROR_NOT_CONNECTED, but I don't know what that
> means in your
> >situation.
> >
> >--
> >This posting is provided "AS IS" with no warranties, and
> confers no rights.
> >
> >
> >"user_x" > wrote in message
> ...
> >> one of my pc's is invisible to my home network (though I
> >> CAN ping it's IP - not \\computername). I've traced this
> >> problem (so far) to a failure of the "net start
> >> workstation" service..which I understand is used to make
> >> the PC visible on an MS network (computer name, file &
> >> printer sharing etc.)
> >>
> >> In my computer admin screen, it says the service is set
> to
> >> manual (not auto). When I try to manually run the
> command,
> >> I get an error 2250, and it says to type helpmsge 3547.
> >> When I do that, it says a "service specific error ***
> >> occurred" & to refer to documentation (?)
> >>
> >> I've tried scanning/replacing my system files with the
> MS
> >> utility included with XP. No dice.
> >> Questions - what is the actual file name(s) used by
> >> the "net start workstation" service command, and can I
> >> manually replace them...and how?
> >> Again, the network is OK at the IP level - can ping in
> and
> >> out of all PCs using IPs. But the one PC is not visible
> >> in any network neighborhood, and it's not able to see
> any
> >> of the others. Ideas?
> >
> >
> >.
> >

[user_x]

hmmm I did more digging - it seems my PC is not running
the "remote procedure call (RPC) locator service
(locator.exe)..which depends upon the workstation
service...which of course is not running. The RPC locator
is shown as an "essential" service under MSCONFIG.

I can't find any logical reason why these services should
not be running. Under MSCONFIG they both show up, but
are "stopped".

As I said, I can't find any hardware problems, I don't
get any kind of error msgs on boot..these services just
don't run - so I'm trying to trace the dependencies back
to find out what's missing. Maybe I am wrong about
corrupted files, but if the files are there (which they
are) and they are intact, why won't they run? Could
network settings be preventing them? The broke PC is set
up the same as the others, so I'm doubting that's it.
Thanks for the continued help...

>-----Original Message-----
>I'm not sure what you mean. net start workstation uses
>\windows\system32\net.exe
>
>I kind of doubt the files themseleves are corrupted.
>
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>"user_x" > wrote in message
...
>> - any idea what executable the command line utilizes
(net
>> start workstation)? I have a feeling that I may have
>> corrupted fles (executable or maybe dlls) - would like
to
>> replace them (extract from original xp disk) prior to
>> looking elsewhere. No hardware conflicts - all devices
>> seem to work fine.
>>
>> >-----Original Message-----
>> >The workstation service should be set to automatic.
>> >
>> >2250 is ERROR_NOT_CONNECTED, but I don't know what
that
>> means in your
>> >situation.
>> >
>> >--
>> >This posting is provided "AS IS" with no warranties,
and
>> confers no rights.
>> >
>> >
>> >"user_x" > wrote in message
>> ...
>> >> one of my pc's is invisible to my home network
(though I
>> >> CAN ping it's IP - not \\computername). I've traced
this
>> >> problem (so far) to a failure of the "net start
>> >> workstation" service..which I understand is used to
make
>> >> the PC visible on an MS network (computer name,
file &
>> >> printer sharing etc.)
>> >>
>> >> In my computer admin screen, it says the service is
set
>> to
>> >> manual (not auto). When I try to manually run the
>> command,
>> >> I get an error 2250, and it says to type helpmsge
3547.
>> >> When I do that, it says a "service specific error
***
>> >> occurred" & to refer to documentation (?)
>> >>
>> >> I've tried scanning/replacing my system files with
the
>> MS
>> >> utility included with XP. No dice.
>> >> Questions - what is the actual file name(s) used by
>> >> the "net start workstation" service command, and
can I
>> >> manually replace them...and how?
>> >> Again, the network is OK at the IP level - can ping
in
>> and
>> >> out of all PCs using IPs. But the one PC is not
visible
>> >> in any network neighborhood, and it's not able to
see
>> any
>> >> of the others. Ideas?
>> >
>> >
>> >.
>> >
>
>
>.
>

[Ken Wickes [MSFT]]

Well the RpcLocator service isn't running on my machine, so I don't think it
is that essential.

A google search reveals that another person with this problem had luck with
a "sfc /scannow", so maybe you were right about the corrupted files.

Try the "sfc /scannow"

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"user_x" > wrote in message
...
> hmmm I did more digging - it seems my PC is not running
> the "remote procedure call (RPC) locator service
> (locator.exe)..which depends upon the workstation
> service...which of course is not running. The RPC locator
> is shown as an "essential" service under MSCONFIG.
>
> I can't find any logical reason why these services should
> not be running. Under MSCONFIG they both show up, but
> are "stopped".
>
> As I said, I can't find any hardware problems, I don't
> get any kind of error msgs on boot..these services just
> don't run - so I'm trying to trace the dependencies back
> to find out what's missing. Maybe I am wrong about
> corrupted files, but if the files are there (which they
> are) and they are intact, why won't they run? Could
> network settings be preventing them? The broke PC is set
> up the same as the others, so I'm doubting that's it.
> Thanks for the continued help...
>
> >-----Original Message-----
> >I'm not sure what you mean. net start workstation uses
> >\windows\system32\net.exe
> >
> >I kind of doubt the files themseleves are corrupted.
> >
> >--
> >This posting is provided "AS IS" with no warranties, and
> confers no rights.
> >
> >
> >"user_x" > wrote in message
> ...
> >> - any idea what executable the command line utilizes
> (net
> >> start workstation)? I have a feeling that I may have
> >> corrupted fles (executable or maybe dlls) - would like
> to
> >> replace them (extract from original xp disk) prior to
> >> looking elsewhere. No hardware conflicts - all devices
> >> seem to work fine.
> >>
> >> >-----Original Message-----
> >> >The workstation service should be set to automatic.
> >> >
> >> >2250 is ERROR_NOT_CONNECTED, but I don't know what
> that
> >> means in your
> >> >situation.
> >> >
> >> >--
> >> >This posting is provided "AS IS" with no warranties,
> and
> >> confers no rights.
> >> >
> >> >
> >> >"user_x" > wrote in message
> >> ...
> >> >> one of my pc's is invisible to my home network
> (though I
> >> >> CAN ping it's IP - not \\computername). I've traced
> this
> >> >> problem (so far) to a failure of the "net start
> >> >> workstation" service..which I understand is used to
> make
> >> >> the PC visible on an MS network (computer name,
> file &
> >> >> printer sharing etc.)
> >> >>
> >> >> In my computer admin screen, it says the service is
> set
> >> to
> >> >> manual (not auto). When I try to manually run the
> >> command,
> >> >> I get an error 2250, and it says to type helpmsge
> 3547.
> >> >> When I do that, it says a "service specific error
> ***
> >> >> occurred" & to refer to documentation (?)
> >> >>
> >> >> I've tried scanning/replacing my system files with
> the
> >> MS
> >> >> utility included with XP. No dice.
> >> >> Questions - what is the actual file name(s) used by
> >> >> the "net start workstation" service command, and
> can I
> >> >> manually replace them...and how?
> >> >> Again, the network is OK at the IP level - can ping
> in
> >> and
> >> >> out of all PCs using IPs. But the one PC is not
> visible
> >> >> in any network neighborhood, and it's not able to
> see
> >> any
> >> >> of the others. Ideas?
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >

[user_x]

I'd be scouring the net for a few weeks and had already
found that post (on expert's exchange I think..). Tried
the sfc /scannow command last week. All it did was
totally hose up my video (replaced my groovy nvidia driver
with the generic VGA.

What I think I've learned so far:
RPC Locator Service (locator.exe) depends upon the
Workstation Service to run - default XP config says this
should be automatic. It does not run (prolly because
Worstation is not running).
Workstation Service (svchost.exe) - default XP config says
this should run - it does not.
WMI (windows management instrumentation) (svchost.exe)
also will not run (says it's unavailable) - should also
run automatically.
I found that I can manually extract files from the XP CD
if I go to msconfig - do I have to be in safe mode to do
this? I tried it on a normal boot & my PC crashed.
** ALSO ** are there any .dlls that these executables look
to for info - I'll need to replace those too.
T H A N K S

>-----Original Message-----
>Well the RpcLocator service isn't running on my machine,
so I don't think it
>is that essential.
>
>A google search reveals that another person with this
problem had luck with
>a "sfc /scannow", so maybe you were right about the
corrupted files.
>
>Try the "sfc /scannow"
>
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>"user_x" > wrote in message
...
>> hmmm I did more digging - it seems my PC is not running
>> the "remote procedure call (RPC) locator service
>> (locator.exe)..which depends upon the workstation
>> service...which of course is not running. The RPC
locator
>> is shown as an "essential" service under MSCONFIG.
>>
>> I can't find any logical reason why these services
should
>> not be running. Under MSCONFIG they both show up, but
>> are "stopped".
>>
>> As I said, I can't find any hardware problems, I don't
>> get any kind of error msgs on boot..these services just
>> don't run - so I'm trying to trace the dependencies back
>> to find out what's missing. Maybe I am wrong about
>> corrupted files, but if the files are there (which they
>> are) and they are intact, why won't they run? Could
>> network settings be preventing them? The broke PC is set
>> up the same as the others, so I'm doubting that's it.
>> Thanks for the continued help...
>>
>> >-----Original Message-----
>> >I'm not sure what you mean. net start workstation uses
>> >\windows\system32\net.exe
>> >
>> >I kind of doubt the files themseleves are corrupted.
>> >
>> >--
>> >This posting is provided "AS IS" with no warranties,
and
>> confers no rights.
>> >
>> >
>> >"user_x" > wrote in message
>> ...
>> >> - any idea what executable the command line utilizes
>> (net
>> >> start workstation)? I have a feeling that I may have
>> >> corrupted fles (executable or maybe dlls) - would
like
>> to
>> >> replace them (extract from original xp disk) prior to
>> >> looking elsewhere. No hardware conflicts - all
devices
>> >> seem to work fine.
>> >>
>> >> >-----Original Message-----
>> >> >The workstation service should be set to automatic.
>> >> >
>> >> >2250 is ERROR_NOT_CONNECTED, but I don't know what
>> that
>> >> means in your
>> >> >situation.
>> >> >
>> >> >--
>> >> >This posting is provided "AS IS" with no warranties,
>> and
>> >> confers no rights.
>> >> >
>> >> >
>> >> >"user_x" > wrote in message
>> >> ...
>> >> >> one of my pc's is invisible to my home network
>> (though I
>> >> >> CAN ping it's IP - not \\computername). I've
traced
>> this
>> >> >> problem (so far) to a failure of the "net start
>> >> >> workstation" service..which I understand is used
to
>> make
>> >> >> the PC visible on an MS network (computer name,
>> file &
>> >> >> printer sharing etc.)
>> >> >>
>> >> >> In my computer admin screen, it says the service
is
>> set
>> >> to
>> >> >> manual (not auto). When I try to manually run the
>> >> command,
>> >> >> I get an error 2250, and it says to type helpmsge
>> 3547.
>> >> >> When I do that, it says a "service specific error
>> ***
>> >> >> occurred" & to refer to documentation (?)
>> >> >>
>> >> >> I've tried scanning/replacing my system files with
>> the
>> >> MS
>> >> >> utility included with XP. No dice.
>> >> >> Questions - what is the actual file name(s) used
by
>> >> >> the "net start workstation" service command, and
>> can I
>> >> >> manually replace them...and how?
>> >> >> Again, the network is OK at the IP level - can
ping
>> in
>> >> and
>> >> >> out of all PCs using IPs. But the one PC is not
>> visible
>> >> >> in any network neighborhood, and it's not able to
>> see
>> >> any
>> >> >> of the others. Ideas?
>> >> >
>> >> >
>> >> >.
>> >> >
>> >
>> >
>> >.
>> >
>
>
>.
>

[Ken Wickes [MSFT]]

Workstation is wkssvc.dll

WMI is wmisvc.dll

You don't have to be in safe mode to replace dlls.

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"user_x" > wrote in message
...
> I'd be scouring the net for a few weeks and had already
> found that post (on expert's exchange I think..). Tried
> the sfc /scannow command last week. All it did was
> totally hose up my video (replaced my groovy nvidia driver
> with the generic VGA.
>
> What I think I've learned so far:
> RPC Locator Service (locator.exe) depends upon the
> Workstation Service to run - default XP config says this
> should be automatic. It does not run (prolly because
> Worstation is not running).
> Workstation Service (svchost.exe) - default XP config says
> this should run - it does not.
> WMI (windows management instrumentation) (svchost.exe)
> also will not run (says it's unavailable) - should also
> run automatically.
> I found that I can manually extract files from the XP CD
> if I go to msconfig - do I have to be in safe mode to do
> this? I tried it on a normal boot & my PC crashed.
> ** ALSO ** are there any .dlls that these executables look
> to for info - I'll need to replace those too.
> T H A N K S
>
> >-----Original Message-----
> >Well the RpcLocator service isn't running on my machine,
> so I don't think it
> >is that essential.
> >
> >A google search reveals that another person with this
> problem had luck with
> >a "sfc /scannow", so maybe you were right about the
> corrupted files.
> >
> >Try the "sfc /scannow"
> >
> >--
> >This posting is provided "AS IS" with no warranties, and
> confers no rights.
> >
> >
> >"user_x" > wrote in message
> ...
> >> hmmm I did more digging - it seems my PC is not running
> >> the "remote procedure call (RPC) locator service
> >> (locator.exe)..which depends upon the workstation
> >> service...which of course is not running. The RPC
> locator
> >> is shown as an "essential" service under MSCONFIG.
> >>
> >> I can't find any logical reason why these services
> should
> >> not be running. Under MSCONFIG they both show up, but
> >> are "stopped".
> >>
> >> As I said, I can't find any hardware problems, I don't
> >> get any kind of error msgs on boot..these services just
> >> don't run - so I'm trying to trace the dependencies back
> >> to find out what's missing. Maybe I am wrong about
> >> corrupted files, but if the files are there (which they
> >> are) and they are intact, why won't they run? Could
> >> network settings be preventing them? The broke PC is set
> >> up the same as the others, so I'm doubting that's it.
> >> Thanks for the continued help...
> >>
> >> >-----Original Message-----
> >> >I'm not sure what you mean. net start workstation uses
> >> >\windows\system32\net.exe
> >> >
> >> >I kind of doubt the files themseleves are corrupted.
> >> >
> >> >--
> >> >This posting is provided "AS IS" with no warranties,
> and
> >> confers no rights.
> >> >
> >> >
> >> >"user_x" > wrote in message
> >> ...
> >> >> - any idea what executable the command line utilizes
> >> (net
> >> >> start workstation)? I have a feeling that I may have
> >> >> corrupted fles (executable or maybe dlls) - would
> like
> >> to
> >> >> replace them (extract from original xp disk) prior to
> >> >> looking elsewhere. No hardware conflicts - all
> devices
> >> >> seem to work fine.
> >> >>
> >> >> >-----Original Message-----
> >> >> >The workstation service should be set to automatic.
> >> >> >
> >> >> >2250 is ERROR_NOT_CONNECTED, but I don't know what
> >> that
> >> >> means in your
> >> >> >situation.
> >> >> >
> >> >> >--
> >> >> >This posting is provided "AS IS" with no warranties,
> >> and
> >> >> confers no rights.
> >> >> >
> >> >> >
> >> >> >"user_x" > wrote in message
> >> >> ...
> >> >> >> one of my pc's is invisible to my home network
> >> (though I
> >> >> >> CAN ping it's IP - not \\computername). I've
> traced
> >> this
> >> >> >> problem (so far) to a failure of the "net start
> >> >> >> workstation" service..which I understand is used
> to
> >> make
> >> >> >> the PC visible on an MS network (computer name,
> >> file &
> >> >> >> printer sharing etc.)
> >> >> >>
> >> >> >> In my computer admin screen, it says the service
> is
> >> set
> >> >> to
> >> >> >> manual (not auto). When I try to manually run the
> >> >> command,
> >> >> >> I get an error 2250, and it says to type helpmsge
> >> 3547.
> >> >> >> When I do that, it says a "service specific error
> >> ***
> >> >> >> occurred" & to refer to documentation (?)
> >> >> >>
> >> >> >> I've tried scanning/replacing my system files with
> >> the
> >> >> MS
> >> >> >> utility included with XP. No dice.
> >> >> >> Questions - what is the actual file name(s) used
> by
> >> >> >> the "net start workstation" service command, and
> >> can I
> >> >> >> manually replace them...and how?
> >> >> >> Again, the network is OK at the IP level - can
> ping
> >> in
> >> >> and
> >> >> >> out of all PCs using IPs. But the one PC is not
> >> visible
> >> >> >> in any network neighborhood, and it's not able to
> >> see
> >> >> any
> >> >> >> of the others. Ideas?
> >> >> >
> >> >> >
> >> >> >.
> >> >> >
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >