Re: The Domain Time Sych challenge

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Brent Rowell (brent_at_jrowell.com)
Date: 03/08/04 

Date: Sun, 7 Mar 2004 21:26:25 -0600

Ithink you need to check if port 123 is open for udp
Brent
"steveb" <anonymous@discussions.microsoft.com> wrote in message
news:5a3601c4045a$86567fc0$a601280a@phx.gbl...
> (This is a refined-retry on an earlier thread that got
> lost through time)
>
> This is first - after setting up hundreds of Windows 2000
> and 2003 domains in classrooms as an MCT, this is the
> first time I can't get Domain Time Sych to work, and this
> is real network.
>
> The client Win32time error says say they can't find a
> domain controller - but read on . . . it's NOT a dns
> problem.
>
> facts:
>
> 1. client dns settings point to the SBS server which is
> the only domain controller.
>
> 2. There are no DHCP options configured to look for non-
> default time servers
>
> 3. The SBS has only one network interface.
>
> 4. There is only one A-record for the SBS and it is shows
> the correct IP on the same subnet as the clients.
>
> 5. All of DNS SRV-records for domain support are present
> and point to the SBS.
>
> 6. There are no other domain problems - group policy,
> client logons, name resolution work fine and their are no
> other errors in client or server event logs.
>
> 7. windows-time-service is running on the domain
> controller and all the clients.
>
> 8. the domain conroller is successfully synchronizing with
> an external sntp time server.
>
> 9. All client machines have domain accounts.
> ( Did the XP clients have a differnet domain membership in
> the past? That's not it . . New XP installations joined
> to the domain have the same problem ? )
>
> 10. their are no network connectivity or load problems.
>
> 11. The clients do not have external time servers
> configured in the registry. (net time /querysntp)
>
> 12. The clients can be synched manually with the SBS using
> the net time \\sbs /set commmand.
>
>
> What else is there to check ?
>
>

Relevant Pages

  • Re: Remote Client Configuration
    ... the client computer to the SBS domain via connect computer wizard remotely. ... local network or via dial up VPN connection, you will use an local copy on ... connection is established, Group Policy is not applied during logon. ...
    (microsoft.public.windows.server.sbs)
  • Re: Good sites for Remote Web Workplace info/setup?
    ... on their network & see what I can do - or damage. ... I've TS'd into a server for testing, and via IIS browsing /remote, right now ... > could go for a cold one while the happy user explores SBS. ... Client Microsoft® Windows® Telephony Application Programming ...
    (microsoft.public.backoffice.smallbiz)
  • Re: Good sites for Remote Web Workplace info/setup?
    ... on their network & see what I can do - or damage. ... I've TS'd into a server for testing, and via IIS browsing /remote, right now ... > could go for a cold one while the happy user explores SBS. ... Client Microsoft® Windows® Telephony Application Programming ...
    (microsoft.public.windows.server.sbs)
  • Re: Wireless connects but only partially
    ... the Vista unable to access Internet. ... Please ensure the wireless client get IP address from SBS DHCP. ... Ensure the Vista could work fine when connect the SBS network thru cable. ...
    (microsoft.public.windows.server.sbs)
  • Re: Printers disappearing
    ... Computer (client) as the end user wasn't familiar with that. ... When the printer is listed in directory, using AddPrinter wizard, network, ... Suggestion 1: The SBS Way: ... printer published in Active Directory to client computers running Windows ...
    (microsoft.public.windows.server.sbs)