l) 503.267.9764
>
> *From:* Michael B. Smith [mailto:mich...@theessentialexchange.com]
> *Sent:* Monday, March 02, 2009 11:32 AM
>
> *To:* NT System Admin Issues
> *Subject:* RE: Bizarro-world - addendum
>
>
>
> Yep, and that defines the problem. Either DNS or WINS is br
That'll do it too.
From: David Lum [mailto:david@nwea.org]
Sent: Monday, March 02, 2009 4:13 PM
To: NT System Admin Issues
Subject: RE: Bizarro-world - addendum
How about a time skew of 12 minutes between the local and remote DC's? J
David Lum // SYSTEMS ENGINEER
ystem Admin Issues
Subject: RE: Bizarro-world - addendum
Yep, and that defines the problem. Either DNS or WINS is broken (or VPN
or...long possible list - DNS or WINS is most likely) and replication is
failing.
From: Jim Majorowicz [mailto:jmajorow...@gmail.com]
Sent: Monday, March 02, 2009 2:16
-world - addendum
The math does appear to be correct, sir.
From: David Lum [mailto:david@nwea.org]
Sent: Monday, March 02, 2009 9:25 AM
To: NT System Admin Issues
Subject: RE: Bizarro-world - addendum
REPLMON results "Changes have not been successfully replicated from Site2
DC1 in
The math does appear to be correct, sir.
From: David Lum [mailto:david@nwea.org]
Sent: Monday, March 02, 2009 9:25 AM
To: NT System Admin Issues
Subject: RE: Bizarro-world - addendum
REPLMON results "Changes have not been successfully replicated from Site2
DC1 in 5502 att
REPLMON results "Changes have not been successfully replicated from Site2 DC1
in 5502 attempts".
Check my math...at 15 minute intervals I come up with 5502/4 = 1375 hours = 57
days...right?
Dave
From: David Lum [mailto:david@nwea.org]
Sent: Monday, March 02, 2009 8:18 AM
To: NT System Admi
