|
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
- RE: [ActiveDir] time server joe
- RE: [ActiveDir] time server Dean Wells
- RE: [ActiveDir] time server Nathan Muggli
- RE: [ActiveDir] time server Creamer, Mark
- RE: [ActiveDir] time server Rick Kingslan
- RE: [ActiveDir] time server Robert Williams \(RRE\)
- RE: [ActiveDir] time server Celone, Mike
- RE: [ActiveDir] time server Ken Cornetet
- RE: [ActiveDir] time server Mulnick, Al
- RE: [ActiveDir] time server Renouf, Phil
- RE: [ActiveDir] time server Nathan Muggli
- RE: [ActiveDir] time server Mulnick, Al
