SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : Dream Machine ( Build your own PC ) -- Ignore unavailable to you. Want to Upgrade?


To: peter michaelson who wrote (8111)7/13/1999 10:03:00 AM
From: Spots  Read Replies (1) | Respond to of 14778
 
Yes, the server service is necessary for the server side
of microsoft networking (what you see from a client).

I don't know what the error means, but presumably you have
a reasonable amount of memory (64mb or more) and a reasonable
page file size (twice memory or more). If not, fix 'em,
but I doubt that's the problem. Probably something was
misinstalled.

My best suggestion is to reinstall the server service,
which you do in the services tab of the network propery
sheet (right click the network desktop icon and choose
properties). Be sure you have the windows and latest
service pack CDs handy. Remove the server service,
then add it back and tell NT to get the files from
the CD. Reboot and reinstall the service pack.
Reboot again and the server service should start.

I'd also have my NIC driver handy, just in case.
A good precaution when fiddling with network configs.

If this doesn't work, do it again but remove ALL network
config (make notes) then reboot, add it all back (NOW
you'll need your NIC driver) getting files from
NT CD. Reboot, reinstall the service pack. Be sure to
name the workgroup the same as it was (assuming it's
the same as the other PC already, if not, go stand in
the corner and make it the same when you come out
tomorrow).

If THIS doesn't work, well, you should have asked someone
who knew what he was doing.

Spots



To: peter michaelson who wrote (8111)7/14/1999 2:28:00 PM
From: S.Y.R.  Read Replies (1) | Respond to of 14778
 
Peter, I had the same problem not long ago. Microsoft tech support suggest to re-install your latest NT Service Pack (minimum SP3). It cured my problem which was a corrupted file. But it could be from many other sources. Search the Microsoft database:

search.microsoft.com

SYR