Re: Primary WINS Server

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

OK, I've done that. I'll report back here in a week or so.

"Dave Nickason [SBS MVP]" wrote:

Sounds right. By default, that Time Server option is not used in DHCP. I'm
not sure if that would override the registry setting or not, but it sounds
like that's the case.


"Terry Ephony" <TerryEphony@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:27871FA8-0AA9-4C82-9660-BB1A9E78D155@xxxxxxxxxxxxxxxx
Dave,

Thanks for that.

The SNTP value on the server is as you expected, and on a workstation I
also
saw the NT5DS in the win32time parameters.

However, I'm not getting event 35, in fact I'm seeing event 36, "The time
service has not been able to synchronize the system time because none of
the
time providers has been able to provide a usable time stamp." This is
understandable because previously the DHCP had been giving out the IP
address
of the Linux box (which is not running a time server) as the time server.

Does this mean I simply need to uncheck the Time Server option in the DHCP
Scope Options the server (which is currently giving out a valid internet
NTP
server IP address as recommended by OneInTen in his earlier post) to get
the
workstations to sync with the server?

Many thanks for your ongoing help with this.

"Dave Nickason [SBS MVP]" wrote:

On the server, open a command prompt and type "net time /querysntp"
without
the quotes. By default, it should return "The current SNTP value is:
time.windows.com,0x1," which means your server is getting its time from
the
default time server.

On a workstation, the easiest thing to do is to search the System log for
event ID 35 from source W32Time. This should indicate that the
workstation
is synching with the SBS. If it's not, check in the registry:
HKLM\CurrentControlSet\Services\w32time\Parameters. The Type value
should
be set to "NT5DS" without the quotes. That should be the default for a
domain-member XP box that's getting its time sync from the domain
controller.


"Terry Ephony" <TerryEphony@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1426EEEE-EF4A-4C65-8718-6B8251DB277D@xxxxxxxxxxxxxxxx
Dave,

Thanks for the advice, I've taken it on board, but I'm not sure how to
implement it.

I can see that unchecking "Time Server" in the Scope Options would be
easy
enough. But now how do I get the server to synchronise with an NTP
server?
There's no "Internet Time" tab in Date and Time Settings.

Thanks for your help,
Terry

"Dave Nickason [SBS MVP]" wrote:

I wouldn't set a time server in DHCP. The SBS should be configured to
sync
with a good external time server, then the workstations should sync
with
the
SBS. Odds are, this is already working without any intervention - by
default, domain-member PCs should be synching their time with the
domain
controller.

If you run into a sync issue with the client PCs and they get more
than
about 5 minutes off from the SBS, you're going to run into login
problems.
That's avoided by just letting them sync with the SBS.


"Terry Ephony" <TerryEphony@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:BF5BF207-8BAA-470C-895B-CD859CA59DE9@xxxxxxxxxxxxxxxx
That's excellent news. Thanks for all your help with the WINS
problem,
and
the time server information, it's much appreciated.

"OneInTen" wrote:

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: Still have problem with DNS forwarding
    ... How many nics in your SBS server ... > The linux server was part of the original setup which> included a w2k server. ... > I have installed w2003 sbs on the old w2k server, and> migrated to clients to the new server. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Port 443 Question
    ... expensive router than can support more than 1 public IP? ... Is the Linux box part of the SBS domain? ... is a completely different server on the ...
    (microsoft.public.windows.server.sbs)
  • Re: Port 443 Question
    ... If your router supports one-to-one NAT, you can ask your ISP for a block of IP addresses and have both servers, the SBS and the Linux published to the Internet with their own IP address. ... > is a completely different server on the ...
    (microsoft.public.windows.server.sbs)