I haven't come across a way to configure this to point to the correct server? Is it possible to manage this or should I somehow try to ignore it?
thanks On 2/7/08, Free, Bob <[EMAIL PROTECTED]> wrote: > > Yep- > > Net Time uses the old LanMan NetTOD API calls and searches the browse > list for a system advertising the "TS" flag. No NTP or SNTP involved. > > The only thing Net Time has to do with NTP is that it can query or set > the HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\NTPServer > value in the registry > > -----Original Message----- > From: Ben Scott [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 06, 2008 8:06 PM > To: NT System Admin Issues > Subject: Re: Time oddity > > On Feb 6, 2008 4:30 PM, MarvinC <[EMAIL PROTECTED]> wrote: > > If I type net time from the command prompt I get current time at > > \\myIndiaDC is 4:24pm and local time (GMT +05:30) at \\myIndiaDC is > 2/7/2008 2:53 AM. > > I believe using just "NET TIME" doesn't use NTP; rather, it uses > whatever mechanism NTLM SMB has for time server location. Probably a > browser master or NTLM logon server or something. Active Directory > doesn't use those mechanisms, so this is something of a leftover. > > -- Ben > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ > ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
