Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 455
  • Last Modified:

w32time error

In order to build a test platform to migrate an Exchange Organisation from 5.5 and 2K to 2K3, I installed a test platform.

Firts, I installed a W2K (SP4) server as the server of the root domain test.com.

Then, I installed a child domain (W2K3) a.test.com.

Before installing the child domain, I launched the forestprep and domainprep of W2K3 CD on the controler of the root domain.

Wen I restart the W2K server, following messages are logged in the System EV:

Type : Error
Source : W32time
Event : 62
This machine is a PDC of the domain at the root of the forest. Configure to sync from externam time source using the net command 'net time ...'

This message is logged several times (2 per hour).

There are also 2 warnings : 5781 and 54.

On the child domain (W2K3) I can find following warnings just after having rebooted : 40960 and 40961. According to the article 823712 of Microsoft KB, it is not necessary a problem).

The W2K server is the time server for the W2K3 server (KB 216734 and 257187)

I wan't to be sure that there isn't any issue on this side before doing Exchange tests.
Thanks.
Fred
0
fho
Asked:
fho
  • 3
  • 2
2 Solutions
 
BigC666Commented:
0
 
fhoAuthor Commented:
Thanks for the thread, but I had already read it.
The problem is that  I can't connect the test platform to any external time server source (no internet access).
That's why I've configured the server in the root domain as an authoritative time server (KB 216734) and the W2K3 server in the child domain as a client.
I've checked that both are time synchronized.
My question is more to know if errors that are logged in the EV are serious and must be taken into account, and if they indicate a communication issue between the root and child domain.
Unfortunately, I'm sure that I'll have lots of other issues to solve during the migration of my exchange servers, and don't want to add this one as a potential cause.
Fred
0
 
BigC666Commented:
as far as i've found, the only problem with this is in the adding of boxes to the domain, if they can't sync the time with some source then then can't join or logon to a domain.
sorry
0
How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

 
Debsyl99Commented:
Hi
You should be able to set the Win2k server to not synchronise with an external time source and this will prevent the error. See how in the link below. Time synchronisation isn't essential with an external time server for the purposes of the domain running correctly - it is essential though within the domain but it seems as though you have that running fine. As long as all other servers and pc's within the domain can sync with this server then all should be well,
Windows Time Synchronization Settings
http://www.winguides.com/registry/display.php/1118/

Deb :))
0
 
BigC666Commented:
thanx Deb, that's a new ref. for me.
0
 
Debsyl99Commented:
Howdy BigC666 - Cool :))
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now