time.windows.com

  • Thread starter Thread starter George Hester
  • Start date Start date
G

George Hester

Pinging time.windows.com [207.46.130.100] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 207.46.130.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Here is another time server

Pinging time.nist.gov [192.43.244.18] with 32 bytes of data:

Reply from 192.43.244.18: bytes=32 time=100ms TTL=45
Reply from 192.43.244.18: bytes=32 time=91ms TTL=45
Reply from 192.43.244.18: bytes=32 time=90ms TTL=45
Reply from 192.43.244.18: bytes=32 time=90ms TTL=45

Ping statistics for 192.43.244.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 100ms, Average = 92ms

Now what good is a time server that doesn't work like the one at windows.com
which is suggested at:

http://support.microsoft.com/default.aspx?scid=kb;en-us;216734

Don't you think that issues such as reflect negatively on Microsoft? That
the activation for Windows XP and Windows 2003 - the Genuine Windows product
nags we now have to deal with - the hodgepdge of Windows Security Updates
from the Update Service don't you think these things are doomed to fail when
they cannot even have a working time server? Man!!!
 
Could it be that time.windows.com has ICMP echos disabled? There used
to be a DoS attack that used ping.
 
From: "George Hester" <[email protected]>

| Pinging time.windows.com [207.46.130.100] with 32 bytes of data:
|
| Request timed out.
| Request timed out.
| Request timed out.
| Request timed out.
|
| Ping statistics for 207.46.130.100:
| Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
| Approximate round trip times in milli-seconds:
| Minimum = 0ms, Maximum = 0ms, Average = 0ms
|
| Here is another time server
|
| Pinging time.nist.gov [192.43.244.18] with 32 bytes of data:
|
| Reply from 192.43.244.18: bytes=32 time=100ms TTL=45
| Reply from 192.43.244.18: bytes=32 time=91ms TTL=45
| Reply from 192.43.244.18: bytes=32 time=90ms TTL=45
| Reply from 192.43.244.18: bytes=32 time=90ms TTL=45
|
| Ping statistics for 192.43.244.18:
| Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
| Approximate round trip times in milli-seconds:
| Minimum = 90ms, Maximum = 100ms, Average = 92ms
|
| Now what good is a time server that doesn't work like the one at windows.com
| which is suggested at:
|
| http://support.microsoft.com/default.aspx?scid=kb;en-us;216734
|
| Don't you think that issues such as reflect negatively on Microsoft? That
| the activation for Windows XP and Windows 2003 - the Genuine Windows product
| nags we now have to deal with - the hodgepdge of Windows Security Updates
| from the Update Service don't you think these things are doomed to fail when
| they cannot even have a working time server? Man!!!
|
| --
| George Hester
| _________________________________

The NIST has both Time Servers and client software.

http://tf.nist.gov/service/its.htm

{ This is my preference. }
 
Could be but then how do I know it works? EXPLICITLY? Is there some other
way to verify that it works other than lack of errors in Event Viewer that
the time server could not be reached?

--
George Hester
_________________________________
Stubby said:
Could it be that time.windows.com has ICMP echos disabled? There used
to be a DoS attack that used ping.


George said:
Pinging time.windows.com [207.46.130.100] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 207.46.130.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Here is another time server

Pinging time.nist.gov [192.43.244.18] with 32 bytes of data:

Reply from 192.43.244.18: bytes=32 time=100ms TTL=45
Reply from 192.43.244.18: bytes=32 time=91ms TTL=45
Reply from 192.43.244.18: bytes=32 time=90ms TTL=45
Reply from 192.43.244.18: bytes=32 time=90ms TTL=45

Ping statistics for 192.43.244.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 100ms, Average = 92ms

Now what good is a time server that doesn't work like the one at windows.com
which is suggested at:

http://support.microsoft.com/default.aspx?scid=kb;en-us;216734

Don't you think that issues such as reflect negatively on Microsoft? That
the activation for Windows XP and Windows 2003 - the Genuine Windows product
nags we now have to deal with - the hodgepdge of Windows Security Updates
from the Update Service don't you think these things are doomed to fail when
they cannot even have a working time server? Man!!!
Click to expand...
Click to expand...
 
On a Windows 2000 machine, try w32tm -once -v

George Hester said:
Could be but then how do I know it works? EXPLICITLY? Is there some
other
way to verify that it works other than lack of errors in Event Viewer that
the time server could not be reached?

