Actually, while working on this very topic today, I found out some
interesting issues. My production domain is still NT4. I have my PDC and
BDCs running timeserve and retrieving their time from a corporate
timeserver across our WAN (they have the actual internet connection). and
my users, win95, 98, and a few win2k, run a login script that does a net
time \\xxx.xx.xxx.xxx /set using the ip address of our PDC. While testing
a WIN2k server and workstation on a test domain, I noticed that the
workstation was syncing from the DC in my test domain, but the time was
way off from my production machine, so I started looking for how to sync
the time from the corporate time server across the WAN. This turned out
to be a fairly simple process, once I found the instructions. Run from a
command line "c:\net time /setsntp:xxx.xx.xxx.xxxx" then cycle your
windows time service. It actually writes to the registry where to look
for time syncing. This worked from both the server and pro box. I pointed
them both to the corp box, but could have left the pro box syncing to the
DC and the DC syncing to the corp box, to minimize WAN traffic, which is
probably best practice, once rolled out.
Just thought someone out there might want to know,
Russ Braaten, MCSE, MCP+I
> Actually, that is what I have always done. One of my associates pointed out
> the effect of just using "net time /set" and I couldn't answer why we got
> the different results. Just goes to show that browsing and NetBIOS is far
> from gone in W2K.
>
>
> ***************************
> Pete Carstensen, MCSE
> Senior LAN Engineer
> CSK Auto, Inc.
> 645 E. Missouri Ave.
> Phoenix, AZ 85012
> (602) 631-7176
> [EMAIL PROTECTED]
>
> Little surprises around every corner, but nothing dangerous.
> -- Willie Wonka
>
> -----Original Message-----
> From: Phil Pettifer [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 18, 2001 1:05 PM
> To: NT System Admin Issues
> Subject: RE: net time
>
> The simple answer is to hard code the name of the machine you want to use
> for network time into the script you are calling the command from...
>
> e.g.
> net time \\mypdc.mydomain.com /set
>
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 18, 2001 3:19 PM
> To: NT System Admin Issues
> Subject: Re: net time
>
>
> it seems like the net time command does not care about ntp service at all
> but
> queries the first alphabetical computer on a local subnet. Does your
> proxy's
> NetBIOS name comes before your PDC name?
>
> Andrey Kalinin
>
>
>
>
>
> Please respond to "NT System Admin Issues"
> <[EMAIL PROTECTED]>
>
>
>
> To: "NT System Admin Issues"
> <[EMAIL PROTECTED]>
>
> cc: (bcc: Andrey Kalinin/FIS)
>
>
>
> Subject: net time
>
>
>
>
>
>
> I have an interesting situation.
>
> Environment: NT4 Domain, W2K Pro workstation. PDC (NT4, SP6) set to be the
> time server via "NET TIME /SETSNTP:PDC" at the workstation (verified via
> /querysntp)
> The PDC is running Windows Time Service (w32time) and is set as an NTP
> server. It gets its time from a proxy server (W2KS) which has it's time
> updated from NIST.
>
> Anyway, at the W2KP station, if you type "net time /set" it points to the
> proxy server. Why? If you enter "net time /domain /set" it points to the
> PDC as well as when you do the /querysntp.
>
> All I can think of is that the "net time /set" command sees the ntp service
> on the proxy server and reports connection to it. Why is it not going to
> the PDC like it is told to do?
>
> Pete
>
> ***************************
> Pete Carstensen, MCSE
> Senior LAN Engineer
> CSK Auto, Inc.
> 645 E. Missouri Ave.
> Phoenix, AZ 85012
> (602) 631-7176
> [EMAIL PROTECTED]
>
> Little surprises around every corner, but nothing dangerous.
> -- Willie Wonka
>
> -----Original Message-----
> From: Kent, Larry SYNETICS [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 18, 2001 9:31 AM
> To: NT System Admin Issues
> Subject: NT System Admin List
>
> Never thought I would send one of these but....
>
> Is the list up?
>
> I haven't received any emails in a day and a half fromt he list.
>
> Thanks
>
> http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
>
> http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
>
>
>
>
>
> http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
>
>
> http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
