Re: IP address change on Active Directory Server

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Joe Richards [MVP] (humorexpress_at_hotmail.com)
Date: 07/07/04 

Date: Wed, 07 Jul 2004 16:43:31 -0400

Hmm I have to say the guy was certainly creative... I hope you shoed him out the
door and note that shoed is not a mispelling of shoo'ed. I mean hopefully he
went out the door on the end of a shoe.

Yeah those errors are most certainly DNS related. That tends to be the case with
a great many AD issues.

If you only have DNS on one server, you should definitely set up a backup
somewhere, whether it is on a DC or not is your call. Otherwise if you lose that
DC your whole DNS structure falls down as well. 

--
Joe Richards Microsoft MVP Windows Server Directory Services
www.joeware.net
anonymous@discussions.microsoft.com wrote:
> Basically what the guy fed me was that the SSID's for the 
> DC's were changed and that killed the replication 
> partnership between them.  He said that it occured due to 
> the ip stack being refreshed.  
> 
> I was being given several errors when the servers would 
> attempt to replicate. Below are examples of them.
> 
> -------------------------------------------------------
> Domain Controller Name:  SERVER1
> Directory Partition:        
> CN=Schema,CN=Configuration,DC=mydomain,DC=edu
>               Replication Partner:        Default-First-
> Site-Name\SERVER2
>               Failure Code:                8524
>               Failure Reason:             The DSA 
> operation is unable to proceed because of a DNS lookup 
> failure.
> 
> 
> Domain Controller Name:                   SERVER2
>               Directory Partition:        
> DC=mydomain,DC=edu
>               Replication Partner:        Default-First-
> Site-Name\Server1              Failure 
> Code:                5
>               Failure Reason:             Access is denied.
> 
> -------------------------------------------------------
> 
> I'll admit that I'm new to ADS and its directory 
> structure.  So it is possible that I hosed something in 
> the DNS when we first set it up.  
> 
> Another question we only have DNS setup on one of our 
> DC's.  Should we have it setup on both?  Thanks.
> 
> -Dan
> 
> 
> 
> 
>>-----Original Message-----
>>Nope. Just make sure that name resolution is fine and you 
> 
> should be ok. If the 
> 
>>server is a DNS or WINS Server you will need to make sure 
> 
> that the clients and 
> 
>>other DNS/WINS Servers know the change occurred.
>>
>>As for your other issue, someone was feeding you a line. 
> 
> In my last position we 
> 
>>had about 400 Dell Domain Controllers. We replaced 
> 
> motherboards occasionally and 
> 
>>most everything was on the motherboard for the low end 
> 
> systems we were using and 
> 
>>we didn't see issues that you describe. Most likely 
> 
> figured that was an answer 
> 
>>you would buy and didn't know the real reason but didn't 
> 
> need to because you 
> 
>>bought that answer.
>>
>> joe
>>
>>--
>>Joe Richards Microsoft MVP Windows Server Directory 
> 
> Services
> 
>>www.joeware.net
>>
>>
>>
>>Dan wrote:
>>
>>>We're in the process of switching over from a class C 
>>>address schema to a class B.  Are there any problems 
> 
> that 
> 
>>>you know of that this would pose with our Active 
> 
> Directory 
> 
>>>Services.  We are currently running 2 Windows 2000 
> 
> domain 
> 
>>>controllers on our network.
>>>
>>>We had an issue when dell replaced the motherboard on 
> 
> one 
> 
>>>of these servers and it had an embedded network card 
> 
> that 
> 
>>>was handling the network connection.  I was told there 
> 
> was 
> 
>>>something about a TCP/IP stack change/refresh that 
> 
> caused 
> 
>>>the replication to fail and the partnership to 
>>>termininate.  I had to demote/promote the DC to get it 
>>>working again.  Basically I want to prevent this if at 
> 
> all 
> 
>>>possible in this changeover to the new class B. 
>>>
>>>Any information or tips would be greatly appreciated.  
>>>Thanks.
>>>
>>>-Dan
>>
>>.
>>

Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... DNS Host Name: tonyb-pc.imageproc.imageproc.com ... Testing IpConfig - pinging the DHCP Server... ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)