--
George Hester
_________________________________
Stubby said:
Could it be that time.windows.com has ICMP echos disabled? There used
to be a DoS attack that used ping.


George said:
Pinging time.windows.com [207.46.130.100] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 207.46.130.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Here is another time server

Pinging time.nist.gov [192.43.244.18] with 32 bytes of data:

Reply from 192.43.244.18: bytes=32 time=100ms TTL=45
Reply from 192.43.244.18: bytes=32 time=91ms TTL=45
Reply from 192.43.244.18: bytes=32 time=90ms TTL=45
Reply from 192.43.244.18: bytes=32 time=90ms TTL=45

Ping statistics for 192.43.244.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 100ms, Average = 92ms

Now what good is a time server that doesn't work like the one at windows.com
which is suggested at:

http://support.microsoft.com/default.aspx?scid=kb;en-us;216734

Don't you think that issues such as reflect negatively on Microsoft? That
the activation for Windows XP and Windows 2003 - the Genuine Windows product
nags we now have to deal with - the hodgepdge of Windows Security Updates
from the Update Service don't you think these things are doomed to fail when
they cannot even have a working time server? Man!!!
Click to expand...
Click to expand...
Click to expand...
 
Oh bummer:

Event Type: Error
Event Source: w32time
Event Category: None
Event ID: 49
Date: 8/28/2005
Time: 3:29:20 PM
User: N/A
Computer: MyComputer
Description:
An unexpected error occured while trying to start the server. The port may
already be in use.
Data:
0000: 00 00 00 00 ....

I have a Network card that has nothing attached to it at the moment.

W32Time: BEGIN:InitAdjIncr
W32Time: Adj 100144 , Incr 100144 fAdjust 0
W32Time: END:Line 2481
W32Time: BEGIN:TsUpTheThread
W32Time: END Line 1385
W32Time: TimeMMInit()
W32Time: Kernel timer : using default maximum resolution
W32Time: MaximumTime = 100144
W32Time: CurrentTime = 100144
W32Time: Timer calibrated, looped 1 times
W32Time: BEGIN:InitTmCfg
W32Time: END:Line 802
W32Time: BEGIN:InitTmCli
W32Time: END:Line 2574
W32Time: BEGIN:InitTmData
W32Time: END:Line 2596
W32Time: AvoidTimeSyncOnWan 0
W32Time: ntpserver - time.nist.gov
W32Time: BEGIN:CMOSSynchSet
W32Time: Setting adjustment 100144 - Bool 0
W32Time: BEGIN:SetTSTimeRes
W32Time: END:Line 1273
W32Time: END:Line 842
W32Time: BEGIN:InitializeDC
W32Time: BEGIN:GetRole
W32Time: Role is 'PDC'
W32Time: END Line 672
W32Time: BEGIN:FetchParentDomainName
W32Time: NetLogonGetTimeServiceParentDomain() returned 54b with ptr 0
W32Time: END:Line 782
W32Time: END:Line 704
W32Time: Server: Binding to 2 NICs.
W32Time: bind failed: 0x80072740
W32Time: Logging event 0xC0000031. 15 min until this event is allowed again.
W32Time: 0xC0000031 reported to System Log in Event Viewer
W32Time: BEGIN:FinishCleanup
W32Time: BEGIN:TsUpTheThread
W32Time: END Line 1385
W32Time: BEGIN:UnInitializeDC
W32Time: Ptrs 0 - 0
W32Time: END:Line 727
W32Time: Time service stopped.
W32Time: END:Line 407

--
George Hester
_________________________________
neo said:
On a Windows 2000 machine, try w32tm -once -v

George Hester said:
Could be but then how do I know it works? EXPLICITLY? Is there some
other
way to verify that it works other than lack of errors in Event Viewer that
the time server could not be reached?

--
George Hester
_________________________________
Stubby said:
Could it be that time.windows.com has ICMP echos disabled? There used
to be a DoS attack that used ping.


George Hester wrote:
Pinging time.windows.com [207.46.130.100] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 207.46.130.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Here is another time server

Pinging time.nist.gov [192.43.244.18] with 32 bytes of data:

Reply from 192.43.244.18: bytes=32 time=100ms TTL=45
Reply from 192.43.244.18: bytes=32 time=91ms TTL=45
Reply from 192.43.244.18: bytes=32 time=90ms TTL=45
Reply from 192.43.244.18: bytes=32 time=90ms TTL=45

