system hangs- logging w32time errors

  • Thread starter Thread starter msshapira
  • Start date Start date
M

msshapira

Hi all,
running windows 2003 R2 server running role as DC (AD and FS only)
in the past few days domain has been hanging (either server itself hang or
it refuses logons from all domain computers)
logs show various errors but none seem to be related to the problem.
However, w32time error repeat themselves ID 22, 36, 12
could any or these events cause DC to hang?

Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 22
Date: 08/06/2008
Time: 14:34:00
User: N/A
Computer: SERVER2003
Description:
The time provider NtpServer encountered an error while digitally signing the
NTP response for peer 192.168.3.147:123. NtpServer cannot provide secure
(signed) time to the client and will ignore the request. The error was: Not
enough storage is available to process this command. (0x80070008)

(the peer IP varies)
Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 36
Date: 08/05/2008
Time: 10:14:23
User: N/A
Computer: SERVER2003
Description:
The time service has not synchronized the system time for 86400 seconds
because none of the time service providers provided a usable time stamp. The
time service is no longer synchronized and cannot provide the time to other
clients or update the system clock. Monitor the system events displayed in
the Event Viewer to make sure that a more serious problem does not exist.

Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 12
Date: 05/05/2008
Time: 14:02:34
User: N/A
Computer: SERVER2003
Description:
Time Provider NtpClient: This machine is configured to use the domain
hierarchy to determine its time source, but it is the PDC emulator for the
domain at the root of the forest, so there is no machine above it in the
domain hierarchy to use as a time source. It is recommended that you either
configure a reliable time service in the root domain, or manually configure
the PDC to synchronize with an external time source. Otherwise, this machine
will function as the authoritative time source in the domain hierarchy. If
an external time source is not configured or used for this computer, you may
choose to disable the NtpClient.
 
Hello msshapira,

No, the time service shouldn't create this kind of errors. Is this the only
DC in your domain? The errors occur because you server has no external time
source setup. So if you have internet available you can choose an external
time server and sync the time.
On a command prompt type on the PDCEmulator (if you have only one DC, easy):

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/

What do you mean with hanging, slow client logons? Run dcdaig, netdiag and
repadmin /showreps from a command line to check for errors. Additional make
sure all Domain machines use only internal domain DNS server.

Please post also an unedited ipconfig /all from the server and one problem
client.

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 all,
> running windows 2003 R2 server running role as DC (AD and FS only)
> in the past few days domain has been hanging (either server itself
> hang or
> it refuses logons from all domain computers)
> logs show various errors but none seem to be related to the problem.
> However, w32time error repeat themselves ID 22, 36, 12
> could any or these events cause DC to hang?
> Event Type: Warning
> Event Source: W32Time
> Event Category: None
> Event ID: 22
> Date: 08/06/2008
> Time: 14:34:00
> User: N/A
> Computer: SERVER2003
> Description:
> The time provider NtpServer encountered an error while digitally
> signing the
> NTP response for peer 192.168.3.147:123. NtpServer cannot provide
> secure
> (signed) time to the client and will ignore the request. The error
> was: Not
> enough storage is available to process this command. (0x80070008)
> (the peer IP varies)
> Event Type: Warning
> Event Source: W32Time
> Event Category: None
> Event ID: 36
> Date: 08/05/2008
> Time: 10:14:23
> User: N/A
> Computer: SERVER2003
> Description:
> The time service has not synchronized the system time for 86400
> seconds
> because none of the time service providers provided a usable time
> stamp. The
> time service is no longer synchronized and cannot provide the time to
> other
> clients or update the system clock. Monitor the system events
> displayed in
> the Event Viewer to make sure that a more serious problem does not
> exist.
> Event Type: Warning
> Event Source: W32Time
> Event Category: None
> Event ID: 12
> Date: 05/05/2008
> Time: 14:02:34
> User: N/A
> Computer: SERVER2003
> Description:
> Time Provider NtpClient: This machine is configured to use the domain
> hierarchy to determine its time source, but it is the PDC emulator for
> the
> domain at the root of the forest, so there is no machine above it in
> the
> domain hierarchy to use as a time source. It is recommended that you
> either
> configure a reliable time service in the root domain, or manually
> configure
> the PDC to synchronize with an external time source. Otherwise, this
> machine
> will function as the authoritative time source in the domain
> hierarchy. If
> an external time source is not configured or used for this computer,
> you may
> choose to disable the NtpClient.
 
