W32time errors on servers

  • Thread starter Thread starter Steven
  • Start date Start date
S

Steven

Hello, If I type net time on any computer in my network it
replys with a server that in located over a WAN link.
WANserver not with a local server. This includes the PDC
emulator located on the same network.

No matter what I do I always seem to get from any computer
on any network. Except for the successfully when the wan
link is slow.

C:\>net time
Current time at \\WANSERVER is 12/22/2003 9:13 AM

The command completed successfully.

I have read the document "The Windows Time Service" and
done all of the suggestions.
..
 
Steven said:
Hello, If I type net time on any computer in my network it
replys with a server that in located over a WAN link.
WANserver not with a local server. This includes the PDC
emulator located on the same network.
Click to expand...

Can you explain your Site organization? Did you configure a site for remote
network? While the PDC is the time authority on a domain, clients will
synchronize with their login DC which are themselves independently synced
with "PDC emulator".

http://www.microsoft.com/technet/prodtechnol/ad/windows2000/maintain/opsguid
e/Part1/adogd06.asp
 
We have 3 sites. Two remote and one local. WANSERVER is
located at a remote site. It has a copy of the directory
but has no roles defined to it. Each remote site is
connected by one T1 connection and a backup 512
connection. WANSERVER is probably the least worked server
in the company that is a DC. DNS is part of active
directory. The PDC emulator is in the local LAN. The PDC
emulator is the main DNS and WINS server and is worked
heavily.
 
Another note, if you are on wanserver and stop the time
service, it replys with the PDC emulator's server name, if
you start the service it replys with itself. If you go to
the PDC emulator and type net time, it replys with
wanserver, if you stop the service on wanserver, it still
replys with wanserver.
 
If the PDC emulator is on local LAN, try modifying/resetting the password of
a given user in Users and Computers and log in to network. That should then
force a login to emulator instead of remote DC. Note there is a KB article
that suggests installing the latest service pack to correct the issue.

If you have a router, you might consider modifying the route metric between
the local subnet and remote site. Since a login should connect to closest DC
theoretically, that should prevent users from being authenticated accross
Link. I'm willing to bet that the problem you have resolves around how
packets are routed around your network.
 
Back
Top