Ping statistics for 192.43.244.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 100ms, Average = 92ms

Now what good is a time server that doesn't work like the one at windows.com
which is suggested at:

http://support.microsoft.com/default.aspx?scid=kb;en-us;216734

Don't you think that issues such as reflect negatively on Microsoft? That
the activation for Windows XP and Windows 2003 - the Genuine Windows product
nags we now have to deal with - the hodgepdge of Windows Security Updates
from the Update Service don't you think these things are doomed to
Click to expand...
fail
when
they cannot even have a working time server? Man!!!
Click to expand...
Click to expand...
Click to expand...
 
Try this instead from a command prompt.

net stop w32time
w32tm -v -once
net start w32time

The above will stop the Windows Time Service, try a manual sync, and then
restart the service. If you still get a port in use after this point, then
it is trying to figure out what else is installed that is grabbing the ntp
port (123).

I just noticed the other statement, does "I have a Network card that has
nothing attached to it at the moment" mean that you have a NIC that doesn't
have a network connection or something else? (If no network connection,
what happens if you disable the interface in network connections?)

George Hester said:
Oh bummer:

Event Type: Error
Event Source: w32time
Event Category: None
Event ID: 49
Date: 8/28/2005
Time: 3:29:20 PM
User: N/A
Computer: MyComputer
Description:
An unexpected error occured while trying to start the server. The port may
already be in use.
Data:
0000: 00 00 00 00 ....

I have a Network card that has nothing attached to it at the moment.

W32Time: BEGIN:InitAdjIncr
W32Time: Adj 100144 , Incr 100144 fAdjust 0
W32Time: END:Line 2481
W32Time: BEGIN:TsUpTheThread
W32Time: END Line 1385
W32Time: TimeMMInit()
W32Time: Kernel timer : using default maximum resolution
W32Time: MaximumTime = 100144
W32Time: CurrentTime = 100144
W32Time: Timer calibrated, looped 1 times
W32Time: BEGIN:InitTmCfg
W32Time: END:Line 802
W32Time: BEGIN:InitTmCli
W32Time: END:Line 2574
W32Time: BEGIN:InitTmData
W32Time: END:Line 2596
W32Time: AvoidTimeSyncOnWan 0
W32Time: ntpserver - time.nist.gov
W32Time: BEGIN:CMOSSynchSet
W32Time: Setting adjustment 100144 - Bool 0
W32Time: BEGIN:SetTSTimeRes
W32Time: END:Line 1273
W32Time: END:Line 842
W32Time: BEGIN:InitializeDC
W32Time: BEGIN:GetRole
W32Time: Role is 'PDC'
W32Time: END Line 672
W32Time: BEGIN:FetchParentDomainName
W32Time: NetLogonGetTimeServiceParentDomain() returned 54b with ptr
0
W32Time: END:Line 782
W32Time: END:Line 704
W32Time: Server: Binding to 2 NICs.
W32Time: bind failed: 0x80072740
W32Time: Logging event 0xC0000031. 15 min until this event is allowed
again.
W32Time: 0xC0000031 reported to System Log in Event Viewer
W32Time: BEGIN:FinishCleanup
W32Time: BEGIN:TsUpTheThread
W32Time: END Line 1385
W32Time: BEGIN:UnInitializeDC
W32Time: Ptrs 0 - 0
W32Time: END:Line 727
W32Time: Time service stopped.
W32Time: END:Line 407

--
George Hester
_________________________________
neo said:
On a Windows 2000 machine, try w32tm -once -v

George Hester said:
Could be but then how do I know it works? EXPLICITLY? Is there some
other
way to verify that it works other than lack of errors in Event Viewer that
the time server could not be reached?

--
George Hester
_________________________________
Could it be that time.windows.com has ICMP echos disabled? There used
to be a DoS attack that used ping.


George Hester wrote:
Pinging time.windows.com [207.46.130.100] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 207.46.130.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Here is another time server

Pinging time.nist.gov [192.43.244.18] with 32 bytes of data:

Reply from 192.43.244.18: bytes=32 time=100ms TTL=45
Reply from 192.43.244.18: bytes=32 time=91ms TTL=45
Reply from 192.43.244.18: bytes=32 time=90ms TTL=45
Reply from 192.43.244.18: bytes=32 time=90ms TTL=45

