Sponsored Content
Operating Systems AIX Sync AIX system time with Windows Domain Controller Post 302159453 by murderfly on Thursday 17th of January 2008 07:42:45 PM
Old 01-17-2008
Sync AIX system time with Windows Domain Controller

Yeah so, I have setup a domain controller (windows 2003) active directory machine and it is managing couple of windows servers and workstation. I also have couple of AIX machines that need to have the same time as other windows server and workstation hanging off of that domain controller.

Now DC uses SNTP to sync time with the windows machine but AIX can't use DC as a time server or can it? I can't install an NTP server on the domain controller because it'll conflict with the kerberos/SNTP time service. I've considered making AIX machines smbclient so it is managed by Active Directory and provide time sync service to the AIX machine, but not sure if this is possible. Can an AIX machine be in an Active Directory domain? Anyway I also though about setting up an NTP server on the member windows machine ans use that machines system time as stratum 1 time server for the AIX machine.

This test network is setup to simulate business hour and all the application that runs on it. So I need a turn-key (or close) solution so I can set the time on DC (or any member machine) any time I want (forward/backword/different timezone etc) and the rest of the windows and AIX machines will automatically (or semi?) synchronize their system clock to this newly set time. How would you do it? If you need further clarification feel free to ask. Thanks
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Linux as a Domain Controller

First question, can Linux be configured to be the domain controller on a network with Microsoft computers? If so, where can I find information about configuring Linux for this purpose? (4 Replies)
Discussion started by: cstovall
4 Replies

2. Windows & DOS: Issues & Discussions

How to: Linux BOX in Windows Domain (w/out joining the domain)

Dear Expert, i have linux box that is running in the windows domain, BUT did not being a member of the domain. as I am not the System Administrator so I have no control on the server in the network, such as modify dns entry , add the linux box in AD and domain record and so on that relevant. ... (2 Replies)
Discussion started by: regmaster
2 Replies

3. Linux

Adding linux system into windows domain

Hi i need to add linux system into windows network .Tell me the procedure if anybody know. Thanks & Regards, Veerababu. (1 Reply)
Discussion started by: veerababu
1 Replies

4. UNIX for Dummies Questions & Answers

Samba change domain controller

Hello people i have a samba and they changed domain controller from a windows 2003 to a windows 2008, there is a problem with the version of samba maybe incompatibilities i dont know what show me this domain_client_validate: unable to validate password for user xxxx in domain xxxx to Domain... (0 Replies)
Discussion started by: enkei17
0 Replies

5. Debian

Testing a SAMBA Domain Controller

Hello,,, We have an existing(working) MS PDC in our office. I have already installed SAMBA with LDAP Authentication on a TEST machine (on same LAN). But, am unable to join a WinXP machine to this domain. in smb.conf i have: WORKGROUP = mydomain and tried to join the XP machine to... (0 Replies)
Discussion started by: coolatt
0 Replies

6. UNIX for Dummies Questions & Answers

how to fix these preoblems in samba in order to act as domain controller

Dear all I now working on samba in order to act as domain controller, but I have some problems in the configuration file that I don't how to solve it, so I hope you able to give me some help: the warnings and the configuration I made : dos charset = 850 unix charset = ISO8859-1 ... (0 Replies)
Discussion started by: hard_revenge
0 Replies

7. Solaris

Solaris 11 server as Primary Domain Controller

Hi, All of our servers run Solaris (currently 10, but looking to upgrade to 11). In each of our offices we have a server configured as a Primary Domain Controller via Samba to provide naming services to our Windoze users. I would like to continue with that arrangement, but I would also like... (2 Replies)
Discussion started by: wgkorb
2 Replies

8. Red Hat

How to create domain controller in Linux for windows client?

Hi Team I have configured a linux dns server locally. Its fully working on linux clients but not windows client as its can't ping host by name. someone told me to create domain controller for working this to windows client as well. I am new in linux and not aware how to create the domain and add... (8 Replies)
Discussion started by: boby.kumar
8 Replies

9. UNIX for Dummies Questions & Answers

Ubuntu Server 14.04 LTS - domain controller configuration (SAMBA)

Hello! Never configured a Linux server from a scratch. Reviewed the official documentation and dozens of different "how to", but now one of them helped me to solve the issue. The need: My final goal is to install a small network (later with around 10 stations) where I can controle the... (0 Replies)
Discussion started by: AQwert
0 Replies
TIMED(8)						    BSD System Manager's Manual 						  TIMED(8)

NAME
timed -- time server daemon SYNOPSIS
timed [-dMt] [-F host ...] [-G netgroup] [-i network | -n network] DESCRIPTION
The timed utility is a time server daemon which is normally invoked at boot time from the rc(8) file. It synchronizes the host's time with the time of other machines, which are also running timed, in a local area network. These time servers will slow down the clocks of some machines and speed up the clocks of others to bring them to the average network time. The average network time is computed from measurements of clock differences using the ICMP timestamp request message. The following options are available: -d Enable debugging mode; do not detach from the terminal. -F host ... Create a list of trusted hosts. The timed utility will only accept trusted hosts as masters. If it finds an untrusted host claiming to be master, timed will suppress incoming messages from that host and call for a new election. This option implies the -M option. If this option is not specified, all hosts on the connected networks are treated as trustworthy. -G netgroup Specify a netgroup of trustworthy hosts, in addition to any masters specified with the -M flag. This option may only be specified once. -i network Add network to the list of networks to ignore. All other networks to which the machine is directly connected are used by timed. This option may be specified multiple times to add more than one network to the list. -M Allow this host to become a timed master if necessary. -n network Add network to the list of allowed networks. All other networks to which the machine is directly connected are ignored by timed. This option may be specified multiple times to add more than one network to the list. -t Enable tracing of received messages and log to the file /var/log/timed.log. Tracing can be turned on or off while timed is running with the timedc(8) utility. The -n and -i flags are mutually exclusive and require as arguments real networks to which the host is connected (see networks(5)). If nei- ther flag is specified, timed will listen on all connected networks. A timed running without the -M nor -F flags will always remain a slave. If the -F flag is not used, timed will treat all machines as trust- worthy. The timed utility is based on a master-slave scheme. When timed is started on a machine, it asks the master for the network time and sets the host's clock to that time. After that, it accepts synchronization messages periodically sent by the master and calls adjtime(2) to per- form the needed corrections on the host's clock. It also communicates with date(1) in order to set the date globally, and with timedc(8), a timed control utility. If the machine running the master becomes unreachable, the slaves will elect a new master from among those slaves which are running with at least one of the -M and -F flags. At startup timed normally checks for a master time server on each network to which it is connected, except as modified by the -n and -i options described above. It will request synchronization service from the first master server located. If permitted by the -M or -F flags, it will provide synchronization service on any attached networks on which no trusted master server was detected. Such a server propagates the time computed by the top-level master. The timed utility will periodically check for the presence of a master on those networks for which it is operating as a slave. If it finds that there are no trusted masters on a network, it will begin the election process on that network. One way to synchronize a group of machines is to use ntpd(8) to synchronize the clock of one machine to a distant standard or a radio receiver and -F hostname to tell its timed to trust only itself. Messages printed by the kernel on the system console occur with interrupts disabled. This means that the clock stops while they are print- ing. A machine with many disk or network hardware problems and consequent messages cannot keep good time by itself. Each message typically causes the clock to lose a dozen milliseconds. A time daemon can correct the result. Messages in the system log about machines that failed to respond usually indicate machines that crashed or were turned off. Complaints about machines that failed to respond to initial time settings are often associated with ``multi-homed'' machines that looked for time masters on more than one network and eventually chose to become a slave on the other network. WARNINGS
Temporal chaos will result if two or more time daemons attempt to adjust the same clock. If both timed and another time daemon are run on the same machine, ensure that the -F flag is used, so that timed never attempts to adjust the local clock. The protocol is based on UDP/IP broadcasts. All machines within the range of a broadcast that are using the TSP protocol must cooperate. There cannot be more than a single administrative domain using the -F flag among all machines reached by a broadcast packet. Failure to fol- low this rule is usually indicated by complaints concerning ``untrusted'' machines in the system log. FILES
/var/log/timed.log tracing file for timed /var/log/timed.masterlog log file for master timed SEE ALSO
date(1), adjtime(2), gettimeofday(2), icmp(4), netgroup(5), networks(5), ntpd(8), timedc(8) R. Gusella and S. Zatti, TSP: The Time Synchronization Protocol for UNIX 4.3BSD. HISTORY
The timed utility appeared in 4.3BSD. BSD
May 11, 1993 BSD
All times are GMT -4. The time now is 05:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy