Win2k Server setup blues

[renorocks]

I just finished the basic install of win2k server. I have a small home network and am using it as a domain controller. I am using static IP
addressing. I noticed that on bootup I get three warnings in the sys event manager and one error. How can I get rid of them.

1) error: W32Time.....The machine is a PDC of the domain at the root of the forest. Configure to sync from external time source using the
net command. "net time/setsntp:<server name>.
I ran this command from start / run, the screen blinked briefly. I still get the W32Time error. What's up ??

2) warning: W32Time....The Windows Time Service was not able to find a domain controller. A time and date update was not possible

3) warning: Netlogon....Dynamic registration or deregistration of one or more DNS records failed because no DNS servers are available.

4) warning: Disk....The driver disabled write cache on device: \device\harddisk0\DR0

Update: I disabled Windows Time in the component manager and the error went away, but it would be cool to know how to configure it

 

[Saltin]

Th net time thing is easy to fix. Do a search on google for a time source. I used to know a military one that I set everything too, but its been a while. You use the net time command to do this.
Because you only have one DC it's not the end of the world if you don't have a reliable outside timesource. If you were to add a couple more DC's you would want them all the be syncd. AD replication relies on this.

As for the netlogon.... check your forward lookup zone in DNS. Right click it, select Properties and ensure that dynamic updates are enabled.

 

[Woodie]

Actually, time sync within the domain is critical. Kerberos depends on the the client/server/kdc all being time-synched, so if the DC is 5 minutes fast, the client 5 minutes slow, no user will be able to login from that client.

Note: This would affect Kerberos enabled clients! NTLM would continue to function just fine.

--Woodie

 

[Saltin]

Woodie: I am assuming the client and server are synched. Since he's only got one DC, it must be the PDC Emulator, which handles time sync in the domain. If the client is net timed to the DC, those concerns are nil.
The real problem here is that the PDC Emulator role on the DC is not synched to a reliable outside source. This, as I pointed out, is only a concern in a multiple domain environment.

 

[Woodie]

<< If the client is net timed to the DC, those concerns are nil. >>



Agreed. *If*.

--Woodie