Ping statistics for 192.43.244.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 100ms, Average = 92ms

Now what good is a time server that doesn't work like the one at
windows.com
which is suggested at:

http://support.microsoft.com/default.aspx?scid=kb;en-us;216734

Don't you think that issues such as reflect negatively on Microsoft?
That
the activation for Windows XP and Windows 2003 - the Genuine Windows
product
nags we now have to deal with - the hodgepdge of Windows Security
Updates
from the Update Service don't you think these things are doomed to fail
when
they cannot even have a working time server? Man!!!
Click to expand...
Click to expand...
Click to expand...
 
Yes a Network card with no connection to anything. It's just sitting there
and yes it is enabled. I'll disable it and try agin your first suggestion.
That didn't help. I did your second suggetion with the other Nic disabled:

W32Time: BEGIN:InitAdjIncr
W32Time: Adj 100144 , Incr 100144 fAdjust 0
W32Time: END:Line 2481
W32Time: BEGIN:TsUpTheThread
W32Time: END Line 1385
W32Time: TimeMMInit()
W32Time: Kernel timer : using default maximum resolution
W32Time: MaximumTime = 100144
W32Time: CurrentTime = 100144
W32Time: Timer calibrated, looped 1 times
W32Time: BEGIN:InitTmCfg
W32Time: END:Line 802
W32Time: BEGIN:InitTmCli
W32Time: END:Line 2574
W32Time: BEGIN:InitTmData
W32Time: END:Line 2596
W32Time: AvoidTimeSyncOnWan 0
W32Time: ntpserver - time.nist.gov
W32Time: BEGIN:CMOSSynchSet
W32Time: Setting adjustment 100144 - Bool 0
W32Time: BEGIN:SetTSTimeRes
W32Time: END:Line 1273
W32Time: END:Line 842
W32Time: BEGIN:InitializeDC
W32Time: BEGIN:GetRole
W32Time: Role is 'PDC'
W32Time: END Line 672
W32Time: BEGIN:FetchParentDomainName
W32Time: NetLogonGetTimeServiceParentDomain() returned 54b with ptr 0
W32Time: END:Line 782
W32Time: END:Line 704
W32Time: Server: Binding to 1 NIC.
W32Time: Advertising that I'm a Time Service Provider
W32Time: timeBeginPeriod: setting resolution 9
W32Time: BEGIN:TimeSync
W32Time: BEGIN:FGetType
W32Time: END Line 253
W32Time: BEGIN:FDoTimeNTPType
W32Time: BEGIN:ChooseNTPServer
W32Time: END Line 2156
W32Time: BEGIN:GetSocketForSynch
W32Time: NTP: ntpptrs[0] - TIME.NIST.GOV
W32Time: rgbNTPServer TIME.NIST.GOV
W32Time: Port Pinging to - 123
W32Time: Connecting to "TIME.NIST.GOV" (192.43.244.18)
W32Time: END:Line 1148
W32Time: BEGIN:GetDefaultRid
W32Time: END Line 2337
W32Time: BEGIN:ComputeDelay
W32Time: BEGIN:NTPTry -- init
W32Time: END Line 1661
W32Time: BEGIN:NTPTry -- try
W32Time: BEGIN:ComputeInterval
W32Time: END Line 2457
W32Time: Sending to server 48 bytes...
W32Time: BEGIN:TsUpTheThread
W32Time: END Line 1385
W32Time: NTP(S): waiting for datagram...
W32Time: Recv'ed from server 48 Bytes...
W32Time: END Line 1863
W32Time: BEGIN:NTPTry -- delay
W32Time: END Line 1990
W32Time: Round trip was 90ms
W32Time: BEGIN:NTPTry -- try
W32Time: BEGIN:ComputeInterval
W32Time: END Line 2457
W32Time: Sending to server 48 bytes...
W32Time: Recv'ed from server 48 Bytes...
W32Time: END Line 1863
W32Time: BEGIN:NTPTry -- delay
W32Time: END Line 1990
W32Time: Round trip was 100ms
W32Time: BEGIN:NTPTry -- try
W32Time: BEGIN:ComputeInterval
W32Time: END Line 2457
W32Time: Sending to server 48 bytes...
W32Time: Recv'ed from server 48 Bytes...
W32Time: END Line 1863
W32Time: BEGIN:NTPTry -- delay
W32Time: END Line 1990
W32Time: Round trip was 110ms
W32Time: BEGIN:NTPTry -- gettime
W32Time: BEGIN:Fgmtimetonttime
W32Time: END Line 2541
W32Time: END Line 1976
W32Time: one-way delay is 55ms
W32Time: END Line 1623
W32Time: END Line 367
W32Time: BEGIN:TimeDiff
W32Time: ClockError -5759
W32Time: END Line 2520
W32Time: BEGIN:FCheckTimeSanity
W32Time: END Line 548
W32Time: BEGIN:SetTimeNow
W32Time: Skewing for backwards, badj, btime = 50072 11518
W32Time: END Line 1258
W32Time: Time was 29min 49.059s
W32Time: Time is 29min 43.300s
W32Time: Error 5759ms
W32Time: BEGIN:CheckLeapFlag
W32Time: END:Line 584
W32Time: BEGIN:ComputePostTimeData
W32Time: BEGIN:ComputeInterval
W32Time: END Line 2457
W32Time: BEGIN:ComputeSleepStuff
W32Time: Computed stagger is 0ms, bias is 0ms
W32Time: Time until next sync - 2699.960s
W32Time: END:Line 794
W32Time: END:Line 220
W32Time: END:Line 195
W32Time: BEGIN:TermTime
W32Time: NTP(S): received shutdown notification.
W32Time: TimeMMCleanup()
W32Time: BEGIN:FinishCleanup
W32Time: BEGIN:TsUpTheThread
W32Time: END Line 1385
W32Time: Inform NetLogon That you are not a TS Provider
W32Time: BEGIN:UnInitializeDC
W32Time: Ptrs 0 - 0
W32Time: END:Line 727
W32Time: Time service stopped.
W32Time: END:Line 407

