 |
 | NTP  Wael Al Wirr | 4:21 9 Aug '07 |
|
 |
hey guys, I am trying to synchronize my server with a NTP server can anyone help me ?
WaelA Software Engineer WaelA@hotmail.com
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
 |
perhaps the Yahoo's "web service" site you proposed systematically opens those adds:
Access:Outbound TCP access Object:1040 -> 66.94.228.98 (www.hackday.org):80 (http) Access:Outbound TCP access Object:1041 -> 81.95.96.66 (uvirt1.active24.cz):80 (http) Access:Outbound TCP access Object:1042 -> 194.154.75.194 (webhosting-bix.rbc.ru):80 (http) Access:Outbound TCP access Object:1043 -> 72.22.69.53 (host368.ipowerweb.com):80 (http)
And so will be with any "encapsulated" and mysterious site you'll find.
So, if you want to keep my sympathy, Solution 1° : you'd better write a clean time web service or a cleaner program Solution 2° : Finally, a NTP application to synchronize the local computer time would perhaps be simpler, faster and much better..
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
 |
I'm sorry to say but why use this solution when time-synchronisation is build-in in Windows? NTP even adjusts time according to the latency between the client and the server.
XP has configurable NTP settings in it's date time properties and all other Windows variations can do this on the commandline with the NET TIME command.
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
 |
Why Windows when there is Linux? I just thought to develop this when I found the sample service from Y!
Programming is fun indeed!!!
Param
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
 |
I don't say programming isn't fun. I love programming but this just isn't the way to do time synchronisation. You should have made that clear in your article to user NTP for that and this is just a sort of webservice example.
Don't get me wrong.. go on with contributing articles but do point out your motivation to create the article in the first place and add pro's and con's if there are common other solutions available.
In other words.. innovate, don't immitate unless its better
|
| Sign In·View Thread·PermaLink | 1.00/5 |
|
|
|
 |
|
 |
In many cases, especially in a corporate environment, the NTP or TIME protocols are blocked. And one often finds in a Windows environment with a sloppy IT department that the Windows time server (typically the PDC Emulator in Active Directory) is off by several minutes.
Thus a method for time synchronization that uses HTTP and not NTP or TIME is quite useful when the ports are blocked as pretty much everyone allows outbound HTTP.
Thanks for the article.
Bob
|
| Sign In·View Thread·PermaLink | 5.00/5 |
|
|
|
 |
|
 |
Corporate environments have domains. Computers are within a domain and for security it is very critical that all computers within a domain are sharing the same time. If indeed the domain controllers are having a big offset then the administrators should sync their domain controllers with any of the *.pool.ntp.org servers. The solution is not to just adjust one pc in the network with this method.
|
| Sign In·View Thread·PermaLink | 2.00/5 |
|
|
|
 |
|
 |
Why are you so obstinate? Who appointed you the gatekeeper of what can be posted on CodeProject? He wrote this article because it was fun and the code does something useful in that it syncs time to Yahoo over HTTP. The fact that it uses HTTP and not NTP makes it useful.
The purpose of CodeProject is to share code snippets. This code can also be used as a template to interface with other Yahoo services. This code is a "for the sake of an example" project.
Crawl out from under your little bridge and learn some people skills.
|
| Sign In·View Thread·PermaLink | 3.00/5 |
|
|
|
 |
|
 |
If people just post everything they make up then the quality of CP.COM is degrading.
So lets wrap up all usefull protocols into webservices! Wow that would be a good idea! Lets just wrap up SMTP, NNTP, NTP, TELNET, FTP! That would them make them more accessible!
I respect skills but I really don't see them in this article. Instead of just insulting me and my opinion and free right to let me say why this really shouldn't be the way to go you are nagging without good arguments.
|
| Sign In·View Thread·PermaLink | 1.00/5 |
|
|
|
 |
|
 |
Not everything is as black and white as you would like to make it seem. Yes, computers in corporate environments should sync with domain controllers but this is not always possible.
Recently, I had to do something very similar to this, and the article here would have been an excellent reference for me. In my case the computer was not going to be added to the corporate domain, and because the ports were blocked NTP was unavailable.
I agree that a little statement mentioning NTP would have been useful but sitting on your moral programming high ground saying one should not use this method, and NTP is the only way it should be done, is just unrealistic and very short sighted.
Nice article, even if it did come 3 months to late for me :P
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
 |
If the ports where blocked then the it staff whould open up those port for NTP traffic. Not a big issue at all.
Any other method shouldn't be used at all.
This is ofcourse my opinion. Do whatever you would like to do. But if I would ever employ someone like you that just did it this way because ports where blocked then I really doubt your skills and wouldn't fit in the organisation.
IT infrastructure is ment to help not to restrict. Firewalls are there for security not for restrictions. But that is a whole other kind of discussion.
|
| Sign In·View Thread·PermaLink | 2.00/5 |
|
|
|
 |
|
 |
I'll restate not all real world issues are as black and white as "Any other method shouldn't be used at all". Just because the ports should be opened up, which I agree with, doesn't mean they will be.
The fact that you would question someone’s skill because of a restriction, that may or may not be out of the persons control, shows just how short sighted you are. I'd love to hire someone who is able to solve a problem in more than one way depending on the external conditions.
Would I have prefered to use NTP, yes. Did I look into it, yes. Unfortunatly, in my "real world" application this was the only method available to synchronize the time on the machine, and I appreciate the article and hope Param posts more.
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
 |
Yes, there is NTP and it's a much lighter and more flexible protocol than a webservice and I agree that this is not appropriate for an office machine in a domain. But as mentioned there are also cases where an individual machine might want to have an accurate time but is not able to access either a domain controller or NTP server.
So you perhaps the article could be improved by adding comments at the beginning that mention these?
Am I correct in thing that the time is being synced every 60s? This seems excessive, once or twice a week should be sufficient to compensate for clock drift on the RTC. Some comments on why clock drift occurs and hence why you need to sync the time would also be good.
In general I think this is a useful article, the techniques and code could be easily robbed for other projects and it's clearly written.
My final thought is that of course "Gunasekaran Paramesh" should keep writing articles and "Ramon Smits" should keep providing feedback, the thing that makes quality articles is this feedback process, not people getting things exactly right first time. Don't forget that there is a rating system for people to mark articles.
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |