|
If you're going to fix one of them, you may as well
suggest that they fix them all. There're several as seen by a query for
NTP+Windowsserver2003 and you might want to throw in W32Time just for fun.
The confusing wording was pervasive on the
several that I sampled while looking at this question and trying to remember how
this all worked, which protocol was used, why it should even matter, etc.
There's a lot of room for improvement in the docs... I should stop before it
comes to, "hey, why don't you write a kb and/or STHU? "
;-)
-ajm
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nathan Muggli Sent: Monday, January 10, 2005 6:44 PM To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] time server The packets are identical, and NTP actually came first. I just spoke with my time developer and he confirmed that time syncs should be able to work ntp -> sntp, and sntp -> ntp. Most of the problems we've seen with interoperability have been caused by client side logic in applications doing weird things like version checks, etc.
The best way to get to the bottom of Mark's NTP phone problem is network sniffs. You could try turning on W32time debug logging on the 2000 server and see if you can catch the discovery request. I think the sniff is the best way to go. Or, you could always upgrade to 2003 J.
Regarding the Doc, it's obviously wrong (I'll get it fixed). The W32time server service in 2000 was SNTP, and 2003 its NTP.
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of joe
As Al pointed out, some MS docs need to be reviewed...
The one Al specifically pointed out "http://www.microsoft.com/technet/itsolutions/cits/interopmigration/unix/usecdirw/06wsdsu.mspx" says straight out that the Time Server is SNTP based.
Windows Server 2003 time services are based upon the Simple Network Time Protocol (SNTP); this is a simplified version of the UNIX Network Time Protocol (NTP). The packet formats of both protocols are identical, and the servers and clients for each can be used interchangeably.
The interchangeable part seems to be more of a theory or hope than strictly the real world. From chats I have had previously with people who played with the time stuff a lot it seems that it is more likely a SNTP client will be able to use a NTP source than an NTP client using a SNTP source.
joe
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Nathan
Muggli I own the time service for Windows, so I can field the OS question. The NTP server in Windows 2003 is NTP V3 RFC compliant and third party NTP clients can (well *should*) be able to sync with it. When you say "doesn't seem to recognize", is there an error message? How does it find a valid NTP server?
-Nathan
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Dean
Wells
Uncertain as to the OS in question here but Windows 2003 supports both NTP and SNTP -
--
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of joe Does your switch use/support SNTP (Simple NTP)? That is what Windows DCs support, not NTP.
joe
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Creamer,
Mark Our forest root server acts as the time server for AD domain member machines (I think that happens by default.) Do I have to take any additional steps to allow that same server to be the NTP server for a non-Windows device? The device is a phone switch on our network, and it doesn't seem to recognize that server as being a valid NTP server. Thanks!
|
Title: time server
