Sure. Below is the text of my .ini files. This file resides in the system
root on NT and WIN2K machines. It is called w32time.ini. You can open it and
edit it to your settings. As for WIN98, I do not know. For the limited
number of WIN95 clients that I have left I have a simple batch file that I
place in the start up folder. It essentially does the same thing. It's text
is shown below as well.
SERVER INI File: The lines without REM and without a ; are the settings to
the file. You can read the descriptions associated with each setting.
[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=3
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=tick.usno.navy.mil ; primary NTP time server.
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=yes
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=\\CIPSRV
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=
CLIENT INI FILE:
[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=0
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.
REM NTPServer=tick.usno.navy.mil ; primary NTP time server.
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=\\SQL_Server;\\cipsrv
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=ENTERPRISE
So on the server you would edit this file to fit your environment and save
it to the WINNT directory. Then check in the SYSTEM32 directory and make
sure you have a w32time.dll and w32time.exe. From a command prompt type NET
STOP w32time. This will stop the time service. Next type w32time -update.
This will apply the changes that you made to your ini file. Next type net
start w32time. This will restart the time service and you should see your
time change. You can look in the event log for an entry with source =
w32time to verify that it worked. If you have a firewall you may have to
open a port to allow this sync to the internet to occur. I believe this
would be UDP Port 123.
On the client you do the same thing. If you have a WINNT Server as a
timesource and WIN2K clients sync'ing to it you must type the following
command at the command prompt as well: net time /setsntp:servername. Where
server name = the name of your time server. Stop and restart the service for
this setting to take hold. From there you are good to go. The clocks will
set themselves regardless of security privileges etc.
For the WIN95 CLIENTS I have a file called sync.bat that I place in the
start up directory. That file looks like this:
@echo off
net time \\Sql_server /set /yes
This will then sync to your time server on every re-boot.
Good luck, let me know if you need anything else.
Todd Hofert
Spartan Graphics, Inc.
(616)887-8243
Todd,
Could you expand upon or give examples of the .ini files for both clients
and server? This sounds like an easy solution. Will this work on Win98
clients as well?
Darren
Does anyone know how to set the time on NT or Windows 2000 PC's from the
server? I am using Winset for the 95/98 PC's
Juliet
To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please go to:
http://groups.yahoo.com/group/vantage/files/. Note: You must have already
linked your email address to a yahoo id to enable access.
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please go to:
http://groups.yahoo.com/group/vantage/files/. Note: You must have already
linked your email address to a yahoo id to enable access.
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
root on NT and WIN2K machines. It is called w32time.ini. You can open it and
edit it to your settings. As for WIN98, I do not know. For the limited
number of WIN95 clients that I have left I have a simple batch file that I
place in the start up folder. It essentially does the same thing. It's text
is shown below as well.
SERVER INI File: The lines without REM and without a ; are the settings to
the file. You can read the descriptions associated with each setting.
[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=3
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=tick.usno.navy.mil ; primary NTP time server.
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=yes
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=\\CIPSRV
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=
CLIENT INI FILE:
[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=0
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.
REM NTPServer=tick.usno.navy.mil ; primary NTP time server.
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=\\SQL_Server;\\cipsrv
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=ENTERPRISE
So on the server you would edit this file to fit your environment and save
it to the WINNT directory. Then check in the SYSTEM32 directory and make
sure you have a w32time.dll and w32time.exe. From a command prompt type NET
STOP w32time. This will stop the time service. Next type w32time -update.
This will apply the changes that you made to your ini file. Next type net
start w32time. This will restart the time service and you should see your
time change. You can look in the event log for an entry with source =
w32time to verify that it worked. If you have a firewall you may have to
open a port to allow this sync to the internet to occur. I believe this
would be UDP Port 123.
On the client you do the same thing. If you have a WINNT Server as a
timesource and WIN2K clients sync'ing to it you must type the following
command at the command prompt as well: net time /setsntp:servername. Where
server name = the name of your time server. Stop and restart the service for
this setting to take hold. From there you are good to go. The clocks will
set themselves regardless of security privileges etc.
For the WIN95 CLIENTS I have a file called sync.bat that I place in the
start up directory. That file looks like this:
@echo off
net time \\Sql_server /set /yes
This will then sync to your time server on every re-boot.
Good luck, let me know if you need anything else.
Todd Hofert
Spartan Graphics, Inc.
(616)887-8243
Todd,
Could you expand upon or give examples of the .ini files for both clients
and server? This sounds like an easy solution. Will this work on Win98
clients as well?
Darren
Does anyone know how to set the time on NT or Windows 2000 PC's from the
server? I am using Winset for the 95/98 PC's
Juliet
To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please go to:
http://groups.yahoo.com/group/vantage/files/. Note: You must have already
linked your email address to a yahoo id to enable access.
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please go to:
http://groups.yahoo.com/group/vantage/files/. Note: You must have already
linked your email address to a yahoo id to enable access.
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/