NTP Server didn't respond error

Hi,

Our corporate time is wrong because our DCs don't get the correct time. Do I
define what time server to connect or is this something built-in to Windows
2000 Server Standard?

Thanks,

Sam

Assuming the time service is enabled on all domain computers they should
synch their times with the pdc fsmo for the domain and in a forest the
domain pdc fsmos use the pdc fsmo in the root domain to synch time. The KB
link below explains how this works and how to use an internal or external
source to synch with. They used to recommend a simple net time command which
you can use. Use net help time for more info on that command. The KB article
is very recent and now recommends a registry entry however. See the links
below. --- Steve

http://support.microsoft.com/default.aspx?scid=216734
http://64.233.167.104/search?q=cache...+service&hl=en

"Sam" <(E-Mail Removed)> wrote in message
news:u41$(E-Mail Removed)...
> Hi,
>
> Our corporate time is wrong because our DCs don't get the correct time. Do
> I define what time server to connect or is this something built-in to
> Windows 2000 Server Standard?
>
> Thanks,
>
> Sam
>

Steven,

All computers are synching their time w/ our domain controllers but the time
on the domain controller is wrong. I followed the KB article and when I went
into regedit, I realized the server is set to connect to time.microsoft.com.
I also see that some of the parameters mentioned in the KB article are
missing. Here's what I have in there:

(Default) -- REG_SZ -- (value not set)
Adj -- REG_DWORD -- 0x00023258 (156248)
LocalNTP -- REG_DWORD -- 0x00000000 (0)
msSkewPerDay -- REG_SZ -- 1005.0000
ntpserver -- REG_SZ -- time.microsoft.com
Period -- REG_SZ -- SpecialSkew
type -- REG_SZ -- NTP

Is this sufficient for our domain controller to connect to
time.microsoft.com? If it is, why would I not be able to connect and update
the time? If it is not sufficient, what am I missing?

Thanks,

Sam


"Steven L Umbach" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Assuming the time service is enabled on all domain computers they should
> synch their times with the pdc fsmo for the domain and in a forest the
> domain pdc fsmos use the pdc fsmo in the root domain to synch time. The KB
> link below explains how this works and how to use an internal or external
> source to synch with. They used to recommend a simple net time command
> which you can use. Use net help time for more info on that command. The KB
> article is very recent and now recommends a registry entry however. See
> the links below. --- Steve
>
> http://support.microsoft.com/default.aspx?scid=216734
> http://64.233.167.104/search?q=cache...+service&hl=en
>
> "Sam" <(E-Mail Removed)> wrote in message
> news:u41$(E-Mail Removed)...
>> Hi,
>>
>> Our corporate time is wrong because our DCs don't get the correct time.
>> Do I define what time server to connect or is this something built-in to
>> Windows 2000 Server Standard?
>>
>> Thanks,
>>
>> Sam
>>
>
>

Hi Sam.

That KB is very new and I have not had a problem where I had to actually
check or modify the registry so I can not really comment on that. However I
would check that your firewalls/port filters allow outbound access to port
123 udp is allowed which is what the time service uses. --- Steve


"Sam" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Steven,
>
> All computers are synching their time w/ our domain controllers but the
> time on the domain controller is wrong. I followed the KB article and when
> I went into regedit, I realized the server is set to connect to
> time.microsoft.com. I also see that some of the parameters mentioned in
> the KB article are missing. Here's what I have in there:
>
> (Default) -- REG_SZ -- (value not set)
> Adj -- REG_DWORD -- 0x00023258 (156248)
> LocalNTP -- REG_DWORD -- 0x00000000 (0)
> msSkewPerDay -- REG_SZ -- 1005.0000
> ntpserver -- REG_SZ -- time.microsoft.com
> Period -- REG_SZ -- SpecialSkew
> type -- REG_SZ -- NTP
>
> Is this sufficient for our domain controller to connect to
> time.microsoft.com? If it is, why would I not be able to connect and
> update the time? If it is not sufficient, what am I missing?
>
> Thanks,
>
> Sam
>
>
> "Steven L Umbach" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Assuming the time service is enabled on all domain computers they should
>> synch their times with the pdc fsmo for the domain and in a forest the
>> domain pdc fsmos use the pdc fsmo in the root domain to synch time. The
>> KB link below explains how this works and how to use an internal or
>> external source to synch with. They used to recommend a simple net time
>> command which you can use. Use net help time for more info on that
>> command. The KB article is very recent and now recommends a registry
>> entry however. See the links below. --- Steve
>>
>> http://support.microsoft.com/default.aspx?scid=216734
>> http://64.233.167.104/search?q=cache...+service&hl=en
>>
>> "Sam" <(E-Mail Removed)> wrote in message
>> news:u41$(E-Mail Removed)...
>>> Hi,
>>>
>>> Our corporate time is wrong because our DCs don't get the correct time.
>>> Do I define what time server to connect or is this something built-in to
>>> Windows 2000 Server Standard?
>>>
>>> Thanks,
>>>
>>> Sam
>>>
>>
>>
>
>

Steven,

Thanks again for your response. I did open up port 123 udp. I still get an
error message in the event viewer telling me that the NTP server did not
respond. Any suggestions?

Thanks,

Sam
"Steven L Umbach" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Sam.
>
> That KB is very new and I have not had a problem where I had to actually
> check or modify the registry so I can not really comment on that. However
> I would check that your firewalls/port filters allow outbound access to
> port 123 udp is allowed which is what the time service uses. --- Steve
>
>
> "Sam" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Steven,
>>
>> All computers are synching their time w/ our domain controllers but the
>> time on the domain controller is wrong. I followed the KB article and
>> when I went into regedit, I realized the server is set to connect to
>> time.microsoft.com. I also see that some of the parameters mentioned in
>> the KB article are missing. Here's what I have in there:
>>
>> (Default) -- REG_SZ -- (value not set)
>> Adj -- REG_DWORD -- 0x00023258 (156248)
>> LocalNTP -- REG_DWORD -- 0x00000000 (0)
>> msSkewPerDay -- REG_SZ -- 1005.0000
>> ntpserver -- REG_SZ -- time.microsoft.com
>> Period -- REG_SZ -- SpecialSkew
>> type -- REG_SZ -- NTP
>>
>> Is this sufficient for our domain controller to connect to
>> time.microsoft.com? If it is, why would I not be able to connect and
>> update the time? If it is not sufficient, what am I missing?
>>
>> Thanks,
>>
>> Sam
>>
>>
>> "Steven L Umbach" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Assuming the time service is enabled on all domain computers they should
>>> synch their times with the pdc fsmo for the domain and in a forest the
>>> domain pdc fsmos use the pdc fsmo in the root domain to synch time. The
>>> KB link below explains how this works and how to use an internal or
>>> external source to synch with. They used to recommend a simple net time
>>> command which you can use. Use net help time for more info on that
>>> command. The KB article is very recent and now recommends a registry
>>> entry however. See the links below. --- Steve
>>>
>>> http://support.microsoft.com/default.aspx?scid=216734
>>> http://64.233.167.104/search?q=cache...+service&hl=en
>>>
>>> "Sam" <(E-Mail Removed)> wrote in message
>>> news:u41$(E-Mail Removed)...
>>>> Hi,
>>>>
>>>> Our corporate time is wrong because our DCs don't get the correct time.
>>>> Do I define what time server to connect or is this something built-in
>>>> to Windows 2000 Server Standard?
>>>>
>>>> Thanks,
>>>>
>>>> Sam
>>>>
>>>
>>>
>>
>>
>
>