Windows 2000 server and WINS

  • Thread starter Thread starter dbpbandit
  • Start date Start date
D

dbpbandit

I have a windows 2000 server on the network. it's not the domain
controller or WINS server, just use it as file storage and print
server. For some reason it will not start the WINS service. I have
followed all Microsoft's advice, cleared out the wins folder , etc. but
it will not start. This has all but stopped access to it for files,
printing and pretty much everything. I can ping the Wins server but
only by ip address, not by name. Anyone have an idea of what I can try
next, outside of whipping it clean and reinstalling the OS? Any
suggestions would be greatly appreciated...

-Dave
 
I believe the WINS service is the WINS Server. You said this computer is not
the WINS server. All you need for WINS client setup is the approporiate
entry in your advanced TCP/IP properties. For the WINS service to be
present, you must need to have the WINS server installed. I checked my W2K3
member server, which is a WINS client, but there is no WINS service listed
in the services snap-in.

....kurt
 
I do have a WINS server and It's working fine because all of the other
Servers and systems are seeing and using WINS. The server in question
gives me an error in the event viewer stating that WINS could not be
started. error # 3758096385 I have looked up this error on the internet
and everything I read tells me to delete the files in the wins
directory and restart the service. I have done this several times and
get the same error. Not sure if I need to try something in the registry
but that makes me nervous and I'm not sure what to do. I have also
reinstalled this service from the W2K server disk but no dice. Any
other suggestions?
Thanks,

-Dave
 
Wait a minute. Do you want this server to be a WINS server? If so, the WINS
service will have to be started. But if your WINS server is running on
another computer, you don't need the WINS service running (go look at the
services on some of the other computers - I bet the WINS service isn't even
there). Do this: Go to a workstations and run "ipconfig /all" from the
command line. Do the same on the server in question and post both.

....kurt
 
Back
Top