OK that's better right? Now I will do it for the time.windows.com Time
Server:

W32Time: BEGIN:InitAdjIncr
W32Time: Adj 100144 , Incr 100144 fAdjust 0
W32Time: END:Line 2481
W32Time: BEGIN:TsUpTheThread
W32Time: END Line 1385
W32Time: TimeMMInit()
W32Time: Kernel timer : using default maximum resolution
W32Time: MaximumTime = 100144
W32Time: CurrentTime = 100144
W32Time: Timer calibrated, looped 1 times
W32Time: BEGIN:InitTmCfg
W32Time: END:Line 802
W32Time: BEGIN:InitTmCli
W32Time: END:Line 2574
W32Time: BEGIN:InitTmData
W32Time: END:Line 2596
W32Time: AvoidTimeSyncOnWan 0
W32Time: ntpserver - time.windows.com
W32Time: BEGIN:CMOSSynchSet
W32Time: Setting adjustment 100144 - Bool 0
W32Time: BEGIN:SetTSTimeRes
W32Time: END:Line 1273
W32Time: END:Line 842
W32Time: BEGIN:InitializeDC
W32Time: BEGIN:GetRole
W32Time: Role is 'PDC'
W32Time: END Line 672
W32Time: BEGIN:FetchParentDomainName
W32Time: NetLogonGetTimeServiceParentDomain() returned 54b with ptr 0
W32Time: END:Line 782
W32Time: END:Line 704
W32Time: Server: Binding to 1 NIC.
W32Time: Advertising that I'm a Time Service Provider
W32Time: timeBeginPeriod: setting resolution 9
W32Time: BEGIN:TimeSync
W32Time: BEGIN:FGetType
W32Time: END Line 253
W32Time: BEGIN:FDoTimeNTPType
W32Time: BEGIN:ChooseNTPServer
W32Time: END Line 2156
W32Time: BEGIN:GetSocketForSynch
W32Time: NTP: ntpptrs[0] - TIME.WINDOWS.COM
W32Time: rgbNTPServer TIME.WINDOWS.COM
W32Time: BEGIN:TsUpTheThread
W32Time: END Line 1385
W32Time: NTP(S): waiting for datagram...
W32Time: Port Pinging to - 123
W32Time: Connecting to "TIME.WINDOWS.COM" (207.46.130.100)
W32Time: END:Line 1148
W32Time: BEGIN:GetDefaultRid
W32Time: END Line 2337
W32Time: BEGIN:ComputeDelay
W32Time: BEGIN:NTPTry -- init
W32Time: END Line 1661
W32Time: BEGIN:NTPTry -- try
W32Time: BEGIN:ComputeInterval
W32Time: END Line 2457
W32Time: Sending to server 48 bytes...
W32Time: Recv'ed from server 48 Bytes...
W32Time: END Line 1863
W32Time: BEGIN:NTPTry -- delay
W32Time: END Line 1990
W32Time: Round trip was 200ms
W32Time: BEGIN:NTPTry -- try
W32Time: BEGIN:ComputeInterval
W32Time: END Line 2457
W32Time: Sending to server 48 bytes...
W32Time: Recv'ed from server 48 Bytes...
W32Time: END Line 1863
W32Time: BEGIN:NTPTry -- delay
W32Time: END Line 1990
W32Time: Round trip was 110ms
W32Time: BEGIN:NTPTry -- try
W32Time: BEGIN:ComputeInterval
W32Time: END Line 2457
W32Time: Sending to server 48 bytes...
W32Time: Recv'ed from server 48 Bytes...
W32Time: END Line 1863
W32Time: BEGIN:NTPTry -- delay
W32Time: END Line 1990
W32Time: Round trip was 101ms
W32Time: BEGIN:NTPTry -- gettime
W32Time: BEGIN:Fgmtimetonttime
W32Time: END Line 2541
W32Time: END Line 1976
W32Time: one-way delay is 50ms
W32Time: END Line 1623
W32Time: END Line 367
W32Time: BEGIN:TimeDiff
W32Time: ClockError --21
W32Time: END Line 2520
W32Time: BEGIN:FCheckTimeSanity
W32Time: END Line 548
W32Time: BEGIN:SetTimeNow
W32Time: Time 8/28/2005 23:33:47:167
W32Time: *****SetSystemTime()*****
W32Time: END Line 1258
W32Time: Time was 33min 47.146s
W32Time: Time is 33min 47.167s
W32Time: Error -21ms
W32Time: BEGIN:CheckLeapFlag
W32Time: END:Line 584
W32Time: BEGIN:ComputePostTimeData
W32Time: BEGIN:ComputeInterval
W32Time: END Line 2457
W32Time: BEGIN:ComputeSleepStuff
W32Time: Computed stagger is 0ms, bias is 0ms
W32Time: Time until next sync - 2699.960s
W32Time: END:Line 794
W32Time: END:Line 220
W32Time: END:Line 195
W32Time: BEGIN:TermTime
W32Time: NTP(S): received shutdown notification.
W32Time: TimeMMCleanup()
W32Time: BEGIN:FinishCleanup
W32Time: BEGIN:TsUpTheThread
W32Time: END Line 1385
W32Time: Inform NetLogon That you are not a TS Provider
W32Time: BEGIN:UnInitializeDC
W32Time: Ptrs 0 - 0
W32Time: END:Line 727
W32Time: Time service stopped.
W32Time: END:Line 407

Looks OK huh? The time.windows.com IS working?

--
George Hester
_________________________________
neo said:
Try this instead from a command prompt.

net stop w32time
w32tm -v -once
net start w32time

The above will stop the Windows Time Service, try a manual sync, and then
restart the service. If you still get a port in use after this point, then
it is trying to figure out what else is installed that is grabbing the ntp
port (123).

I just noticed the other statement, does "I have a Network card that has
nothing attached to it at the moment" mean that you have a NIC that doesn't
have a network connection or something else? (If no network connection,
what happens if you disable the interface in network connections?)

George Hester said:
Oh bummer:

Event Type: Error
Event Source: w32time
Event Category: None
Event ID: 49
Date: 8/28/2005
Time: 3:29:20 PM
User: N/A
Computer: MyComputer
Description:
An unexpected error occured while trying to start the server. The port may
already be in use.
Data:
0000: 00 00 00 00 ....

I have a Network card that has nothing attached to it at the moment.

W32Time: BEGIN:InitAdjIncr
W32Time: Adj 100144 , Incr 100144 fAdjust 0
W32Time: END:Line 2481
W32Time: BEGIN:TsUpTheThread
W32Time: END Line 1385
W32Time: TimeMMInit()
W32Time: Kernel timer : using default maximum resolution
W32Time: MaximumTime = 100144
W32Time: CurrentTime = 100144
W32Time: Timer calibrated, looped 1 times
W32Time: BEGIN:InitTmCfg
W32Time: END:Line 802
W32Time: BEGIN:InitTmCli
W32Time: END:Line 2574
W32Time: BEGIN:InitTmData
W32Time: END:Line 2596
W32Time: AvoidTimeSyncOnWan 0
W32Time: ntpserver - time.nist.gov
W32Time: BEGIN:CMOSSynchSet
W32Time: Setting adjustment 100144 - Bool 0
W32Time: BEGIN:SetTSTimeRes
W32Time: END:Line 1273
W32Time: END:Line 842
W32Time: BEGIN:InitializeDC
W32Time: BEGIN:GetRole
W32Time: Role is 'PDC'
W32Time: END Line 672
W32Time: BEGIN:FetchParentDomainName
W32Time: NetLogonGetTimeServiceParentDomain() returned 54b with ptr
0
W32Time: END:Line 782
W32Time: END:Line 704
W32Time: Server: Binding to 2 NICs.
W32Time: bind failed: 0x80072740
W32Time: Logging event 0xC0000031. 15 min until this event is allowed
again.
W32Time: 0xC0000031 reported to System Log in Event Viewer
W32Time: BEGIN:FinishCleanup
W32Time: BEGIN:TsUpTheThread
W32Time: END Line 1385
W32Time: BEGIN:UnInitializeDC
W32Time: Ptrs 0 - 0
W32Time: END:Line 727
W32Time: Time service stopped.
W32Time: END:Line 407

--
George Hester
_________________________________
neo said:
On a Windows 2000 machine, try w32tm -once -v

Could be but then how do I know it works? EXPLICITLY? Is there some
other
way to verify that it works other than lack of errors in Event Viewer that
the time server could not be reached?

--
George Hester
_________________________________
Could it be that time.windows.com has ICMP echos disabled? There used
to be a DoS attack that used ping.


George Hester wrote:
Pinging time.windows.com [207.46.130.100] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 207.46.130.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Here is another time server

Pinging time.nist.gov [192.43.244.18] with 32 bytes of data:

Reply from 192.43.244.18: bytes=32 time=100ms TTL=45
Reply from 192.43.244.18: bytes=32 time=91ms TTL=45
Reply from 192.43.244.18: bytes=32 time=90ms TTL=45
Reply from 192.43.244.18: bytes=32 time=90ms TTL=45

Ping statistics for 192.43.244.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 100ms, Average = 92ms

Now what good is a time server that doesn't work like the one at
windows.com
which is suggested at:

http://support.microsoft.com/default.aspx?scid=kb;en-us;216734

Don't you think that issues such as reflect negatively on Microsoft?
That
the activation for Windows XP and Windows 2003 - the Genuine Windows
product
nags we now have to deal with - the hodgepdge of Windows Security
Updates
from the Update Service don't you think these things are doomed to fail
when
they cannot even have a working time server? Man!!!
Click to expand...
Click to expand...
Click to expand...
 
Yes, both are working. :)

George Hester said:
Yes a Network card with no connection to anything. It's just sitting
there
and yes it is enabled. I'll disable it and try agin your first
suggestion.
That didn't help. I did your second suggetion with the other Nic
disabled:
Click to expand...
OK that's better right? Now I will do it for the time.windows.com Time
Server:
Click to expand...
Looks OK huh? The time.windows.com IS working?

--
George Hester
_________________________________
neo said:
Try this instead from a command prompt.

net stop w32time
w32tm -v -once
net start w32time

The above will stop the Windows Time Service, try a manual sync, and then
restart the service. If you still get a port in use after this point, then
it is trying to figure out what else is installed that is grabbing the
ntp
port (123).

I just noticed the other statement, does "I have a Network card that has
nothing attached to it at the moment" mean that you have a NIC that doesn't
have a network connection or something else? (If no network connection,
what happens if you disable the interface in network connections?)

George Hester said:
Oh bummer:

Event Type: Error
Event Source: w32time
Event Category: None
Event ID: 49
Date: 8/28/2005
Time: 3:29:20 PM
User: N/A
Computer: MyComputer
Description:
An unexpected error occured while trying to start the server. The port may
already be in use.
Data:
0000: 00 00 00 00 ....

I have a Network card that has nothing attached to it at the moment.

W32Time: BEGIN:InitAdjIncr
W32Time: Adj 100144 , Incr 100144 fAdjust 0
W32Time: END:Line 2481
W32Time: BEGIN:TsUpTheThread
W32Time: END Line 1385
W32Time: TimeMMInit()
W32Time: Kernel timer : using default maximum resolution
W32Time: MaximumTime = 100144
W32Time: CurrentTime = 100144
W32Time: Timer calibrated, looped 1 times
W32Time: BEGIN:InitTmCfg
W32Time: END:Line 802
W32Time: BEGIN:InitTmCli
W32Time: END:Line 2574
W32Time: BEGIN:InitTmData
W32Time: END:Line 2596
W32Time: AvoidTimeSyncOnWan 0
W32Time: ntpserver - time.nist.gov
W32Time: BEGIN:CMOSSynchSet
W32Time: Setting adjustment 100144 - Bool 0
W32Time: BEGIN:SetTSTimeRes
W32Time: END:Line 1273
W32Time: END:Line 842
W32Time: BEGIN:InitializeDC
W32Time: BEGIN:GetRole
W32Time: Role is 'PDC'
W32Time: END Line 672
W32Time: BEGIN:FetchParentDomainName
W32Time: NetLogonGetTimeServiceParentDomain() returned 54b with ptr
0
W32Time: END:Line 782
W32Time: END:Line 704
W32Time: Server: Binding to 2 NICs.
W32Time: bind failed: 0x80072740
W32Time: Logging event 0xC0000031. 15 min until this event is allowed
again.
W32Time: 0xC0000031 reported to System Log in Event Viewer
W32Time: BEGIN:FinishCleanup
W32Time: BEGIN:TsUpTheThread
W32Time: END Line 1385
W32Time: BEGIN:UnInitializeDC
W32Time: Ptrs 0 - 0
W32Time: END:Line 727
W32Time: Time service stopped.
W32Time: END:Line 407

--
George Hester
_________________________________
On a Windows 2000 machine, try w32tm -once -v

Could be but then how do I know it works? EXPLICITLY? Is there
some
other
way to verify that it works other than lack of errors in Event
Viewer
that
the time server could not be reached?

--
George Hester
_________________________________
Could it be that time.windows.com has ICMP echos disabled? There used
to be a DoS attack that used ping.


George Hester wrote:
Pinging time.windows.com [207.46.130.100] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 207.46.130.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Here is another time server

Pinging time.nist.gov [192.43.244.18] with 32 bytes of data:

Reply from 192.43.244.18: bytes=32 time=100ms TTL=45
Reply from 192.43.244.18: bytes=32 time=91ms TTL=45
Reply from 192.43.244.18: bytes=32 time=90ms TTL=45
Reply from 192.43.244.18: bytes=32 time=90ms TTL=45

Ping statistics for 192.43.244.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 100ms, Average = 92ms

Now what good is a time server that doesn't work like the one at
windows.com
which is suggested at:

http://support.microsoft.com/default.aspx?scid=kb;en-us;216734

Don't you think that issues such as reflect negatively on Microsoft?
That
the activation for Windows XP and Windows 2003 - the Genuine Windows
product
nags we now have to deal with - the hodgepdge of Windows Security
Updates
from the Update Service don't you think these things are doomed
to
fail
when
they cannot even have a working time server? Man!!!
Click to expand...
Click to expand...
Click to expand...
 
OK neo now for the $60000000 question. How to do the same think in Windows
XP? Verify the Time Server Source. XP doesn't have w32tm.
 
It does, but its command line has changed. Umm... never tried this against
a NTP server only a domain controller, but take a peek at the w32tm
/stripchart /computer:<target> /samples:<how many times>. (To see all
options for w32tm under Windows XP/2003, type w32tm /? at a command prompt.)
 
You know something neo. I left the ntp server to time.windows.com after we
last spoke. I figured if it was working just leave it be. I had not
rebooted till just a moment ago. Turns out:

Event Type: Warning
Event Source: w32time
Event Category: None
Event ID: 11
Date: 9/4/2005
Time: 11:15:32 AM
User: N/A
Computer: MyComputer
Description:
The NTP server didn't respond
Data:
0000: 49 27 00 00 I'..

I'm going back to time.nist.gov since that pings and reboot. Will let you
know if this Warning comes up again or not. I still have to look at the
Windows XP yet but I have to do some work on that machine.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

urgetly need help 2
XP - Ping one way but not other? 0
XP - Ping one way but not other? 8
File and print sharing problems 6
Problem with Dns 0
Network only working one way? 4
Can't get home network working? 1
Cannot connect XP Pro SP2 to Windows ME 2

Back
Top