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
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 - t
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 prima
On Wed, Jun 9, 2010 at 11:00 AM, Bob Anderson
wrote:
> 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
Are DNS records correct for this DC?
Can the new DC ping other DC's by FQDN and vice versa?
Is this DC a DNS server and pointing to itself?
What do event logs show?
David Lum // SYSTEMS ENGINEER
NORTHWEST EVALUATION ASSOCIATION
(Desk) 971.222.1025 // (Cell) 503.267.9764
-Original Message---
