The server can both ping each other but my DSN logs are throwing 4000 4011 and 9999
How would I remove the netlogon.dns Again thanks Bob IT Manager -----Original Message----- From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Wednesday, June 09, 2010 11:05 AM To: NT System Admin Issues Subject: RE: Server won't replicate When did you change the IP address? It seems likely that you didn't do it before you moved it down there, so both local and remote DNS is fubar'ed. On the remote end you'll need to stop netlogon, remove netlogon.dns, and reboot - that should cause the proper records to get registered. The primary DNS server for that server, at least until replication is working, should be the server at the home office. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Bob Anderson [mailto:bander...@kentwatersports.com] Sent: Wednesday, June 09, 2010 11:00 AM To: NT System Admin Issues Subject: Server won't replicate Hello, I have a W23 server that we built here and joined the network here and made him a DC. We then powered him off and packed him up and sent him to our Texas facility to be a local DC for logging on to the domain. However once he powered up he will not replicate with the DCs here. His IP address has changed but all else remains the same. On our DCs he is in the Texas DC site but no replication. Thanks for any help you may provide. Bob Anderson IT Manager Kent Sporting Goods Inc. 433 Park Ave. S New London OH 44851 419-929-7021 x315 P Please consider the environment before printing this e-mail. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
