That did not help.... Digging alittle bit further into this I see that my CM is actually pulling clock from my ESX box. Not sure why that is happening.
Anyone else running ESX for their Call Manager having the same issue? On Wed, Jan 14, 2009 at 10:41 PM, karuna durai <karu...@gmail.com> wrote: > Hi, > After editing the ntp.conf file please fo to CMD as > C:\Prog file\cisco\xntp> ntpdate -b <IPADD of NTP> > > > pls try this and let me know > > > > > > On Thu, Jan 15, 2009 at 4:33 AM, Ryan Trauernicht < > ryanstudyvo...@gmail.com> wrote: > >> Any reason why CM will not keep its NTP clock. >> I have a local router with the following commands: >> >> ntp master 3 >> ntp source loopback0 (IP address is 192.168.187.1) >> >> >> I have edited the c:\WINNT\System32\Drivers\Etc\ntp.config >> >> >> My file looks like: >> server 192.168.187.1 # Set Local Clock to Authoritive Time Source >> fudge 192.168.187.1 stratum 5 # Resets Stratum from default 3 to 5 >> driftfile C:\WINNT\system32\drivers\etc\ntp.drift # path for drift file >> >> I stopped the Network Time Protocol service and I run "ntpdate.exe >> 192.168.187.1" command from the cmd. >> >> That sets the clock to sync to NTP router just fine. After I reboot CM it >> goes back to GMT it looks like. I see it trying to sync but it never does. >> I have waited over 15mins and nothing. >> >> Thanks, >> Ryan Trauernicht >> >> >
