disable server 2000 time service

[Guest]

Hi, I just migrated my company to 2003 active directory from an NT 4
platform. I have configured the AD domain controller as the NTP server so
that the network syncs time with the DC and the DC syncs time with an online
time server. the problem is that prior to the migration, the company had a
few NT4 and 2000 member servers acting as time servers. I diabled the time
server services on all the acting servers and they still appear to be
broadcasting that they are time servers when I no a net time with an XP
machine. The time however does appear to be syncing with the 2003 AD domain
controller. Very strange. Please HELP!!!

 

[Guest]

Did you check your DHCP scope options to see if that is where the XP boxes
are getting the information about the older NTP servers?

 

[Guest]

Yes, I check and configured the scope to reflect the 2003 AD as the NTP and
time server. There are no other servers listed

 

[Guest]

same problem, if I do a net time, it shows the 2000 server as the time server
and not the DC

 

[Charlie Tame]

command window

net time /querysntp should tell you what they are set at.

net time /setsntp:xxx.xxx.xxx.xxx you new server

Have the time service running

See what happens

What do you see when you double click the clock and go to internet time tab?

I am not sure if this will make a difference or not, but I think it might.

Good luck

Charlie

 

[Phillip Windell]

same problem, if I do a net time, it shows the 2000 server as the time server
and not the DC

Let's backup to the beginning. You don't have to "configure the AD domain
controller as the NTP server". It is automatic. Member machines (2000 and
newer) will always sync their time to the one DC that carries the PDC "Role"
(not the same thing as the PDC in the NT world). The fact that you tried to
do it manually may have screwed things up.

"Unjoin" the machines from the Domain and rejoin them. They will *actively*
go to the DC with the "PDC Role" for their Time,...they do not respond to
"broadcasts",...the other servers can broadcast till the are "blue in the
face" that they are "time servers"and it isn't going to matter, they will be
ignored.

NT4 machines and Win95x/98x machine do not sync thier time at all unless you
rig that up yourself. via a batch file or a logon script. This requires the
Local System Policy to be altered in the case of NT4 machines because normal
users (which the logon script or batch file runs "as") is not allowed to
change the clock.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/prodtechnol/isa/2004/deploy/dgisaserver.mspx
-----------------------------------------------------