loosain
asked on
Time sync with domain controller isn´t working
Hi,
we have the problem that some clients have wrong time (few minutes) to each other. In the event protocol it says, that there was no answer from domaincotroller and it wouldn´t be used as timeserver anymore.
Time-Service is running on the server and there is no Firewall active.
If i use "w32tm /monitor" on a client, it gives the following warning:
Reverse name resolution is best effort. It may not be
correct since RefID field in time packets differs across
NTP implementations and may not be using IP addresses
What does this warning mean ?
We have a server 2012 and win7-Clients.
Thanks in advance.
we have the problem that some clients have wrong time (few minutes) to each other. In the event protocol it says, that there was no answer from domaincotroller and it wouldn´t be used as timeserver anymore.
Time-Service is running on the server and there is no Firewall active.
If i use "w32tm /monitor" on a client, it gives the following warning:
Reverse name resolution is best effort. It may not be
correct since RefID field in time packets differs across
NTP implementations and may not be using IP addresses
What does this warning mean ?
We have a server 2012 and win7-Clients.
Thanks in advance.
David Johnson, CD
did you enable reverse dns zones?
Time sync for workstations is automatic. When a machine is on the domain it will get its Time from the PDC (if you have a GPO which points to this DC directly) or it will use the domain time sync hierarchy (any domain controllers in the domain). These domain controllers get their time from the PDC so this scenario also works (and this is my preferred method).
Is this happening to ALL clients? If so, i have seen issues like this when computers/servers have not be Syspreped properly.
Are you getting any errors on the domain controllers themselves?
Will.
Is this happening to ALL clients? If so, i have seen issues like this when computers/servers have not be Syspreped properly.
Are you getting any errors on the domain controllers themselves?
Will.
If i use "w32tm /monitor" on a client, it gives the following warning:
Reverse name resolution is best effort. It may not be
correct since RefID field in time packets differs across
NTP implementations and may not be using IP addresses
What does this warning mean ?
It means that reverse DNS resolution may not work, but it probably has nothing to do with resolving the time servers themselves. What's the rest of the output look like?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The antivirus (firewall) was the problem...