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 PM To: NT System Admin Issues Subject: RE: Bizarro-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 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 Admin Issues Subject: Bizarro-world I replaced a production file-print server this weekend (Friday night specifically), but am having some weird results. Site1 is the main site where I am. Site2 is where the new server is and also on the same domain and has its own DC. The method I used was Server1 was: 1) Build Server2, join to domain 2) Rename Server1 to Server1-old, change IP address 3) Renamed Server2 to Server1 and changed IP address to what Server1 was >From Site2 users are able to use their new server fine, and from DC1 at Site2 I can UNC to \\Server1 >From Site1 if I try to UNC to \\SERVER1 <file:///\\SERVER1> I get "Logon Failure: The target account name is incorrect" which is what I'd expect to see if the machine account was invalid for the domain. I get this even if I try to UNC from a DC at Site1. Security log shows multiple 529 failures, so I'm confused why it'd work at their site but not ours? I'm guessing removing / rejoining it would fix it, but that wouldn't tell me why it's sorta broken. David Lum // SYSTEMS ENGINEER NORTHWEST EVALUATION ASSOCIATION (Desk) 971.222.1025 // (Cell) 503.267.9764 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
