Results 1 to 8 of 8

Thread: Time Sync in 2003

  1. #1
    WORLDe Guest

    Time Sync in 2003

    Hi,
    We have a domain setup with about 100 users.
    95% of the users' PCs all have the same time on their PC clock.
    All users are running XP Pro and all are logged into the domain.

    From my understanding, WIN Serv 2003 Active Directory should automatically
    sync all PCs throughout the day so that they should all have the same system
    clock.

    The remaining 5% of PCS are maybe 6- 8 minutes fast and, unless I manually
    change the clocks, they will never sync to the AD.

    Also, to force a time sync when they login. I have added a logon script to
    group policy. Even after this, their PCs still do not sync the time.


    Is there a way I can sync their PC clocks remotely over the LAN?
    Why is this happening?
    What should I check into?





  2. #2
    Meinolf Weber Guest

    Re: Time Sync in 2003

    Hello WORLDe,

    The PDCEmulator is the time master of the domain, all other DC's will sync
    with that one and all member serveres and clients use one available DC for
    there sync, doesn't matter which one. So the dc's, member servers and clients
    connect to the above mentioned time providers and request the time.

    Configure the PDCEmulator to an external time source with this:
    w32tm /config /manualpeerlist:peers /syncfromflags:manual /reliable:yes /update

    With "peers" you can set the time source, either DNS name (time.windows.com)
    or an ip address from a reliable time source.

    Here you can find some of them:
    http://www.pool.ntp.org/

    Client configuration:
    To configure a client computer for automatic domain time synchronization

    w32tm /config /syncfromflags:domhier /update

    After that run:

    net stop w32time

    net start w32time

    Also make sure that all clients have no firewall running where port 123 NTP
    is blocked.

    Best regards

    Meinolf Weber
    Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    no rights.
    ** Please do NOT email, only reply to Newsgroups
    ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

    > Hi,
    > We have a domain setup with about 100 users.
    > 95% of the users' PCs all have the same time on their PC clock.
    > All users are running XP Pro and all are logged into the domain.
    > From my understanding, WIN Serv 2003 Active Directory should
    > automatically sync all PCs throughout the day so that they should all
    > have the same system clock.
    >
    > The remaining 5% of PCS are maybe 6- 8 minutes fast and, unless I
    > manually change the clocks, they will never sync to the AD.
    >
    > Also, to force a time sync when they login. I have added a logon
    > script to group policy. Even after this, their PCs still do not sync
    > the time.
    >
    > Is there a way I can sync their PC clocks remotely over the LAN?
    > Why is this happening?
    > What should I check into?




  3. #3
    WORLDe Guest

    Re: Time Sync in 2003

    Do I need to run the w32tm /config /syncfromflags:domhier /update command on
    every user's PC?



    "Meinolf Weber" wrote:

    > Hello WORLDe,
    >
    > The PDCEmulator is the time master of the domain, all other DC's will sync
    > with that one and all member serveres and clients use one available DC for
    > there sync, doesn't matter which one. So the dc's, member servers and clients
    > connect to the above mentioned time providers and request the time.
    >
    > Configure the PDCEmulator to an external time source with this:
    > w32tm /config /manualpeerlist:peers /syncfromflags:manual /reliable:yes /update
    >
    > With "peers" you can set the time source, either DNS name (time.windows.com)
    > or an ip address from a reliable time source.
    >
    > Here you can find some of them:
    > http://www.pool.ntp.org/
    >
    > Client configuration:
    > To configure a client computer for automatic domain time synchronization
    >
    > w32tm /config /syncfromflags:domhier /update
    >
    > After that run:
    >
    > net stop w32time
    >
    > net start w32time
    >
    > Also make sure that all clients have no firewall running where port 123 NTP
    > is blocked.
    >
    > Best regards
    >
    > Meinolf Weber
    > Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    > no rights.
    > ** Please do NOT email, only reply to Newsgroups
    > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
    >
    > > Hi,
    > > We have a domain setup with about 100 users.
    > > 95% of the users' PCs all have the same time on their PC clock.
    > > All users are running XP Pro and all are logged into the domain.
    > > From my understanding, WIN Serv 2003 Active Directory should
    > > automatically sync all PCs throughout the day so that they should all
    > > have the same system clock.
    > >
    > > The remaining 5% of PCS are maybe 6- 8 minutes fast and, unless I
    > > manually change the clocks, they will never sync to the AD.
    > >
    > > Also, to force a time sync when they login. I have added a logon
    > > script to group policy. Even after this, their PCs still do not sync
    > > the time.
    > >
    > > Is there a way I can sync their PC clocks remotely over the LAN?
    > > Why is this happening?
    > > What should I check into?

    >
    >
    >


  4. #4
    Meinolf Weber Guest

    Re: Time Sync in 2003

    Hello WORLDe,

    If they make problems you should do that. But the command can also be executed
    with script.

    Best regards

    Meinolf Weber
    Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    no rights.
    ** Please do NOT email, only reply to Newsgroups
    ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

    > Do I need to run the w32tm /config /syncfromflags:domhier /update
    > command on every user's PC?
    >
    > "Meinolf Weber" wrote:
    >
    >> Hello WORLDe,
    >>
    >> The PDCEmulator is the time master of the domain, all other DC's will
    >> sync with that one and all member serveres and clients use one
    >> available DC for there sync, doesn't matter which one. So the dc's,
    >> member servers and clients connect to the above mentioned time
    >> providers and request the time.
    >>
    >> Configure the PDCEmulator to an external time source with this: w32tm
    >> /config /manualpeerlist:peers /syncfromflags:manual /reliable:yes
    >> /update
    >>
    >> With "peers" you can set the time source, either DNS name
    >> (time.windows.com) or an ip address from a reliable time source.
    >>
    >> Here you can find some of them:
    >> http://www.pool.ntp.org/
    >> Client configuration:
    >> To configure a client computer for automatic domain time
    >> synchronization
    >> w32tm /config /syncfromflags:domhier /update
    >>
    >> After that run:
    >>
    >> net stop w32time
    >>
    >> net start w32time
    >>
    >> Also make sure that all clients have no firewall running where port
    >> 123 NTP is blocked.
    >>
    >> Best regards
    >>
    >> Meinolf Weber
    >> Disclaimer: This posting is provided "AS IS" with no warranties, and
    >> confers
    >> no rights.
    >> ** Please do NOT email, only reply to Newsgroups
    >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
    >>> Hi,
    >>> We have a domain setup with about 100 users.
    >>> 95% of the users' PCs all have the same time on their PC clock.
    >>> All users are running XP Pro and all are logged into the domain.
    >>> From my understanding, WIN Serv 2003 Active Directory should
    >>> automatically sync all PCs throughout the day so that they should
    >>> all
    >>> have the same system clock.
    >>> The remaining 5% of PCS are maybe 6- 8 minutes fast and, unless I
    >>> manually change the clocks, they will never sync to the AD.
    >>>
    >>> Also, to force a time sync when they login. I have added a logon
    >>> script to group policy. Even after this, their PCs still do not sync
    >>> the time.
    >>>
    >>> Is there a way I can sync their PC clocks remotely over the LAN?
    >>> Why is this happening?
    >>> What should I check into?




  5. #5
    WORLDe Guest

    Re: Time Sync in 2003

    How would I do this remotely across the LAN?


    "Meinolf Weber" wrote:

    > Hello WORLDe,
    >
    > If they make problems you should do that. But the command can also be executed
    > with script.
    >
    > Best regards
    >
    > Meinolf Weber
    > Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    > no rights.
    > ** Please do NOT email, only reply to Newsgroups
    > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
    >
    > > Do I need to run the w32tm /config /syncfromflags:domhier /update
    > > command on every user's PC?
    > >
    > > "Meinolf Weber" wrote:
    > >
    > >> Hello WORLDe,
    > >>
    > >> The PDCEmulator is the time master of the domain, all other DC's will
    > >> sync with that one and all member serveres and clients use one
    > >> available DC for there sync, doesn't matter which one. So the dc's,
    > >> member servers and clients connect to the above mentioned time
    > >> providers and request the time.
    > >>
    > >> Configure the PDCEmulator to an external time source with this: w32tm
    > >> /config /manualpeerlist:peers /syncfromflags:manual /reliable:yes
    > >> /update
    > >>
    > >> With "peers" you can set the time source, either DNS name
    > >> (time.windows.com) or an ip address from a reliable time source.
    > >>
    > >> Here you can find some of them:
    > >> http://www.pool.ntp.org/
    > >> Client configuration:
    > >> To configure a client computer for automatic domain time
    > >> synchronization
    > >> w32tm /config /syncfromflags:domhier /update
    > >>
    > >> After that run:
    > >>
    > >> net stop w32time
    > >>
    > >> net start w32time
    > >>
    > >> Also make sure that all clients have no firewall running where port
    > >> 123 NTP is blocked.
    > >>
    > >> Best regards
    > >>
    > >> Meinolf Weber
    > >> Disclaimer: This posting is provided "AS IS" with no warranties, and
    > >> confers
    > >> no rights.
    > >> ** Please do NOT email, only reply to Newsgroups
    > >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
    > >>> Hi,
    > >>> We have a domain setup with about 100 users.
    > >>> 95% of the users' PCs all have the same time on their PC clock.
    > >>> All users are running XP Pro and all are logged into the domain.
    > >>> From my understanding, WIN Serv 2003 Active Directory should
    > >>> automatically sync all PCs throughout the day so that they should
    > >>> all
    > >>> have the same system clock.
    > >>> The remaining 5% of PCS are maybe 6- 8 minutes fast and, unless I
    > >>> manually change the clocks, they will never sync to the AD.
    > >>>
    > >>> Also, to force a time sync when they login. I have added a logon
    > >>> script to group policy. Even after this, their PCs still do not sync
    > >>> the time.
    > >>>
    > >>> Is there a way I can sync their PC clocks remotely over the LAN?
    > >>> Why is this happening?
    > >>> What should I check into?

    >
    >
    >


  6. #6
    Lanwench [MVP - Exchange] Guest

    Re: Time Sync in 2003

    WORLDe <WORLDe@discussions.microsoft.com> wrote:
    > How would I do this remotely across the LAN?


    (pardon my jumping in)

    You could set it up in a computer startup script, applied via group policy.
    But as Meinolf wrote, you probably won't need to. Fix the server first &
    have all clients reboot once. See if it resolves the problem.
    >
    >
    > "Meinolf Weber" wrote:
    >
    >> Hello WORLDe,
    >>
    >> If they make problems you should do that. But the command can also
    >> be executed with script.
    >>
    >> Best regards
    >>
    >> Meinolf Weber
    >> Disclaimer: This posting is provided "AS IS" with no warranties, and
    >> confers no rights.
    >> ** Please do NOT email, only reply to Newsgroups
    >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
    >>
    >>> Do I need to run the w32tm /config /syncfromflags:domhier /update
    >>> command on every user's PC?
    >>>
    >>> "Meinolf Weber" wrote:
    >>>
    >>>> Hello WORLDe,
    >>>>
    >>>> The PDCEmulator is the time master of the domain, all other DC's
    >>>> will sync with that one and all member serveres and clients use one
    >>>> available DC for there sync, doesn't matter which one. So the dc's,
    >>>> member servers and clients connect to the above mentioned time
    >>>> providers and request the time.
    >>>>
    >>>> Configure the PDCEmulator to an external time source with this:
    >>>> w32tm /config /manualpeerlist:peers /syncfromflags:manual
    >>>> /reliable:yes /update
    >>>>
    >>>> With "peers" you can set the time source, either DNS name
    >>>> (time.windows.com) or an ip address from a reliable time source.
    >>>>
    >>>> Here you can find some of them:
    >>>> http://www.pool.ntp.org/
    >>>> Client configuration:
    >>>> To configure a client computer for automatic domain time
    >>>> synchronization
    >>>> w32tm /config /syncfromflags:domhier /update
    >>>>
    >>>> After that run:
    >>>>
    >>>> net stop w32time
    >>>>
    >>>> net start w32time
    >>>>
    >>>> Also make sure that all clients have no firewall running where port
    >>>> 123 NTP is blocked.
    >>>>
    >>>> Best regards
    >>>>
    >>>> Meinolf Weber
    >>>> Disclaimer: This posting is provided "AS IS" with no warranties,
    >>>> and confers
    >>>> no rights.
    >>>> ** Please do NOT email, only reply to Newsgroups
    >>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
    >>>>> Hi,
    >>>>> We have a domain setup with about 100 users.
    >>>>> 95% of the users' PCs all have the same time on their PC clock.
    >>>>> All users are running XP Pro and all are logged into the domain.
    >>>>> From my understanding, WIN Serv 2003 Active Directory should
    >>>>> automatically sync all PCs throughout the day so that they should
    >>>>> all
    >>>>> have the same system clock.
    >>>>> The remaining 5% of PCS are maybe 6- 8 minutes fast and, unless I
    >>>>> manually change the clocks, they will never sync to the AD.
    >>>>>
    >>>>> Also, to force a time sync when they login. I have added a logon
    >>>>> script to group policy. Even after this, their PCs still do not
    >>>>> sync the time.
    >>>>>
    >>>>> Is there a way I can sync their PC clocks remotely over the LAN?
    >>>>> Why is this happening?
    >>>>> What should I check into?





  7. #7
    Meinolf Weber Guest

    Re: Time Sync in 2003

    Hello Lanwench [MVP - Exchange],

    Nothing to pardon, i am always happy if someone agrees with me. :-)

    Best regards

    Meinolf Weber
    Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    no rights.
    ** Please do NOT email, only reply to Newsgroups
    ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

    > WORLDe <WORLDe@discussions.microsoft.com> wrote:
    >
    >> How would I do this remotely across the LAN?
    >>

    > (pardon my jumping in)
    >
    > You could set it up in a computer startup script, applied via group
    > policy. But as Meinolf wrote, you probably won't need to. Fix the
    > server first & have all clients reboot once. See if it resolves the
    > problem.
    >
    >> "Meinolf Weber" wrote:
    >>
    >>> Hello WORLDe,
    >>>
    >>> If they make problems you should do that. But the command can also
    >>> be executed with script.
    >>>
    >>> Best regards
    >>>
    >>> Meinolf Weber
    >>> Disclaimer: This posting is provided "AS IS" with no warranties, and
    >>> confers no rights.
    >>> ** Please do NOT email, only reply to Newsgroups
    >>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
    >>>> Do I need to run the w32tm /config /syncfromflags:domhier /update
    >>>> command on every user's PC?
    >>>>
    >>>> "Meinolf Weber" wrote:
    >>>>
    >>>>> Hello WORLDe,
    >>>>>
    >>>>> The PDCEmulator is the time master of the domain, all other DC's
    >>>>> will sync with that one and all member serveres and clients use
    >>>>> one available DC for there sync, doesn't matter which one. So the
    >>>>> dc's, member servers and clients connect to the above mentioned
    >>>>> time providers and request the time.
    >>>>>
    >>>>> Configure the PDCEmulator to an external time source with this:
    >>>>> w32tm /config /manualpeerlist:peers /syncfromflags:manual
    >>>>> /reliable:yes /update
    >>>>>
    >>>>> With "peers" you can set the time source, either DNS name
    >>>>> (time.windows.com) or an ip address from a reliable time source.
    >>>>>
    >>>>> Here you can find some of them:
    >>>>> http://www.pool.ntp.org/
    >>>>> Client configuration:
    >>>>> To configure a client computer for automatic domain time
    >>>>> synchronization
    >>>>> w32tm /config /syncfromflags:domhier /update
    >>>>> After that run:
    >>>>>
    >>>>> net stop w32time
    >>>>>
    >>>>> net start w32time
    >>>>>
    >>>>> Also make sure that all clients have no firewall running where
    >>>>> port 123 NTP is blocked.
    >>>>>
    >>>>> Best regards
    >>>>>
    >>>>> Meinolf Weber
    >>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
    >>>>> and confers
    >>>>> no rights.
    >>>>> ** Please do NOT email, only reply to Newsgroups
    >>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
    >>>>>> Hi,
    >>>>>> We have a domain setup with about 100 users.
    >>>>>> 95% of the users' PCs all have the same time on their PC clock.
    >>>>>> All users are running XP Pro and all are logged into the domain.
    >>>>>> From my understanding, WIN Serv 2003 Active Directory should
    >>>>>> automatically sync all PCs throughout the day so that they
    >>>>>> should
    >>>>>> all
    >>>>>> have the same system clock.
    >>>>>> The remaining 5% of PCS are maybe 6- 8 minutes fast and, unless I
    >>>>>> manually change the clocks, they will never sync to the AD.
    >>>>>> Also, to force a time sync when they login. I have added a logon
    >>>>>> script to group policy. Even after this, their PCs still do not
    >>>>>> sync the time.
    >>>>>>
    >>>>>> Is there a way I can sync their PC clocks remotely over the LAN?
    >>>>>> Why is this happening?
    >>>>>> What should I check into?




  8. #8
    Phillip Windell Guest

    Re: Time Sync in 2003

    I like to attack things in a more simplified and direct way.

    Maybe the workstation's membership in the domain is fouled up.
    It has happened to me before.

    1. Unjoin the "problem" machines from the Domain (make them a workgroup)
    2. Delete the machine accounts from the Domain if they were "left behind"
    afterwards
    3. Rejoin them to the Domain and move them to the desired OU.

    See what happens now.
    If it still doesn't work at least you now will know the machine's
    memberships is "good".

    --
    Phillip Windell
    www.wandtv.com

    The views expressed, are my own and not those of my employer, or Microsoft,
    or anyone else associated with me, including my cats.
    -----------------------------------------------------



Similar Threads

  1. Server Time and Time Sync
    By Somchai in forum Windows Server Help
    Replies: 1
    Last Post: 29-12-2008, 01:16 AM
  2. Setting my PDC Emulator to time sync to external time source
    By aja44 in forum Windows Server Help
    Replies: 1
    Last Post: 17-05-2008, 07:38 PM
  3. Can't time sync with Windows 2003 Server Std.
    By Calab in forum Windows Server Help
    Replies: 5
    Last Post: 10-04-2008, 01:35 PM
  4. time sync from NTP in win 2003
    By kyosang in forum Active Directory
    Replies: 3
    Last Post: 21-02-2008, 11:51 AM
  5. Time Sync on a Windows 2003 Server
    By Russyan in forum Active Directory
    Replies: 3
    Last Post: 04-06-2007, 11:55 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,642,738,462.02253 seconds with 17 queries