Re: Event ID 13548 ntfrs

Hello Andrew,

If you read the complete article you could see at the end that it will.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


Thanks for the link,

Does this also work on Windows 2000?

"Salvador Manaois III" <SalvadorManaoisIII@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
news:043FF645-59D3-463D-89A8-3EF4121DB7EF@xxxxxxxxxxxxxxxx

Hi Andrew,

Please follow the steps outlined here:

http://support.microsoft.com/kb/914387

You need to create a .reg file and a .vbs file which you need to push
to
affected machines. The KB should provide you the guidance on how to
go
about
with this exercise.
--
...Badz...
MCSE MCSA CEH MCITP | Enterprise/Server Admin
Bytes & Badz : http://badzmanaois.blogspot.com
"Andrew Story" wrote:

Hi Meinholf,

I've read both articles, but they can't tell me how to proceed with
rectifying the time difference when all looks setup correctly. The
time
zones are set correctly for the servers in UK and Australia (GMT and
+10
respectively), they should have 10 hours difference, but instead
have 9
and
it's this which is causing the issue.
Any ideas on how to resolve this?

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb66954b8caf81561ee5a17@xxxxxxxxxxxxxxxxxxxxxxx

Hello Andrew,

From:
http://technet.microsoft.com/en-us/library/bb727056.aspx#EIAA

FRS event ID 13548 is logged when the time settings for two
replication
partners differ by more than 30 minutes. This error could be caused
by
the
selection of an incorrect time zone on the local computer or its
replication partner.
Check that the time zone and system clock are correctly set on both
computers. They must be within 30 minutes of each other, but
preferably much closer.

From: http://support.microsoft.com/kb/308406

Event ID: 13548 Event Type: Error Rule: Alert suppressed based on
ID,
source, computer Message Text: 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 regedt32. Click on Start, Run and
type regedt32.

Click on the window entitled 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 Add Value
function
under
the Edit Menu item. Type the value name exactly as shown above
using
the
the registry data type REG_DWORD.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Hi,

My DC's in Australia have their clocks 1 hour out.

The DC with the PDCe role is in the UK and has the correct time
and time zone set, all the servers in Aus have their correct time
zone set but the clock on all the servers are 1 hour slow.
They've just gone to daylight saving at the weekend but the clock
have stayed the same time although the time zone has been updated,
it says +10 hours, but all the clocks still show +9 hours.

I've rebooted server, restarted the w32time service - anyone have
any ideas how I can fix this?? All server and DC's are Windows
2000.

Cheers.



.

Relevant Pages

  • Re: Event ID 13548 ntfrs
    ... zones are set correctly for the servers in UK and Australia (GMT and +10 ... Check that the time zone and system clock are correctly set on both ... replicate with its partner computer because the difference in clock ...
    (microsoft.public.windows.server.active_directory)
  • Re: Event ID 13548 ntfrs
    ... zones are set correctly for the servers in UK and Australia (GMT and +10 ... Check that the time zone and system clock are correctly set on both ... replicate with its partner computer because the difference in clock times ...
    (microsoft.public.windows.server.active_directory)
  • Re: Event ID 13548 ntfrs
    ... FRS event ID 13548 is logged when the time settings for two replication partners differ by more than 30 minutes. ... This error could be caused by the selection of an incorrect time zone on the local computer or its replication partner. ... 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. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Event ID 13548 ntfrs
    ... zones are set correctly for the servers in UK and Australia (GMT and +10 ... Check that the time zone and system clock are correctly set on both ... replicate with its partner computer because the difference in clock times ...
    (microsoft.public.windows.server.active_directory)
  • TIP #173: Internationalisation and Refactoring of the clock Command
    ... The [clock] command provides Tcl's fundamental facilities for computing ... {locale era, locale year, month, day of month}: ... If the given format does not include a time zone, ...
    (comp.lang.tcl)
Quantcast