Re: Primary WINS Server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Glad the problem was solved

If you replaced the IP address under WINS that's all you have to do. I
would go and issue an ipconfig /release and then ipconfig /renew to make
sure that everything is refreshed at the workstation level. As far as the
Time Server entry goes, you'll have to supply the IP address of a valid NIST
time server or other appropriate authority.

Here is the list of NIST servers
http://tf.nist.gov/service/time-servers.html

You can use: time.nist.gov or any other server on the list




"Terry Ephony" <TerryEphony@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A2CDAA0B-9C61-4DD6-9F5F-B3B2B219ED2A@xxxxxxxxxxxxxxxx
Great stuff! I think that's cracked it.

There's only one network card in the box, but under "Scope Options" in
DHCP
the IP address of the Linux box was listed under WINS/NBNS Servers. I've
now
replaced the IP of the Linux box with the IP of the SBS.

The WINS service was already running on the SBS box. I assume for now
that
that's all I need to do?

One other thing, I noticed that the Linux box IP address was also listed
under "Time Server". I've removed that reference and replaced it with the
SBS
IP.

That's not going to break anything, is it?

Thanks a lot for your help with this.

"OneInTen" wrote:

Make sure that the WINS server runs on the SBS box. Assuming that DHCP is
running on the SBS box and that all clients are configured to receive IP
addresses from that box, go to DHCP ("Start/Administrative Tools/DHCP")
click on the server name then on "Scope" and then on "Scope Options".

See if the IP address of the internal NIC (assuming two network cards) is
listed under "044 WINS/NBNS Servers"



"Terry Ephony" <TerryEphony@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A98CADDC-0931-4954-81DC-0DBD96B1A434@xxxxxxxxxxxxxxxx
Hi,

Following the departure from our company of a proper Linux
propellerhead
we
recently changed from using a Red Hat Linux box with Samba to run our
network
to Microsoft Small Business Server 2003 SP1.

We paid someone to put the server in for us so exactly how it works is
a
slight mystery to us ;)

We seem to have a problem now in that all our machines are picking up
the
IP
of the Linux box as the Primary WINS Server (this can be seen when
doing
an
ipconfig /all on any of the client PCs).

We have tried unplugging the Linux box from the network, rebooting a
client
PC, and then checking this setting again. Even without the Linux box
on
the
network it is still showing up as the Primary WINS server, even
following
an
ipconfig /release ipconfig /renew.

Do you think this WINS server address is being dished out by the SBS
server
somehow? That would seem to be the case.

Any ideas on how to fix this? We've had a dig around the WINS and DNS
config but not had any joy so far.

Many thanks in advance for your help,
Terry





.



Relevant Pages

  • Re: Cant connet to the Internet.....
    ... Merv Porter [SBS MVP] ... > wanted to know if he could access the Linux box remotely. ... I have successfully implemented a SBS 2003 server ... point it to the LAN IP address of the router (probably ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: LINUX Firewall
    ... there is merit on not having your SBS ... linux firewall server in really doesn't offer any additional security. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Primary WINS Server
    ... run an ipconfig /all on a workstation to make sure ... If the SBS ... Linux box on the network, the DHCP service may not be running on the SBS. ... to Microsoft Small Business Server 2003 SP1. ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... Are you running SBS 2003 Standard or Premium? ... (Don't worry about the ipconfig /all format for now). ... match the broadband connection, the two NIC firewall, the remote ... Ethernet adapter Server Local Area Connection: ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 problem
    ... the ipconfig command returned the correct settings. ... it might have come up with incorrect network settings. ... We have an SBS 2003 server. ...
    (microsoft.public.windows.server.sbs)