Re: w32tm
- From: "Greg Foulks" <greg.foulks@xxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Wed, 15 Aug 2001 09:55:53 -0400
Jim,
I can do it from the ISA server. I can't get it to connect via the DC. It is
set as a secureNAT and I do have the packet filter set as you described.
Very strange!
Greg Foulks, MCP
NewFound Technologies, Inc.
http://www.nfti.com
Email: greg.foulks@xxxxxxxx
Voice: 614.318.5036
Fax: 614.318.5005
-----Original Message-----
From: Jim Harrison [mailto:jim@xxxxxxxxxxxx]
Sent: Wednesday, August 15, 2001 9:37 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] Re: w32tm
http://www.ISAserver.org
<rant>
I hate messages like that: "5 NICs", meaning "IPs". It really throws you
off..
</rant>
Is the AD a secureNAT client?
Did you give the ISA a minute to start using the new rule?
Are there any router ACLs that might be blocking you?
If you create a packet filter as:
UDP send-receive
remote 123
local all
and use the "w32tm -v -once" from the ISA, what is the result?
Jim Harrison
MCP(2K), A+, Network+, PCG
----- Original Message -----
From: "Greg Foulks" <greg.foulks@xxxxxxxx>
To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
Sent: Wednesday, August 15, 2001 5:12 AM
Subject: [isalist] Re: w32tm
http://www.ISAserver.org
Sure it's a Dell PowerEdge 2400
Runs DC, AD, IMail, SQL Server, IAS, Intranet Website, Support
Website, Email Virus Scanning.
1 gig of Ram
667 CPU
2 8 gig drives
5 Internal IP's bound to a single NIC (It has two other NICs
installed but are disabled until needed)
That's the short story.
Greg
---------- Original Message ----------------------------------
From: "Jim Harrison" <jim@xxxxxxxxxxxx>
Reply-To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
Date: Tue, 14 Aug 2001 23:14:29 -0700
>http://www.ISAserver.org
>
>
>"W32Time: Server: Binding to 5 NICs."
>
>You have 5 NICs installed in your AD?
>
>This is not an ideal scenario, to say the least. Your routing
table must be
>really interesting. Can you provide some details of this machine
and the
>network?
>
>----- Original Message -----
>From: "Greg Foulks" <greg.foulks@xxxxxxxx>
>To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
>Sent: Tuesday, August 14, 2001 1:46 PM
>Subject: [isalist] Re: w32tm
>
>
>> http://www.ISAserver.org
>>
>>
>> When I try the w32tm -v -once I get the following output. Does
this look
>> right?
>>
>> W32Time: BEGIN:InitAdjIncr
>> W32Time: Adj 156254 , Incr 156250 fAdjust 0
>> W32Time: 156254 Adj!=Incr 156250
>> W32Time: END:Line 2473
>> W32Time: BEGIN:TsUpTheThread
>> W32Time: END Line 1384
>> W32Time: TimeMMInit()
>> W32Time: Kernel timer : using default maximum resolution
>> W32Time: MaximumTime = 156250
>> W32Time: CurrentTime = 156250
>> W32Time: Timer calibrated, looped 1 times
>> W32Time: BEGIN:InitTmCfg
>> W32Time: END:Line 752
>> W32Time: BEGIN:InitTmCli
>> W32Time: END:Line 2566
>> W32Time: BEGIN:InitTmData
>> W32Time: END:Line 2588
>> W32Time: AvoidTimeSyncOnWan 0
>> W32Time: Using sticky Adj 156254
>> W32Time: ntpserver - tock.usno.navy.mil
>> W32Time: BEGIN:CMOSSynchSet
>> W32Time: Setting adjustment 156254 - Bool 0
>> W32Time: BEGIN:SetTSTimeRes
>> W32Time: END:Line 1272
>> W32Time: END:Line 841
>> W32Time: BEGIN:InitializeDC
>> W32Time: BEGIN:GetRole
>> W32Time: Role is 'PDC'
>> W32Time: END Line 670
>> W32Time: BEGIN:FetchParentDomainName
>> W32Time: NetLogonGetTimeServiceParentDomain() returned
54b with ptr
>0
>> W32Time: END:Line 780
>> W32Time: END:Line 702
>> W32Time: Server: Binding to 5 NICs.
>> W32Time: Advertising that I'm a Time Service Provider
>> W32Time: timeBeginPeriod: setting resolution 9
>> W32Time: BEGIN:TimeSync
>> W32Time: BEGIN:FGetType
>> W32Time: END Line 252
>> W32Time: BEGIN:FDoTimeNTPType
>> W32Time: BEGIN:ChooseNTPServer
>> W32Time: END Line 2150
>> W32Time: BEGIN:GetSocketForSynch
>> W32Time: NTP: ntpptrs[0] - TOCK.USNO.NAVY.MIL
>> W32Time: rgbNTPServer TOCK.USNO.NAVY.MIL
>> W32Time: Port Pinging to - 123
>> W32Time: Connecting to "TOCK.USNO.NAVY.MIL"
(192.5.41.41)
>> W32Time: END:Line 1147
>> W32Time: BEGIN:GetDefaultRid
>> W32Time: END Line 2329
>> W32Time: BEGIN:ComputeDelay
>> W32Time: BEGIN:NTPTry -- init
>> W32Time: END Line 1660
>> W32Time: BEGIN:NTPTry -- try
>> W32Time: BEGIN:ComputeInterval
>> W32Time: END Line 2449
>> W32Time: Sending to server 48 bytes...
>> W32Time: BEGIN:TsUpTheThread
>> W32Time: END Line 1384
>> W32Time: NTP(S): waiting for datagram...
>> W32Time: BEGIN:TsUpTheThread
>> W32Time: END Line 1384
>> W32Time: NTP(S): waiting for datagram...
>> W32Time: BEGIN:TsUpTheThread
>> W32Time: END Line 1384
>> W32Time: NTP(S): waiting for datagram...
>> W32Time: BEGIN:TsUpTheThread
>> W32Time: END Line 1384
>> W32Time: NTP(S): waiting for datagram...
>> W32Time: BEGIN:TsUpTheThread
>> W32Time: END Line 1384
>> W32Time: NTP(S): waiting for datagram...
>> W32Time: NTP: didn't receive datagram
>> W32Time: END Line 1923
>> W32Time: Time source failed to produce usable
timestamp.
>> W32Time: BEGIN:NTPTry -- fail
>> W32Time: END Line 1660
>> W32Time: Time Out occured in sockets
>> W32Time: BEGIN:NTPTry -- try
>> W32Time: BEGIN:ComputeInterval
>> W32Time: END Line 2449
>> W32Time: Sending to server 48 bytes...
>> W32Time: NTP: didn't receive datagram
>> W32Time: END Line 1923
>> W32Time: Time source failed to produce usable
timestamp.
>> W32Time: BEGIN:NTPTry -- fail
>> W32Time: END Line 1660
>> W32Time: Time Out occured in sockets
>> W32Time: BEGIN:NTPTry -- try
>> W32Time: BEGIN:ComputeInterval
>> W32Time: END Line 2449
>> W32Time: Sending to server 48 bytes...
>> W32Time: NTP: didn't receive datagram
>> W32Time: END Line 1921
>> W32Time: Time source failed to produce usable
timestamp.
>> W32Time: BEGIN:NTPTry -- fail
>> W32Time: END Line 1660
>> W32Time: END Line 1473
>> W32Time: END Line 366
>> W32Time: BEGIN:ComputePostTimeData
>> W32Time: BEGIN:ComputeInterval
>> W32Time: END Line 2449
>> W32Time: BEGIN:ComputeSleepStuff
>> W32Time: Computed stagger is 0ms, bias is 0ms
>> W32Time: Time until next sync - 2699.960s
>> W32Time: END:Line 793
>> W32Time: END:Line 219
>> W32Time: END:Line 194
>> W32Time: BEGIN:TermTime
>> W32Time: NTP(S): received shutdown notification.
>> W32Time: NTP(S): received shutdown notification.
>> W32Time: NTP(S): received shutdown notification.
>> W32Time: NTP(S): received shutdown notification.
>> W32Time: NTP(S): received shutdown notification.
>> W32Time: TimeMMCleanup()
>> W32Time: BEGIN:FinishCleanup
>> W32Time: BEGIN:TsUpTheThread
>> W32Time: END Line 1384
>> W32Time: Inform NetLogon That you are not a TS Provider
>> W32Time: BEGIN:UnInitializeDC
>> W32Time: Ptrs 0 - 0
>> W32Time: END:Line 725
>> W32Time: Time service stopped.
>> W32Time: END:Line 383
>>
>> Greg Foulks, MCP
>> NewFound Technologies, Inc.
>> http://www.nfti.com
>> Email: greg.foulks@xxxxxxxx
>> Voice: 614.318.5036
>> Fax: 614.318.5005
>>
>>
>> -----Original Message-----
>> From: Jim Harrison [mailto:jim@xxxxxxxxxxxx]
>> Sent: Tuesday, August 14, 2001 4:34 PM
>> To: [ISAserver.org Discussion List]
>> Subject: [isalist] Re: w32tm
>>
>>
>> http://www.ISAserver.org
>>
>>
>> 1. Make sure your AD is a secureNAT client
>> 2. Create a protocol rule allowing NTP (UDP)
>> 3. At the AD, open command window and type:
>> "net time /setsntp:<time_server>"
>> "net stop w32time"
>> "w32tm -v -once"
>> (this should be successful. If not, recheck 1. and 2.)
>> "net start w32time"
>> 4. Enjoy your new time sync.
>>
>> Jim Harrison
>> MCP(2K), A+, Network+, PCG
>>
>> ----- Original Message -----
>> From: "Adam Embrey" <aembrey@xxxxxxxxxxx>
>> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
>> Sent: Tuesday, August 14, 2001 12:45 PM
>> Subject: [isalist] w32tm
>>
>>
>> http://www.ISAserver.org
>>
>>
>> Hi
>>
>> Has anyone had any troubles with windows time service? I cannot
get my
>> w2k domain controller or another machine to synchronize time
with an
>> external time source. This has got my authentication all out of
wack.
>>
>> Thanks for any help.
>>
>> Adam Embrey
>>
>> ------------------------------------------------------
>> You are currently subscribed to this ISAserver.org Discussion
List as:
>> jim@xxxxxxxxxxxx
>> To unsubscribe send a blank email to leave-isalist-
260948B@xxxxxxxxxxxxx
>>
>>
>>
>> ------------------------------------------------------
>> You are currently subscribed to this ISAserver.org Discussion
List as:
>> greg.foulks@xxxxxxxx
>> To unsubscribe send a blank email to leave-isalist-
260948B@xxxxxxxxxxxxx
>>
>>
>> ------------------------------------------------------
>> You are currently subscribed to this ISAserver.org Discussion
List as:
>jim@xxxxxxxxxxxx
>> To unsubscribe send a blank email to leave-isalist-
260948B@xxxxxxxxxxxxx
>>
>
>
>------------------------------------------------------
>You are currently subscribed to this ISAserver.org Discussion
List as: greg.foulks@xxxxxxxx
>To unsubscribe send a blank email to leave-isalist-
260948B@xxxxxxxxxxxxx
>
________________________________________________________________
Sent via the NewFound Technologies, Inc. - WebMail system at
mail.nfti.com
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
jim@xxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
greg.foulks@xxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
Other related posts:
