Yeah, the PDC needs to be set as NTP to get source from an NTP server.
Also, set the period value to 1, that will sync once every 24 hours, which
is what you want, whereas 24 will sync 24 times a day, or once an hour.
The version you are running should be OK - earlier versions wouldn't even
run with anything but NTP.
Here are some links that may be of use:(Yes, I know most of these are
specific to Win2K - but there is info of use here still.)
MSKB - Q258059 - How to Synchronize the Time on a Windows 2000-Based
Computer in a Windows NT 4.0 Domain
http://support.microsoft.com/support/kb/articles/Q258/0/59.ASP
MSKB - Q246145 - Changes to W32Time and TimeServ Utilities
http://support.microsoft.com/support/kb/articles/Q246/1/45.ASP
MSKB - Q224799 - Basic Operation of the Windows Time Service
http://support.microsoft.com/support/kb/articles/Q224/7/99.ASP
MSKB - Q223184 - Registry Entries for the W32Time Service
http://support.microsoft.com/support/kb/articles/Q223/1/84.ASP
NTFAQ - How can I configure the Time Service in Windows 2000
http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=14943
Windows 2000 Magazine - Windows 2000 Time
http://www.win2000mag.com/Articles/Index.cfm?ArticleID=20195
Windows 2000 Magazine - Win2K and NT 4.0 Coexistence, Round 2
http://www.win2000mag.com/Articles/Index.cfm?ArticleID=16174
Windows 2000 Magazine - Windows 2000 vs. Windows NT Time Synchronization
http://www.win2000mag.com/Articles/Index.cfm?ArticleID=8456
----Original Message Follows----
From: Ryan Malayter <[EMAIL PROTECTED]>
Reply-To: "MSWinNT Discussions" <[EMAIL PROTECTED]>
To: "MSWinNT Discussions" <[EMAIL PROTECTED]>
Subject: RE: Question on configuring W32Time
Date: Wed, 29 Aug 2001 13:10:33 -0500
I would think that you need to uncomment Type=NTP as well to make it use NTP
at all. Otherwise, it will just use the NETBIOS time sync...
-----Original Message-----
From: Masthanaiah Cheekavolu [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 29, 2001 12:51 PM
To: MSWinNT Discussions
Subject: RE: Question on configuring W32Time
Here is the W32TIME.INI content.
[W32Time]
REM This is W32Time.ini, to be placed in %SystemRoot%
REM Remarks and blank lines are allowed.
REM ****************************
REM * W32Time Service Settings *
REM ****************************
REM NTP uses the Simple Network Time Protocol to become a Master Time
Server. REM PRIMARY is the Time source for each domain that services the
Secondary machines. REM SECONDARY clients broadcast to any primary in the
domain for the current time.
;Type=NTP
Type=PRIMARY
;Type=SECONDARY
REM Period=0 uses the default delay (every 8-12 hours) between each time
set. REM Period can also be set to a number representing the number of time
sets per day.
Period=24
REM TAsync=no uses the TimeAdjustment API to disable CMOS synchronization.
TAsync=no
REM *******************************
REM * Master Time Server Settings *
REM *******************************
REM NTPServer is the name or numeric address of an NTP server on the
Internet
REM (or your intranet). The names BroadcastClient and MulticastClient are
reserved.
NTPServer=192.168.130.1
REM Log=yes places an entry in the Application event log for the first
successful REM sync with an NTP Server. Primary and Secondary machines
never log successes. REM Regardless of the type, Failures are always logged.
Log=yes
REM LocalNTP indicates whether to start an NTP server on the local machine.
LocalNTP=no
REM ********************************
REM * Primary Time Server Settings *
REM ********************************
REM The PrimarySource lists all known Master Time Servers in your network.
REM This list is used by the Primary Time Servers in each domain. REM
Separate each server's Netbios name in the list with a semicolon.
PrimarySource=\\HYDDC05
REM RandomPrimary=yes will randomly choose means to choose a random entry in
the
REM PrimarySource list, rather than starting at the top. As long as the
chosen REM server remains accessible, it will continue to be used.
;RandomPrimary=yes
REM Timesource is used by LanmanServer; set this to yes when Type=Primary.
REM Timesources listen for broadcasts by Secondary clients.
;timesource=no
timesource=yes
REM **********************************
REM * Secondary Time Server Settings *
REM **********************************
REM SecondaryDomain tells the clients (Type=Secondary) which domain to
broadcast REM their time requests to. If this entry is empty or missing,
these clients will
REM query the current domain for a Primary Time Server.
SecondaryDomain=hyd.wilco-int.com
192.168.130.1 is the IP address of the solaris server where NTP
daemon is running. This Solaris server is configured to sync from:
server ntp0.nl.net
# Contact [EMAIL PROTECTED]
server ntp2.ja.net
Any help in this regard is highly appreciated. Is there any better free
Timesync tool apart from NT Reskit Timesync?
thanks,
- Masthan.
-----Original Message-----
From: Ryan Malayter [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 29, 2001 9:58 PM
To: MSWinNT Discussions
Subject: RE: Question on configuring W32Time
Post your .INI file... That's probably the issue.
-----Original Message-----
From: Masthanaiah Cheekavolu [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 29, 2001 5:06 AM
To: MSWinNT Discussions
Subject: Question on configuring W32Time
Hi,
We have a pure Windows NT 4.0 single master domain model. All the desktops
and servers are NT 4.0. I have configured W32Time on PDC and made this as a
PRIMARY so that all the NT 4.0 clients (SECONDARY) can get time from this
server.
But, the problem is that the PRIMARY is not getting the time from
NTP server ( a Solaris server which is actually running NTP daemon and
getting the clock from Internet Timeserver). Does W32Time require only
another NT Server as NTP server? We don't want to open the port from one
more NT Server. Instead, make this NT Server (PRIMARY) to get the clock from
a Unix machine (NTP) which is already getting the clock from another NTP
server located on Internet.
There are no event logs getting generated when we run the service
using the command W32time.exe -automatic. 24 hours have been passed way. The
PRIMARY ( domain PDC) didn't even sync it's time with it's NTP server
(Solaris server in the same domain) and no events in event log indicating if
there were any attempts made to
contact NTP server.
The version of W32Time is: 5.00.2092.1
Time stamp of the file: 8/17/99
thanks in adv.
- Masthan
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
------
You are subscribed as [email protected]
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe send a blank email to [EMAIL PROTECTED]
