Re: Time Synchronization

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

Hi,

Thanks for your update!

I am sorry for the delayed response due to weekend. Please understand that
the newsgroups are staffed weekdays by Microsoft Support professionals to
answer your systems and applications questions. Your understanding is
greatly appreciated!

Basically speaking, there are two levels of time synchronization in a
domain environment. The first level is the internal time synchronization.
In a domain environment, the workstations synch the time with the domain
controller. This can keep the time consistency internally. The second level
is the external time synchronization. This means that the domain controller
synchronizes the time with an external time source. When we join a
workstation into a domain, the workstations are configured to synchronize
the time with the domain controller by default so that it is not necessary
to configure the time settings on the internal workstations.

Regarding the time service issue occurred on the SBS 2003 server, I would
like to provide you with the following action plan:

I. Make sure that the Time service on the SBS 2003 server is enabled.

For the SBS server, the time server may be disabled by some software.
Please try the following steps to enable the time service on the SBS server:

1. Open Services console in 'Administrative Tools'.

2. Double-click Windows Time service. Change the startup type from Disable
to Automatic.

3. Open Registry editor (regedit); navigate to the following registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\

Double-click 'Type' value in the right panel. Change the value data from
NoSync to NT5DS

4. Go to the service console, double-click the Windows Time service and
click 'Start' button to start the service.

The above steps will make the server to respond the internal time synch
requests. Go to the Windows XP workstation, open a command prompt, run the
following command to perform a test:

w32tm /monitor /computers:localhost

[ex]. C:\>w32tm /monitor /computers:localhost
localhost [127.0.0.1]:
ICMP: 0ms delay.
NTP: +0.0000000s offset from local clock
RefID: ntdev-dc-10.ntdev.microsoft.com [x.x.x.x]
The computer returned on the RefID line is the time server with whom the
client is synchronizing its time.

II. For ISA server is installed on the SBS box, ensure that the packet
filters for time synchronization has been properly configured:
1. In the ISA Server management tool, expand the management nodes that are
beneath your server name.

2. Expand the Access Policy branch to view the list of access policies.

3. Right-click IP Packet Filters, point to New, and then click Filter to
start the New IP Packet Filter Wizard.

4. Type a descriptive name for the filter (such as "SNTP Allow Filter"
(without the quotation marks)), and then click Next.

5. Click Allow packet transmission as the Filter Mode, and then click Next.

6. Click Custom as the filter type, and then click Next.

7. On the Filter Settings page, click UDP for the IP protocol, click "Send
receive" for the direction, "All ports" as the local port, click "Fixed
port" as the remote port, use port 123 as the remote port number, and then
click Next.

8. Keep the default settings by clicking Next through the next two wizard
pages, and then click Finish at the Completing The New IP Packet Filter
Wizard page.

9. Go to Monitoring\Services and restart the Firewall service. Check if the
issue disappears.

For more info, see:
323621 How To Configure the Simple Network Time Protocol (SNTP) on ISA
Server
http://support.microsoft.com/?id=323621

III. Reconfigure the Windows time service
Open a command prompt and run the following commands to re-configure the
time service to sync time with time.nist.gov:

w32tm /config /manualpeerlist:time.nist.gov,0x8 /syncfromflags:MANUAL

w32tm /config /update

net stop w32time

net start w32time

And then please try to test to see if the issue be fixed.

I appreciate you taking time to perform the tests. I am happy to be
assistance and look forward to your reply!

Have a nice day!

