Windows Server

Fab · Guest

I have a Dfs system setup on W2k servers that are member servers. With
the time server running on the DCs, can ntfrs service on my servers be
affected if the time on my servers is messed up? For example, if the
time server on the DC is messed and and set to a time 10 months ago and
remains so for at least half a day, the time on all member servers will
be messed up as well because they all sync their time with the DC. Will
this situation cause FRS to error out with errors such as
"FrsErrorMismatchedJournalId" or "assertion failure".

Thanks,

F.

Paul Williams [MVP] · Guest

In addition to what Jill has said, you need to realise that time is now very
important. You must ensure that Windows Time is running properly across you
forest. Not just for timestamping, and calendar mismatches, etc. but there
are more and more services depending on it. Certainly, you don't want to be
dropping back to NTLMv2 if you can help it - not just because Kerberos is
more secure but because it changes the way Windows logon works, for example,
which will cause issues in hardened, firewall-segmented setups.

--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net

Jill Zoeller [MSFT] · Guest

FRS is definitely affected by time differences. I'm pasting in two separate
event IDs that are triggered when the time is out of sync.

13548
The File Replication Service is unable to replicate with its partner
computer because the difference in clock times is outside the range of plus
or minus %1 minutes.

The connection to the partner computer is: "%2"

The detected time difference is: %3 minutes.

Note: If this time difference is close to a multiple of 60 minutes then it
is likely that either this computer or its partner computer was set to the
incorrect time zone when the computer time was initially set. Check that the
time zone and the system time are correctly set on both computers.

If necessary, the default value used to test for computer time consistency
may be changed in the registry on this computer. (Note: This is not
recommended.)

To change this parameter, run regedit.

Click Start, Run and type regedit.

Expand HKEY_LOCAL_MACHINE.

Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"

Double click on the value name "Partner Clock Skew In Minutes" and update
the value.

If the value name is not present you may add it with the New->DWORD Value
function under the Edit Menu item. Type the value name exactly as shown
above.

13549
The File Replication Service is unable to replicate from a partner computer
because the event time associated with the file to be replicated is too far
into the future. It is %1 minutes greater than the current time. This can
happen if the system time on the partner computer was set incorrectly when
the file was created or updated. To preserve the integrity of the replica
set this file update will not be performed or propagated further. The file
name is: "%2" The connection to the partner computer is: "%3" Note: If this
time difference is close to a multiple of 60 minutes then it is likely that
this file may have been created or updated on the partner computer while the
computer was set to the incorrect time zone when its computer time was
initially set. Check that the time zone and time are correctly set on the
partner computer.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Fab" <fuladi@yahoo.com> wrote in message
news:1125072217.395837.308280@f14g2000cwb.googlegroups.com...

	Windows Server Forum Index -> DFS and FRS	All times are GMT
Page 1 of 1