Hi, I think its the stratum of the ntp server that is the cause. What stratum have you set the ntp server? 10? If so ,10 is the default stratum of the ntp server if you dont have a time source ie local clock. This is also the default stratum for the ntp client, its local clock. the client is looking for a stratum than is lower then itself. As you have said you are on a closed system you need to either attach a local time source to your server ie gps/radio/internet or lower the stratum value for the local clock on the ntp server. Regards Cillian raj sourabh <rajsourabh1@xxxxxxxxx> wrote: Hi, Thanks for the reply. But since the synchronization with the server is failing, How will cron do? Regards, Raj On Thu, Feb 10, 2011 at 10:18 AM, éåå <dengwh@xxxxxxxxxxxxx> wrote: > > > on client, please run ntp server ip address in crond. > > On Thu, 10 > Feb 2011 08:18:11 +0400, raj sourabh wrote: > > > Hi All, > > > > My > production platform is a closed system (without internet). I have > > > configured a NTP server (on rhel5.5) which is started and running > without > > error. The problem is that all windows client machines are > able to > > sychronise with my NTP server but RHEL client machines are not > able to synch > > the time. > > > > my client config are; > > > > > */etc/ntp.conf* > > ** > > *server 192.168.6.9 > > restrict default ignore > > > restrict 127.0.0.1 > > restrict 192.168.6.9 mask 255.255.255.255 nomodify > notrap noquery > > driftfile /var/lib/ntp/drift > > * > > > > i have entry of > my NTP server name in step-tickers as well. when I start ! the > > service > on client I get; > > > > [root@TESTAPP ~]# service ntpd restart > > Shutting > down ntpd: [ OK ] > > ntpd: Synchronizing with time server: [FAILED] > > > Starting ntpd: [ OK ] > > [root@TESTAPP ~]# ntpdate -q 192.168.6.9 > > > server 192.168.6.9, stratum 10, offset -0.001541, delay 0.02571 > > 10 Feb > 08:12:25 ntpdate[8822]: no server suitable for synchronization found > > > [root@TESTAPP ~]# > > > > ----- > > > > NTP server config is; > > > > *server > 127.127.1.0* > > *restrict default kod nomodify notrap noquery nopeer > > > restrict 127.127.1.0 mask 255.255.255.0 nomodify notrap noquery > > > restrict 192.168.11.0 mask 255.255.255.0 nomodify notrap > > restrict > 127.0.0.1* > > *fudge 127.127.1.0 stratum 10 > > driftfile > /var/lib/ntp/drift > > broadcastdelay 0.008 > > keys /etc/ntp/keys > > logfile > /var/log/ntp > > tos orphan 10 > > * > > > > As mentioned above, with this > server configuration windows clients are > > successfully synchronizing > time with! ntp server. but rhel servers are not. > > any help?? > > > > > Thanks, > > > > RAJ > > -- > > Best Cheer (XiaMen) Stone Works CO.,LTP. > T: > 0592-7221600 > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
