Need Windows Time Service Expert
|
From: jawdoc on 13 Mar 2007 18:25 I really need some help. I administer a network with ~ 12 nodes all xp pro sp2. Server is 2003 SBS. The time on the SBS is correct and is the only server on the domain and of course is the DC. About half on my xp pro machines refuse to keep the manually updated time after having to manually change them because of the early DST. They are all set to the SBS as the sntp. If I manually change them after the time service update cycles they return to one hour earlier. net time output>>> C:\net time Current time at \\CAOMSFS1 is 3/13/2007 3:31PM Local time (GMT-05:00) at \\CAOMSFS1 is 3/13/2007 4:31 PM The command completed successfully. "CAOMSFS1" is my SBS of course. I can stop w32time service of course and it will stick. What I am doing wrong on this? Is there a patch that I need to apply to some of the machines?
From: Russ Grover (SBITS.Biz) on 13 Mar 2007 19:32 Well I don't know if I'm a "Time" Expert. But if all the PC's have All Patches and the server has all Updates and Patches, Things should work, First make sure you Server is in the correct time zone (It sounds like the server's time is correct?) When PC's login to the server they "SHOULD" get the time from the server However I've had cases where they don't Add This line to the SBS Login Script and see if it changes the PC's times, and keeps them there. net time \\CAOMSFS1 /set /yes There are some other things you can do also But Making sure All PC's are Updated and in the Correct TIME ZONE is the first step. If you Don't have WSUS or SBS2003R2 doing this for you. On Each PC go to. http://update.microsoft.com And Make sure they are updated. Once they are all updated, then we can look at other things. Russ -- Russell Grover SBITS.Biz Microsoft Certified Small Business Specialist. MCP, MCPS, MCNPS, (MCP-SBS) support @ SBITS.Biz Remote Computer Support http://www.SBITS.Biz "jawdoc" <drbrooks(a)msoms.com> wrote in message news:1173824759.061707.15830(a)d57g2000hsg.googlegroups.com... >I really need some help. I administer a network with ~ 12 nodes all > xp pro sp2. > Server is 2003 SBS. The time on the SBS is correct and is the only > server on the domain and of course is the DC. About half on my xp pro > machines refuse to keep the manually updated time after having to > manually change them because of the early DST. They are all set to > the SBS as the sntp. If I manually change them after the time service > update cycles they return to one hour earlier. > net time output>>> > C:\net time Current time at http://update.microsoft.com\\CAOMSFS1 is > 3/13/2007 3:31PM > > Local time (GMT-05:00) at \\CAOMSFS1 is 3/13/2007 4:31 PM > > The command completed successfully. > > "CAOMSFS1" is my SBS of course. > > I can stop w32time service of course and it will stick. > What I am doing wrong on this? Is there a patch that I need to apply > to some of the machines? >
From: kj on 13 Mar 2007 19:48 jawdoc wrote: > I really need some help. I administer a network with ~ 12 nodes all > xp pro sp2. > Server is 2003 SBS. The time on the SBS is correct and is the only > server on the domain and of course is the DC. About half on my xp pro > machines refuse to keep the manually updated time after having to > manually change them because of the early DST. They are all set to > the SBS as the sntp. If I manually change them after the time service > update cycles they return to one hour earlier. > net time output>>> > C:\net time Current time at \\CAOMSFS1 is 3/13/2007 3:31PM > > Local time (GMT-05:00) at \\CAOMSFS1 is 3/13/2007 4:31 PM > > The command completed successfully. > > "CAOMSFS1" is my SBS of course. > > I can stop w32time service of course and it will stick. > What I am doing wrong on this? Is there a patch that I need to apply > to some of the machines? Sidestepping the father time jokes for the time being. Time sync in a domain is automatic unless something blocks it or something (or someone) mucked with it. First, on one of the problem childs, type "net time /setsntp:" Then type; "w32tm /config /syncfromflags:domhier" and "w32tm /resync /rediscover" If it still is off; Net stop "windows time" Net start "windows time" If it is still off; net stop "windows time" w32tm /unregister w32tm /register net start "windows time" ....and if it is still off...., The only cause beyound this I'm aware of is something is blocking SNTP protocol, or the Client is running in a virtual machine under Virtual Server 2005 R2. -- /kj
From: Steve on 14 Mar 2007 00:00 Please clarify-you applied the DST patch to all 12 but only 6 of them were correctly patched and the other 6 you had to manually try to change the time? "jawdoc" <drbrooks(a)msoms.com> wrote in message news:1173824759.061707.15830(a)d57g2000hsg.googlegroups.com... >I really need some help. I administer a network with ~ 12 nodes all > xp pro sp2. > Server is 2003 SBS. The time on the SBS is correct and is the only > server on the domain and of course is the DC. About half on my xp pro > machines refuse to keep the manually updated time after having to > manually change them because of the early DST. They are all set to > the SBS as the sntp. If I manually change them after the time service > update cycles they return to one hour earlier. > net time output>>> > C:\net time Current time at \\CAOMSFS1 is 3/13/2007 3:31PM > > Local time (GMT-05:00) at \\CAOMSFS1 is 3/13/2007 4:31 PM > > The command completed successfully. > > "CAOMSFS1" is my SBS of course. > > I can stop w32time service of course and it will stick. > What I am doing wrong on this? Is there a patch that I need to apply > to some of the machines? >
From: jawdoc on 14 Mar 2007 16:01 On Mar 13, 11:00 pm, "Steve" <newsgr...(a)public.lan> wrote: > Please clarify-you applied the DST patch to all 12 but only 6 of them were > correctly patched and the other 6 you had to manually try to change the > time? > > "jawdoc" <drbro...(a)msoms.com> wrote in message > > news:1173824759.061707.15830(a)d57g2000hsg.googlegroups.com... > > > > >I really need some help. I administer a network with ~ 12 nodes all > > xp pro sp2. > > Server is 2003 SBS. The time on the SBS is correct and is the only > > server on the domain and of course is the DC. About half on my xp pro > > machines refuse to keep the manually updated time after having to > > manually change them because of the early DST. They are all set to > > the SBS as the sntp. If I manually change them after the time service > > update cycles they return to one hour earlier. > > net time output>>> > > C:\net time Current time at \\CAOMSFS1 is 3/13/2007 3:31PM > > > Local time (GMT-05:00) at \\CAOMSFS1 is 3/13/2007 4:31 PM > > > The command completed successfully. > > > "CAOMSFS1" is my SBS of course. > > > I can stop w32time service of course and it will stick. > > What I am doing wrong on this? Is there a patch that I need to apply > > to some of the machines?- Hide quoted text - > > - Show quoted text - Found the DST patch and applied to all. All is well. Thanks for the help!
|
Pages: 1 Prev: SMTP could not connect to any DNS server - Event ID 2013 Next: How to reinstall OWA? |