• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1541
  • Last Modified:

Timeserv utility in Windows 2003 server domain?

I recently upgraded from a Windows 2000 to a Windows 2003 domain. I have a mix of Windows NT 4.0, Windows 2000 and Windows XP clients on my network that are running the timeserv utility. After upgrading the domain, this has stopped working. I get the following error messages in the log:

NetRemoteTOD failed for each PrimarySource


It has been over 24 hours since we got a network succeess.

I did replace dcs when I upgraded the domian. I specified the new primary source in the timeserv.ini file as \\'name of pdc' (used netbios name)

FYI - It is important that I have time set to the second so I can't rely on w32time or one time sycn when users logon by using net time.

1 Solution
you stopped w32time service?
you set your PDC Emulator as Source for all DC's?
you set any DC as a source for your clients?
do you get the messages on all computers?
Joe_S_NYAuthor Commented:
I figure it out - I forgot to run timeserv -update on the workstations after I changed the primary server in the timeserv.ini file.
PAQed with points refunded (500)

Community Support Moderator

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

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.

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