Sincerely,

Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>Thread-Topic: Time Synchronization
>thread-index: AcXsfyJU7iEkeimDTSKyS9gcrouOvw==
>X-WBNR-Posting-Host: 66.160.67.150
>From: =?Utf-8?B?QUFT?= <AAS@xxxxxxxxxxxxxxxxxxxxxxxxx>
>References: <D18A19E6-90B2-4513-89D5-555AF2589852@xxxxxxxxxxxxx>
<S1Ief.157776$iC7.49210@xxxxxxxxxxxxxxxxxxxxxx>
<J861ET16FHA.1240@xxxxxxxxxxxxxxxxxxxxx>
>Subject: Re: Time Synchronization
>Date: Fri, 18 Nov 2005 12:32:03 -0800
>Lines: 140
>Message-ID: <6E3A5FCD-4B8F-46E2-B9D2-1F21A9E4EA01@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:223622
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Thanks Jenny:
>
>I tried your suggestions. But the clients did not sync. I had previously
>followed the instructions in Article 875424 and run the following command
on
>the SBS Server:
>w32tm /config /manualpeerlist:NTP_server_IP_Address,0x8
/syncfromflags:MANUAL
>
>I had provided the NIST servers IP address. Do I need to undo that?
>--
>AAS
>
>
>""Jenny wu [MSFT]"" wrote:
>
>> Hi,
>>
>> Thanks for using the SBS newsgroup! Also thanks for Jim's input.
>>
>> For your description, I understand that you have some problem in
>> synchronizing time between the SBS server and client computers. If I am
off
>> base, please don't hesitate to let me know.
>>
>> Please follow below steps to refresh the time service to synchronize
time
>> with time server:
>>
>> The w32time service problem may prevent client from properly accessing
your
>> domain resources. Please try to start the Windows Time service (w32time)
>> and see if the issue can be resolved.
>>
>> A. Let''s open a command prompt and run the following commands to stop
and
>> restart w32time service:
>>
>> *****net stop w32time
>> *****net start w32time
>>
>> Also check if you have a hardware router/firewall in front of your SBS
>> server, if so, please open Registry Editor (regedit), go to
>>
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type
>> , change the value from whatever to Nt5DS and restart the W32Time
service.
>>
>> Maue sure the service''s startup type is set to automatic.
>>
>> B. Please run the following command to make client workstations
synchronize
>> time with the SBS 2003 server:
>> net time /setsntp:<SBS_Server_Name>
>> NOTE: Replace <SBS_Server_Name> with the real server name of the SBS
2003
>> server.
>> After doing the above steps, reboot client workstations and then try to
>> logon the domain. How about the result?
>> For more info:
>> 816042 How to configure the Windows Time service on a Windows Server
>> 2003-based
>> http://support.microsoft.com/?id=816042
>>
>> Hope above information helps! If you have any further concern or
question
>> on the issue please let me know. I am happy to be assistance of you and
>> look forward to your reply!
>>
>> Have a nice day!
>>
>> Sincerely,
>>
>> Jenny Wu
>> Microsoft CSS Online Newsgroup Support
>> Get Secure! - www.microsoft.com/security
>> ======================================================
>> This newsgroup only focuses on SBS technical issues. If you have issues
>> regarding other Microsoft products, you'd better post in the
corresponding
>> newsgroups so that they can be resolved in an efficient and timely
manner.
>> You can locate the newsgroup here:
>> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>>
>> When opening a new thread via the web interface, we recommend you check
the
>> "Notify me of replies" box to receive e-mail notifications when there
are
>> any updates in your thread. When responding to posts via your
newsreader,
>> please "Reply to Group" so that others may learn and benefit from your
>> issue.
>>
>> Microsoft engineers can only focus on one issue per thread. Although we
>> provide other information for your reference, we recommend you post
>> different incidents in different threads to keep the thread clean. In
doing
>> so, it will ensure your issues are resolved in a timely manner.
>>
>> For urgent issues, you may want to contact Microsoft CSS directly.
Please
>> check http://support.microsoft.com for regional support phone numbers.
>>
>> Any input or comments in this thread are highly appreciated.
>> ======================================================
>> This posting is provided "AS IS" with no warranties, and confers no
rights.
>>
>> --------------------
>> >From: "Jim Staunton" <sbsbofh@xxxxxxxxxxxxxx>
>> >Newsgroups: microsoft.public.windows.server.sbs
>> >References: <D18A19E6-90B2-4513-89D5-555AF2589852@xxxxxxxxxxxxx>
>> >Subject: Re: Time Synchronization
>> >Lines: 20
>> >X-Priority: 3
>> >X-MSMail-Priority: Normal
>> >X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>> >X-RFC2646: Format=Flowed; Original
>> >Message-ID: <S1Ief.157776$iC7.49210@xxxxxxxxxxxxxxxxxxxxxx>
>> >X-Complaints-To: abuse@xxxxxxxxxxxx
>> >Organization: EasyNews, UseNet made Easy!
>> >X-Complaints-Info: Please be sure to forward a copy of ALL headers
>> otherwise we will be unable to process your complaint properly.
>> >Date: Wed, 16 Nov 2005 15:15:01 GMT
>> >Path:
>>
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
>>
ne.de!border2.nntp.dca.giganews.com!nntp.giganews.com!cyclone1.gnilink.net!g
>>
nilink.net!newsfeed.news2me.com!newsfeed2.easynews.com!easynews.com!easynews
>> !easynews-local!fe08.news.easynews.com.POSTED!not-for-mail
>> >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:222840
>> >X-Tomcat-NG: microsoft.public.windows.server.sbs
>> >
>> >
>> >"AAS" <AAS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >news:D18A19E6-90B2-4513-89D5-555AF2589852@xxxxxxxxxxxxxxxx
>> >>[snip] One of the
>> >> articles i reviewed talked about making sure that the SBS NTP 123
filter
>> >> is
>> >> properly set. Those instructions are for ISA 2000. In ISA 2004 when
i
>> >> check
>> >> for that particular filter i do not find it. Should i add a new
packet
>> >> filter? Will this impact the syncing of the clients to the server?
All
>> >> clients are running XP SP2. Any help is greatly appreciated. Thanks
in
>> >> advance.
>> >
>> >Any filters for ISA are to allow the server to talk to the outside
world
>> or
>> >the outside world to talk to the server. Your workstations and your
>> server
>> >can always talk to each other and ISA doesn't get in the way.
>> >
>> >Jim
>> >
>> >
>> >
>>
>>
>

.

Quantcast