hi thanks for your help

NETDAIG ERRORS:

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenger Service', <20> 'WINS' names is missing.

no errors in DCDAIG or REPADMIN.
ipconfig (server):


Windows IP Configuration



Host Name . . . . . . . . . . . . : server2003

Primary Dns Suffix . . . . . . . : yatka.students.local

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : yatka.students.local

students.local



Ethernet adapter Local Area Connection 3:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : NVIDIA nForce Networking Controller #2

Physical Address. . . . . . . . . : 00-19-DB-F4-7D-EF

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.3.2

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.3.1

DNS Servers . . . . . . . . . . . : 192.168.3.2

IPCONFIG (client):


Windows IP Configuration



Host Name . . . . . . . . . . . . : students30

Primary Dns Suffix . . . . . . . : yatka.students.local

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : yatka.students.local

students.local



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
Ethernet NIC

Physical Address. . . . . . . . . : 00-19-DB-60-70-75

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.3.101

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.3.1

DHCP Server . . . . . . . . . . . : 192.168.3.2

DNS Servers . . . . . . . . . . . : 192.168.3.2

Lease Obtained. . . . . . . . . . : Wednesday, June 11, 2008
12:08:36 PM

Lease Expires . . . . . . . . . . : Thursday, June 19, 2008 12:08:36
PM


thanks alot
Menachem


"Meinolf Weber" wrote:

> Hello msshapira,
>
> No, the time service shouldn't create this kind of errors. Is this the only
> DC in your domain? The errors occur because you server has no external time
> source setup. So if you have internet available you can choose an external
> time server and sync the time.
> On a command prompt type on the PDCEmulator (if you have only one DC, easy):
>
> 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/
>
> What do you mean with hanging, slow client logons? Run dcdaig, netdiag and
> repadmin /showreps from a command line to check for errors. Additional make
> sure all Domain machines use only internal domain DNS server.
>
> Please post also an unedited ipconfig /all from the server and one problem
> client.
>
> 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 all,
> > running windows 2003 R2 server running role as DC (AD and FS only)
> > in the past few days domain has been hanging (either server itself
> > hang or
> > it refuses logons from all domain computers)
> > logs show various errors but none seem to be related to the problem.
> > However, w32time error repeat themselves ID 22, 36, 12
> > could any or these events cause DC to hang?
> > Event Type: Warning
> > Event Source: W32Time
> > Event Category: None
> > Event ID: 22
> > Date: 08/06/2008
> > Time: 14:34:00
> > User: N/A
> > Computer: SERVER2003
> > Description:
> > The time provider NtpServer encountered an error while digitally
> > signing the
> > NTP response for peer 192.168.3.147:123. NtpServer cannot provide
> > secure
> > (signed) time to the client and will ignore the request. The error
> > was: Not
> > enough storage is available to process this command. (0x80070008)
> > (the peer IP varies)
> > Event Type: Warning
> > Event Source: W32Time
> > Event Category: None
> > Event ID: 36
> > Date: 08/05/2008
> > Time: 10:14:23
> > User: N/A
> > Computer: SERVER2003
> > Description:
> > The time service has not synchronized the system time for 86400
> > seconds
> > because none of the time service providers provided a usable time
> > stamp. The
> > time service is no longer synchronized and cannot provide the time to
> > other
> > clients or update the system clock. Monitor the system events
> > displayed in
> > the Event Viewer to make sure that a more serious problem does not
> > exist.
> > Event Type: Warning
> > Event Source: W32Time
> > Event Category: None
> > Event ID: 12
> > Date: 05/05/2008
> > Time: 14:02:34
> > User: N/A
> > Computer: SERVER2003
> > Description:
> > Time Provider NtpClient: This machine is configured to use the domain
> > hierarchy to determine its time source, but it is the PDC emulator for
> > the
> > domain at the root of the forest, so there is no machine above it in
> > the
> > domain hierarchy to use as a time source. It is recommended that you
> > either
> > configure a reliable time service in the root domain, or manually
> > configure
> > the PDC to synchronize with an external time source. Otherwise, this
> > machine
> > will function as the authoritative time source in the domain
> > hierarchy. If
> > an external time source is not configured or used for this computer,
> > you may
> > choose to disable the NtpClient.
>
>
>
 
Back
Top