Ken,
I was having trouble continuing to find the post, so I
hope you don't mind me sending mail to you directly. I am
still having some trouble with the SERVER Service
stopping. It seems to stop within 15 minutes of
starting. I tried typing the command you gave me...."sc
queryex lanmanserver" but it returned this error
message: 'sc' is not recognized as an internal or
external command, operable program or batch file.
In the RECOVERY tab, there is an option to choose an
action for when the service fails. One of the choices is
RESTART THE SERVICE. When I choose that option and try to
apply, I get the following message:
This service runs in the same process as the service
control manager.
Therefore, the service control manager cannot take action
if this service's
process terminates unexpectedly.
It seems as though the RECOVERY tool would work for me if
I were able to successfully choose it.
Have you ever come across this before, and do you have any
suggestions?
Thank you for your help.
Joe
-----Original Message-----
Strange. I don't know why the server would stop. After it runs and stops,
type "sc queryex lanmanserver" at a command line and see if it set an exit
code. Also check out the event log for anything relevant.
--
Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
JoeFixes said:
Ken,
First, thanks for the continued support. The options on
the service are AUTOMATIC, MANUA & DISABLED. They are
available to choose in a drop down box. AUTOMATIC is
currently selected. I'm not sure how effective that is
though. When I received your message I looked at the
server to se what that options were and to confirm it was
set to AUTOMATIC and when I checked, I noticed THE SERVER
Service was again stopped, and this time there was no
reboot, I had left the server up. I restarted the
service again. It seems to start fine, it just seems to
have a problem to stay running. Any thoughts?
Joe
-----Original Message-----
The server service should have the start
type "Automatic", have you checked
that?
--
Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and
confers no rights.
Ken,
I took your advice and looked into the sharing folder
on
the WIN2000 Server. I wasn't able to share the drive,
it
said becuase THE SERVER Service has not been started.
So, logically I looked in SERVICES and found one called
SERVER when I looked into the properties I saw that it
was "stopped" or "paused" I "started" the service and
was
then able to share the drive which of course led me to
gaining access from the remote computer. The only
problem I ran into was that during this process I did
restart the server and when it came up again THE SERVER
Service was again stopped. Do I need to restart THE
SERVER Service each time I start the server? And If I
do, that's fine, but there must be a way for this
service
to start each time the server boots....no?
Thanks for your help....let's see what you think of
this.
Joe
-----Original Message-----
If the remote computer is able to "see" the server
then
you can rule out
workgroups and connections etc. Looks like you have a
permissions problem.
Have you set up permission in both the sharing and
security tab to allow the
remote user?
--
Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties,
and
confers no rights.
How frustrating this is. I am running Windows 2000
Server and I have one remote computer on the
network.
I
cannot map the network drive on the remote computer.
My
main printer is also connected to the server and I
cannot
print. The remote computer "sees" the server and
the
printer but will not allow access. What is most
frustrating about this is that everything was
working
fine last week, no changes were made but after
restarting
one morning the network connections would not work.
One
thing I notice is this: when searching for
computers
from the remote computer, the remote computer
itself is
found "in folder" WORKGROUP and the server computer
is
also found "in folder" WEB CLIENT NETWORK. I have
checked the workgroup name on both computers and
they
both share same workgroup name (WORKGROUP). One
more
piece that might be helpful---at no time am I given
the
opportunity to enter a log on name and password.
That
could be the key there, but have not figured out
how to
trigger it to ask.
Please help!
.
.
.
