Re: Time sync to Windows. How?
Joshua J. Kugler said... On Friday 14 July 2006 13:07, marc wrote: Hi, I've managed to get Linux through the door at a client's site whoop, applause However, it is necessary to time sync desktop client's to a Windows server. (This is a strict requirement for reasons that I won't go into. Yes, I know how trivial it would be with a Linux server, etc.) Windows has a service called Windows Time, but I haven't managed to sync to it from the Linux boxes. Is it possible? In an attempt to approach this in a sane manner, I installed NetTIme on a Windows box for testing. This worked, up to a point - the Linux boxes could sync to it - but it has a huge flaw in that it refuses to act as a time server when it can't access the sources it syncs from - who designs this stuff? Since the server s not always connected to the net, this means that the clients lose sync, which is not acceptable in this case. Basically, all I need is a time service on Windows that will sync when sources are available, but continue to allow clients to sync to it when they are not. Any ideas or suggestions? Should get you going: http://www.google.com/search?q=ntp+windows I'm a little beyond the 101 stage, thanks. I'm asking for suggestions for a solution from folk who likely have experience with the problem. I've already googled, read, installed, etc. There's little time left to provide a solution before we'll resort to a Windows-only setup and the chance for Linux to be deployed in a Windows-only shop will have passed. I've yet to find an time server for Windows that will continue to server clients when its external sync is absent. -- Best, Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Time sync to Windows. How?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 marc wrote: Joshua J. Kugler said... On Friday 14 July 2006 13:07, marc wrote: Hi, I've managed to get Linux through the door at a client's site whoop, applause However, it is necessary to time sync desktop client's to a Windows server. (This is a strict requirement for reasons that I won't go into. Yes, I know how trivial it would be with a Linux server, etc.) Windows has a service called Windows Time, but I haven't managed to sync to it from the Linux boxes. Is it possible? In an attempt to approach this in a sane manner, I installed NetTIme on a Windows box for testing. This worked, up to a point - the Linux boxes could sync to it - but it has a huge flaw in that it refuses to act as a time server when it can't access the sources it syncs from - who designs this stuff? Since the server s not always connected to the net, this means that the clients lose sync, which is not acceptable in this case. Basically, all I need is a time service on Windows that will sync when sources are available, but continue to allow clients to sync to it when they are not. Any ideas or suggestions? Should get you going: http://www.google.com/search?q=ntp+windows I'm a little beyond the 101 stage, thanks. I'm asking for suggestions for a solution from folk who likely have experience with the problem. I've already googled, read, installed, etc. There's little time left to provide a solution before we'll resort to a Windows-only setup and the chance for Linux to be deployed in a Windows-only shop will have passed. I've yet to find an time server for Windows that will continue to server clients when its external sync is absent. Ah, so you've got a *Windows* question. Why are you asking us? Still, from Googling, I found this: http://www.windowsnetworking.com/articles_tutorials/Configuring-Windows-Time-Service.html W32Time is based on the Simple Network Time Protocol (SNTP) as specified in RFC RFC 1769 (now superceded by RFC 2030). SNTP is designed to ensure *loose* synchronization only, which in the W32Time implementation means the clocks of all Windows 2000/XP/2003 machines in a forest will agree within 20 seconds of one another (or 2 seconds difference within a particular site). Sounds pretty bad to me. - -- Ron Johnson, Jr. Jefferson LA USA Is common sense really valid? For example, it is common sense to white-power racists that whites are superior to blacks, and that those with brown skins are mud people. However, that common sense is obviously wrong. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEuOJLS9HxQb37XmcRAq5ZAJ9EdYAaf7c+dQrgj9rE0e9y7stoIACgigX3 Phf/0uPI7ep6iCLqomUOyNw= =aM4I -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Time sync to Windows. How?
marc wrote: Hi, I've managed to get Linux through the door at a client's site whoop, applause However, it is necessary to time sync desktop client's to a Windows server. (This is a strict requirement for reasons that I won't go into. Yes, I know how trivial it would be with a Linux server, etc.) Windows has a service called Windows Time, but I haven't managed to sync to it from the Linux boxes. Is it possible? In an attempt to approach this in a sane manner, I installed NetTIme on a Windows box for testing. This worked, up to a point - the Linux boxes could sync to it - but it has a huge flaw in that it refuses to act as a time server when it can't access the sources it syncs from - who designs this stuff? Since the server s not always connected to the net, this means that the clients lose sync, which is not acceptable in this case. Basically, all I need is a time service on Windows that will sync when sources are available, but continue to allow clients to sync to it when they are not. Any ideas or suggestions? Hasn't NetTime been abandoned? Anyways, how about pointing the NetTime client on the WinBox to the NetTime Server on the Winbox. Then have a separate NTP client update the time when net access is available. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Time sync to Windows. How?
nick wrote: marc wrote: Any ideas or suggestions? Hasn't NetTime been abandoned? Anyways, how about pointing the NetTime client on the WinBox to the NetTime Server on the Winbox. Then have a separate NTP client update the time when net access is available. Okay, curiousity got the better of me so I actually tried this. I booted to XP and installed NetTime from Sourceforge. As a test, I set one timeserver to 'localhost' and another to a server on the net. To 'bootstrap' the NetTime server it needed to connect to the net first. However, once started, localhost became a valid NTP server. When I shut off my cable modem, NetTime still marks 'locahost' as good and I could sync to the WinBox from another LinBox on my network. Note: It seemed to be important that 'localhost' was first in the time server list. NetTime would occasionally hang and stop serving time if the outside server was unavailable _and_ first on the list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Time sync to Windows. How?
nick said... marc wrote: Hi, I've managed to get Linux through the door at a client's site whoop, applause However, it is necessary to time sync desktop client's to a Windows server. (This is a strict requirement for reasons that I won't go into. Yes, I know how trivial it would be with a Linux server, etc.) Windows has a service called Windows Time, but I haven't managed to sync to it from the Linux boxes. Is it possible? In an attempt to approach this in a sane manner, I installed NetTIme on a Windows box for testing. This worked, up to a point - the Linux boxes could sync to it - but it has a huge flaw in that it refuses to act as a time server when it can't access the sources it syncs from - who designs this stuff? Since the server s not always connected to the net, this means that the clients lose sync, which is not acceptable in this case. Basically, all I need is a time service on Windows that will sync when sources are available, but continue to allow clients to sync to it when they are not. Any ideas or suggestions? Hasn't NetTime been abandoned? Yup, but it still works. Anyways, how about pointing the NetTime client on the WinBox to the NetTime Server on the Winbox. Then have a separate NTP client update the time when net access is available. When the server is off the net, so are the clients. When the server is off the net, the NetTime server pulls up the drawbridge. -- Best, Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Time sync to Windows. How?
nick said... nick wrote: marc wrote: Any ideas or suggestions? Hasn't NetTime been abandoned? Anyways, how about pointing the NetTime client on the WinBox to the NetTime Server on the Winbox. Then have a separate NTP client update the time when net access is available. Okay, curiousity got the better of me so I actually tried this. I booted to XP and installed NetTime from Sourceforge. As a test, I set one timeserver to 'localhost' and another to a server on the net. To 'bootstrap' the NetTime server it needed to connect to the net first. Yup, that's the problem. The network, not this particular hardware, goes on the road for client demos and into random locations - even up the odd mountain - so net connectivity is neither guaranteed nor necessarily easy to get hold of. However, once started, localhost became a valid NTP server. When I shut off my cable modem, NetTime still marks 'locahost' as good and I could sync to the WinBox from another LinBox on my network. Note: It seemed to be important that 'localhost' was first in the time server list. NetTime would occasionally hang and stop serving time if the outside server was unavailable _and_ first on the list. It's quite a nice tool - for Windows ;-) In any case, I've found NTP from these folks: http://www.meinberg.de/ which has a specific option to failover to the system clock. Funnily enough, this also glitches when the server is rebooted when off the net, but either starting the monitoring software or restarting the NTP service kicks it into life. Since the monitoring software can be started during a login - which is always going to happen in this case - that works around the problem - although I've emailed the company to see whether they can provide a config fix, or whether it's a bug. Sooo much easier with a Linux box, though :-) -- Best, Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Time sync to Windows. How?
Ron Johnson said... -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 marc wrote: Joshua J. Kugler said... On Friday 14 July 2006 13:07, marc wrote: Hi, I've managed to get Linux through the door at a client's site whoop, applause However, it is necessary to time sync desktop client's to a Windows server. (This is a strict requirement for reasons that I won't go into. Yes, I know how trivial it would be with a Linux server, etc.) Windows has a service called Windows Time, but I haven't managed to sync to it from the Linux boxes. Is it possible? In an attempt to approach this in a sane manner, I installed NetTIme on a Windows box for testing. This worked, up to a point - the Linux boxes could sync to it - but it has a huge flaw in that it refuses to act as a time server when it can't access the sources it syncs from - who designs this stuff? Since the server s not always connected to the net, this means that the clients lose sync, which is not acceptable in this case. Basically, all I need is a time service on Windows that will sync when sources are available, but continue to allow clients to sync to it when they are not. Any ideas or suggestions? Should get you going: http://www.google.com/search?q=ntp+windows I'm a little beyond the 101 stage, thanks. I'm asking for suggestions for a solution from folk who likely have experience with the problem. I've already googled, read, installed, etc. There's little time left to provide a solution before we'll resort to a Windows-only setup and the chance for Linux to be deployed in a Windows-only shop will have passed. I've yet to find an time server for Windows that will continue to server clients when its external sync is absent. Ah, so you've got a *Windows* question. Why are you asking us? Because there are Linux clients and it's likely that someone else will have tackled the same problem before. Still, from Googling, I found this: http://www.windowsnetworking.com/articles_tutorials/Configuring-Windows-Time-Service.html W32Time is based on the Simple Network Time Protocol (SNTP) as specified in RFC RFC 1769 (now superceded by RFC 2030). SNTP is designed to ensure *loose* synchronization only, which in the W32Time implementation means the clocks of all Windows 2000/XP/2003 machines in a forest will agree within 20 seconds of one another (or 2 seconds difference within a particular site). Sounds pretty bad to me. That's why you strip SNTP and apply NTP. And, in any case, you haven't asked about the degree of synchronisation that is required, so loose might be sufficient. -- Best, Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Time sync to Windows. How?
Should get you going: http://www.google.com/search?q=ntp+windows j On Friday 14 July 2006 13:07, marc wrote: Hi, I've managed to get Linux through the door at a client's site whoop, applause However, it is necessary to time sync desktop client's to a Windows server. (This is a strict requirement for reasons that I won't go into. Yes, I know how trivial it would be with a Linux server, etc.) Windows has a service called Windows Time, but I haven't managed to sync to it from the Linux boxes. Is it possible? In an attempt to approach this in a sane manner, I installed NetTIme on a Windows box for testing. This worked, up to a point - the Linux boxes could sync to it - but it has a huge flaw in that it refuses to act as a time server when it can't access the sources it syncs from - who designs this stuff? Since the server s not always connected to the net, this means that the clients lose sync, which is not acceptable in this case. Basically, all I need is a time service on Windows that will sync when sources are available, but continue to allow clients to sync to it when they are not. Any ideas or suggestions? -- Best, Marc -- Joshua Kugler Lead System Admin -- Senior Programmer http://www.eeinternet.com PGP Key: http://pgp.mit.edu/ ID 0xDB26D7CE PO Box 80086 -- Fairbanks, AK 99708 -- Ph: 907-456-5581 Fax: 907-456-3111 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
