W32 time sync - NT4 vs XP
Hi all. I've just started a new job and I've been asked to try to sort out an issue occuring between our NT4 PDC and the XP Pro clients. The last guy that worked here tried some sort of workaround by installing the Win2k/XP Time Service on the NT box, but it isn't documented so we don't know what he's done (if he d ...
Hi all.
I've just started a new job and I've been asked to try to sort out an issue occuring between our NT4 PDC and the XP Pro clients. The last guy that worked here tried some sort of workaround by installing the Win2k/XP Time Service on the NT box, but it isn't documented so we don't know what he's done (if he did anything in the first place.) Regardless, it doesn't appear to be working.
Has anyone come across a solution to getting the two versions of WStime working together properly?
I suggested syncing with an external source such as time.microsoft.com, but the policy in place here dictates that clients are absolutly not allowed to access the Internet - Port 80 or otherwise...
Any help would be great.
I've just started a new job and I've been asked to try to sort out an issue occuring between our NT4 PDC and the XP Pro clients. The last guy that worked here tried some sort of workaround by installing the Win2k/XP Time Service on the NT box, but it isn't documented so we don't know what he's done (if he did anything in the first place.) Regardless, it doesn't appear to be working.
Has anyone come across a solution to getting the two versions of WStime working together properly?
I suggested syncing with an external source such as time.microsoft.com, but the policy in place here dictates that clients are absolutly not allowed to access the Internet - Port 80 or otherwise...
Any help would be great.
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Well, here's what I do:
1) I don't use the 2K/XP time service at all, I simply disable the service after stopping them.
2) I install a client side time app, this can be set to appear only in the system tray or even stay completely hidden.
The app I use is free and no spyware attached, it's called Abouttime and can be found on www.tucows.com
The problem however is that you need something that will work over what port ?!?
Also how is anyone seeing the web if you block port 80 ;(
I re-read your post and figured out that your company doesn't allow any net access, except I assuming the PDC ?!? If so then I did a google search of a product that may help you out here, it's called NeoClock.
http://www.google.com/search?num=100&...rver+service%22
http://www.neol.fr/uk/neoclock/nwin_f.htm
The only other solution I can think of for you is to use something like Abouttime on the PDC so this is as accurate as possible and then setting up some kind of time server service that will work on the PDC, perhaps that neoclock will do this as well, then you don't have to use Abouttime. But it does look like you may need to spend some money however
1) I don't use the 2K/XP time service at all, I simply disable the service after stopping them.
2) I install a client side time app, this can be set to appear only in the system tray or even stay completely hidden.
The app I use is free and no spyware attached, it's called Abouttime and can be found on www.tucows.com
The problem however is that you need something that will work over what port ?!?
Also how is anyone seeing the web if you block port 80 ;(
I re-read your post and figured out that your company doesn't allow any net access, except I assuming the PDC ?!? If so then I did a google search of a product that may help you out here, it's called NeoClock.
http://www.google.com/search?num=100&...rver+service%22
http://www.neol.fr/uk/neoclock/nwin_f.htm
The only other solution I can think of for you is to use something like Abouttime on the PDC so this is as accurate as possible and then setting up some kind of time server service that will work on the PDC, perhaps that neoclock will do this as well, then you don't have to use Abouttime. But it does look like you may need to spend some money however
What can be done, and what I have done before on legacy NT 4 networks, is install the free service on the NT boxes from MS and configure it in a manner that can let you sync the whole network. I wouldn't even setup the gateway entry on the old NT DCs so they wouldn't be able to transmit traffic outside the network, but they still needed a time source. So, I configured the IIS box to sync with a USNO time server ( http://tycho.usno.navy.mil/ntp.html) and then setup the DCs to sync with this box. This way, an existing box with external access could get accurate time and then it would propogate down to the rest of the network. There is also a registry hack for setting a time source.
Using TimeServ
http://support.microsoft.com/default.aspx?scid=kb;en-us;232255
How to Sync up Domain Time Sources
http://support.microsoft.com/default.aspx?scid=kb;en-us;131715
How to Sync time on Win2K boxes with NT Time Sources
http://support.microsoft.com/default.aspx?scid=kb;en-us;258059
Time Source Modes
http://support.microsoft.com/default.aspx?scid=kb;en-us;174557
Using TimeServ
http://support.microsoft.com/default.aspx?scid=kb;en-us;232255
How to Sync up Domain Time Sources
http://support.microsoft.com/default.aspx?scid=kb;en-us;131715
How to Sync time on Win2K boxes with NT Time Sources
http://support.microsoft.com/default.aspx?scid=kb;en-us;258059
Time Source Modes
http://support.microsoft.com/default.aspx?scid=kb;en-us;174557
