DC Time Server Problem after DC hardware migration

[Terry]

This problem exists on a Win2k SP4 server

I recently moved my (only) PDC to a new hardware platform. Most of this
process went smoothly. I got hung up for a bit on the new hardware
taking over from the old because of Replication problems (which I was
able to resolve).
Once the replication problem was resolved, I was then able to complete
the transition and demote the old PDC to a member server.

I have only one problem that I can see with the new hardware.

When I run DCDiag, I get errors in the output regarding the new
hardware advertising as a time server. The text below shows the ONLY
errors I receive from DCDiag (even running a full, verbose test)

Starting test: Advertising
Warning: BINGPDC is not advertising as a time server.
......................... BINGPDC failed test Advertising


....
Starting test: FsmoCheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error
1355
A Good Time Server could not be located.
......................... bingdom.com failed test FsmoCheck

I've read KB articles about the W32Time service, configured the
registry, bounced the time service, rebooted the PDC, made sure the
service is running, etc., etc.

I've even seen in my event logs from the PDC that the time service IS
synchronizing to the external source:
Source: w32time
Event ID: 0
Description: The Time service synced time from time source
(POOL.NTP.ORG) .

If I do a 'net time' command on my client PC's (WinXP SP2), they
timeout with the error message:

Could not locate a time-server.

At this point, I can't think of anything else to check or to do.

This PDC hosts my DNS, DHCP, AD (everything for the domain--it's a very
small home domain)

Please help!
Thanks

 

[Paul Bergson]

Have you followed this KB to configure your DC? If not follow through on
this and see if it doesn't resolve it for you.

http://support.microsoft.com/kb/216734/

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
http://www.pbbergs.com/

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Terry]

Thanks for the reply.

Yes, I have followed the article you mentioned very, very closely. It
has not helped. My time service on the DC itself works. It just
stubbornly refuses to advertise itself as a time server and I haven't
been able to find anything that will get that working.

 

[JMS]

Hello Terry did you transfer the PDC role before demoting the old Domain
Controller?

check: http://support.microsoft.com/?kbid=223787

 

[Terry]

I did transfer all the FSMO roles successfully (via the MMC console
snap-ins) before demoting the old PDC. I only hit one snag during this
process (as mentioned). I couldn't get replication to happen for a
while. The problem ended up that I didn't have enough free disk space
on the old PDC. Once I freed up some drive space, my replication worked
and I was able to demote the old PDC (as all roles had already been
transfered).

Honestly, I don't know where to turn on this.

Just to be thorough, I will read through your suggested link and verify
all is good. (I know I did successfully transfer 5 FSMO roles
successfully).

As well, all my client machines log in to the network just fine. They
run their login scripts. I can see no errors at all except this one
about the time service.

I'm about to start yanking out clumps of my hair.

 

[Paul Bergson]

netdom query fsmo

--

Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
http://www.pbbergs.com

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[JMS]

check this link:
http://technet2.microsoft.com/WindowsServer/en/Library/539c5381-db4f-445f-aac0-2df5448181c11033.mspx

See example
Example 25: List the Primary Domain Controller Emulator in a Domain.

I holp it helps
regards

 

[Terry]

Well, I've checked things over once more.
Results of the 'netdom query fsmo command':

Schema owner bingpdc.bingdom.com
Domain role owner bingpdc.bingdom.com
PDC role bingpdc.bingdom.com
RID pool manager bingpdc.bingdom.com
Infrastructure owner bingpdc.bingdom.com
The command completed successfully.

The correct server has all the roles it should.

DCDiag results are the same as before--still won't advertise as a time
server
:-(

The W32Time service is running on the new PDC and it is successfully
synchronizing to pool.ntp.org.

Aaaaargh!

 

[JMS]

Take it easy...

see if ti helps
http://www.windowsnetworking.com/articles_tutorials/Configuring-Windows-Time-Service.html

 

[Terry]

Okay, here's what I've done now.
I have made the old PDC (bingserv) I demoted to a member server a DC
again, BUT I left all the FSMO settings intact in the new PDC
(bingpdc). So, now I have two DC's.
bingpdc holds all the FSMO roles and bingserv _shouldn't_ have any.

I ran dcdiag /q /v on both machines. Here are the results...

BINGSERV -- the old PDC I demoted to a member server and now promoted
to a DC
Starting test: FsmoCheck
GC Name: \\bingpdc.bingdom.com
Locator Flags: 0xe00001bd
PDC Name: \\bingpdc.bingdom.com
Locator Flags: 0xe00001bd
Time Server Name: \\bingserv.bingdom.com
Locator Flags: 0xe00001f8
Preferred Time Server Name: \\bingserv.bingdom.com
Locator Flags: 0xe00001f8
KDC Name: \\bingserv.bingdom.com
Locator Flags: 0xe00001f8
......................... bingdom.com passed test FsmoCheck

BINGPDC -- the new hardware and current PDC (holds the FSMO roles I
transferred)
Starting test: FsmoCheck
GC Name: \\bingpdc.bingdom.com
Locator Flags: 0xe00001bd
PDC Name: \\bingpdc.bingdom.com
Locator Flags: 0xe00001bd
Time Server Name: \\bingserv.bingdom.com
Locator Flags: 0xe00001f8
Preferred Time Server Name: \\bingserv.bingdom.com
Locator Flags: 0xe00001f8
KDC Name: \\bingpdc.bingdom.com
Locator Flags: 0xe00001bd
......................... bingdom.com passed test FsmoCheck

BOTH servers believe that bingserv (my old hardware) is the time server
and the preferred time server.

I have set the registry settings for w32time on BINGSERV with:
ReliableTimeSource=0

I have set the registry settings for w32time on BINGPDC with:
ReliableTimeSource=1


How is this possible?!

How can I transfer this FSMO role of the Time Server? Why does my old
hardware INSIST on holding onto this role? How can I force this role to
move to my new hardware.

One other interesting thing...
Each server sees itself as the KDC.......isn't that a problem?
Shouldn't there be one KDC?

 

[Terry]

Just as follow-on info:
W32Time service settings on the two machines
BINGPDC (new hardware, PDC and FSMO role holder)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
"LocalNTP"=dword:00000001
"AvoidTimeSyncOnWAN"=dword:00000000
"ServerType"="NTP"
"Adj"=dword:0001872f
"msSkewPerDay"="843.0000"
"ReliableTimeSource"=dword:00000001
"MaxAllowedClockErrInSecs"=dword:00000384
"Log"=dword:00000064
"WriteLog"="True"
"Period"="SpecialSkew"
"Type"="NTP"
"NtpServer"="pool.ntp.org"
"GetDcBackoffMaxTimes"=dword:00000001

BINGSERV (old hardware and DC)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
"LocalNTP"=dword:00000000
"AvoidTimeSyncOnWan"=dword:00000001
"Adj"=dword:00018716
"msSkewPerDay"="5632.0000"
"ReliableTimeSource"=dword:00000000
"Type"="Nt5DS"

 

[Terry]

I've realized part of my problem. Long, long ago, I installed the NT 4
time service (timeserv.exe).
Both the timeserv and w32time services are running on my bingserv
server (the old PDC). I can remove the service (through registry
deletions according to this article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;238458),
but I don't know if just removing this service will make my old PDC
stop advertising itself as a time server. I've stopped the service and
it hasn't made a difference. It still believes it is the time server.

Any suggestions on how to properly remove this service so it will stop
advertising itself as the time server?