r...@rsrvmon:~# ntpdate 192.168.11.8 1 Oct 13:27:35 ntpdate[7645]: adjust time server 192.168.11.8 offset 0.012268 sec
r...@rsrvmon:/etc# locate ntp.conf r...@rsrvmon:/etc# r...@vrsrvmon:/etc# ntpdate -v 1 Oct 13:29:12 ntpdate[7713]: ntpdate [email protected] Wed May 13 21:05:58 UTC 2009 (1) Ubuntu 8.04 LTS vs Windows 2003 Server that was setup before me -- but it works. Stan On Thu, Oct 1, 2009 at 12:31 PM, Mike Raley <[email protected]> wrote: > Chris, > > The firewall on the linux server is turned off completely for this part, so > I know that's not it. It very well could be a firewall issue on the DC, > however, without a login I cannot confirm. I can only believe what I'm > told, and that is that it's on and working... > > I am curious if you have any special settings in your ntp.conf file > however? > > Thanks! > Mike > > --- On Wed, 9/30/09, Chris <[email protected]> wrote: > > > From: Chris <[email protected]> > > Subject: Re: using a MS SNTP server for linux > > To: [email protected] > > Date: Wednesday, September 30, 2009, 9:21 PM > > I work in an environment with > > hundreds of Linux and Windows systems and we use our DC's as > > the time source for all of our systems. While it is true > > that older Windows systems did not work well, I have not > > seen any issues with 2k3's time server as an NTP server for > > Linux clients. > > > > Do you know if the Windows server has it's firewall > > enabled? I could see that causing problems, that friggin > > firewall is a total pain in the @$!. And, are you sure that > > iptables on your Linux server is not blocking the outbound > > ntp query? Check to make sure that UDP port 123 is open. You > > can run iptables -L to show your iptables ruleset (if Ubuntu > > uses iptables). > > > > Good luck, > > > > Chris Adams > > > > > > > > On Sep 29, 2009, at 10:34 AM, Mike Raley wrote: > > > > > Rick, any advice offered is never a waste of > > time! Unfortunately MS claims, NTP will just > > work. LIES! ;) > > > > > > specifically this is what I'm getting: > > > r...@host-name:~# ntpdate <ip address> > > > 29 Sep 10:31:49 ntpdate[3946]: no server suitable for > > synchronization found > > > > > > which from my investigations is what I would get given > > MS's crappy time deamon. > > > > > > thanks anyways! > > > > > > Mike > > > --- On Tue, 9/29/09, Rick White <[email protected]> > > wrote: > > > > > >> From: Rick White <[email protected]> > > >> Subject: Re: using a MS SNTP server for linux > > >> To: [email protected] > > >> Date: Tuesday, September 29, 2009, 10:10 AM > > >> No wisdom here, but idle googling > > >> turned up this TechNet document on the subject: > > >> Appendix H: Configuring Time Services for a > > Heterogeneous > > >> UNIX and Windows Environment > > >> http://technet.microsoft.com/en-us/library/bb463171..aspx > > >> > > >> Some solutions involve editing the Windows > > registry, which > > >> is OTQ, but the last section: > > >> http://technet.microsoft.com/en-us/library/bb463171.aspx#EAAA > > >> might possibly be relevant. > > >> > > >> If this is completely off-base, sorry to waste > > your time. > > >> > > >> Rick > > >> > > >> --- On Tue, 9/29/09, Mike Raley <[email protected]> > > >> wrote: > > >> > > >>> From: Mike Raley <[email protected]> > > >>> Subject: using a MS SNTP server for linux > > >>> To: [email protected] > > >>> Date: Tuesday, September 29, 2009, 9:44 AM > > >>> Morning all, > > >>> > > >>> I figure I know the unfortunate answer to my > > question, > > >> but > > >>> I'm hoping the wisdom of this crowd will once > > again > > >> prove me > > >>> wrong. I have an Ubuntu server which > > needs to use a > > >>> Windows 2003 Domain Controller as it's > > authoritative > > >> time > > >>> server. Yes, I know, this is an > > abomination, but in > > >>> this case 100% unavoidable. It's either > > this or > > >> wildly > > >>> off on time (bad). Has anyone actually > > gotten this > > >> to > > >>> work? Using NTP is out as MS uses SNTP > > (broken as > > >>> usual). I've tried msntp also to no > > avail. > > >>> Gladly taking suggestions! > > >>> > > >>> Oh, in addition, I do not even have login > > rights to > > >> the DC, > > >>> much less Administrator privileges, so > > changing that > > >> is out > > >>> of the question. > > >>> > > >>> Thanks! > > >>> Mike > > >>> > > >>> > > >>> > > >>> > > >> > > >> > > >> > > >> > > > > > > > > > > > > > > >
