none
Active Directory domain controller could not be contacted

    Question

  • Hello

    Help please.

    I am trying to add a new server (2008) to domain 'bridgelimited.local' - only one DC (2003) doing everything at the moment. The plan is to add the new server, then move everything over from the old machine, then retire/upgrade the old machine and use as a backup.

    I am currently trying to dcpromo on the new machine but I get the following error:

    The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller for domain bridgelimited.local:

    The error was: "DNS name does not exist."
    (error code 0x0000232B RCODE_NAME_ERROR)

    The query was for the SRV record for _ldap._tcp.dc._msdcs.bridgelimited.local

    Common causes of this error include the following:

    - The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:

    212.50.160.100
    196.168.16.2

    - One or more of the following zones do not include delegation to its child zone:

    bridgelimited.local
    local
    . (the root zone)

    For information about correcting this problem, click Help.


    192.168.16.2 is IP address for the DC.


    Any help would be grately appreciated.

    Kind Regards

    Richard

    Thursday, September 10, 2009 12:50 PM

Answers

  • Hello,

    you have still the ip configuration with 2 ip addresses for the LAN and an external, please follow the advises above and reconfigure the server ip addressing.


    Again, MULTIHOMING Domain controllers is not recommended, it always results in multiple problems.
    -----------------------------------------------------------------------
    1. Domain Controllers should not be multi-homed
    2. Being a VPN Server and even simply running RRAS makes it multi-homed.
    3. DNS,..even just all by itself, is better on a single homed machine.
    4. Domain Controllers with the PDF Role are automatically Domain Master
    Browser. Master Browsers should not be multi-homed

    272294 - Active Directory Communication Fails on Multihomed Domain Controllers http://support.microsoft.com/default.aspx?scid=kb;en-us;272294

    191611 - Symptoms of Multihomed Browsers
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;191611

    Phillip Windell
    www.wandtv.com

    The views expressed, are my own and not those of my employer, or Microsoft, or anyone else associated with me, including my cats. -----------------------------------------------------


    See also:

    Multihomed DCs, DNS, RRAS servers.
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++
    Below are the manual steps in more detail, which I had outlined in the above
    paragraph:

    Honestly, multi-homed DCs are not recommended because of the associated issues that can occur, as you've encountered. We usually recommend purchasing an inexpensive Linksys, DLink, etc, Cable/DSL router to perform NAT for you, take out the extra NIC off the DC, but still let the DC handle DHCP (and not the router).

    Little background on AD and DNS:
    First, just to get this out of the way, if you have your ISP's DNS addresses
    in your IP configuration (DCs and clients), they need to be REMOVED.

    If the ISP's DNS is in there, this will cause additional problems.

    Also, AD registers certain records in DNS in the form of SRV records that signify AD's resource and service locations. When there are multiple NICs, each NIC registers. IF a client, or another DC queries DNS for this DC, it may get the wrong record. One factor controlling this is Round Robin. If a DC or client on another subnet that the DC is not configured on queries for it, Round Robin will kick in offering one or the other. If the wrong one gets offered, it may not have a route to it. On the other hand, Subnetmask Priortization will ensure a querying client will get an IP that corresponds to the subnet it's on, which will work. To insure everything works, stick with one NIC.

    Since this DC is multi-homed, it requires additional configuration to prevent the public interface addresses from being registered in DNS. This creates a problem for internal clients locating AD to authenticate and find other services and resources such as the Global Catalog, file sharing and the SYSVOL DFS share and can cause GPO errors with Userenv 1000 events to be logged, authenticating to shares and printers, logging on takes forever, among numerous other issues.

    But if you like, there are some registry changes to eliminate the registration of the external NIC. Here's the whole list of manual steps to follow.

    But believe me, it's much easier to just get a separate NAT device or multihome a non-DC then having to alter the DC. - Good luck!

    1. Insure that all the NICS only point to your internal DNS server(s) only and none others, such as your ISP's DNS servers' IP addresses.

    2. In Network & Dialup properties, Advanced Menu item, Advanced Settings, move the internal NIC (the network that AD is on) to the top of the binding order (top of the list).

    3. Disable the ability for the outer NIC to register. The procedure, as
    mentioned, involves identifying the outer NIC's GUID number. This link will
    show you how:
    246804 - How to Enable-Disable Windows 2000 Dynamic DNS Registrations (per
    NIC too):
    http://support.microsoft.com/?id=246804

    4. Disable NetBIOS on the outside NIC. That is performed by choosing to
    disable NetBIOS in IP Properties, Advanced, and you will find that under the
    "WINS" tab. You may want to look at step #3 in the article to show you how
    to disable NetBIOS on the RRAS interfaces if this is a RRAS server.
    296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
    [Registry Entry]:
    http://support.microsoft.com/?id=296379

    Note: A standard Windows service, called the "Browser service", provides the list of machines, workgroup and domain names that you see in "My Network Places" (or the legacy term "Network Neighborhood"). The Browser service relies on the NetBIOS service. One major requirement of NetBIOS service is a machine can only have one name to one IP address. It's sort of a fingerprint. You can't have two brothers named Darrell. A multihomed machine will cause duplicate name errors on itself because Windows sees itself with the same name in the Browse List (My Network Places), but with different IPs. You can only have one, hence the error generated.

    5. Disable the "File and Print Service" and disable the "MS Client Service" on the outer NIC. That is done in NIC properties by unchecking the respective service under the general properties page. If you need these services on the outside NIC (which is unlikely), which allow other machines to connect to your machine for accessing resource on your machine (shared folders, printers, etc.), then you will probably need to keep them enabled.

    6. Uncheck "Register this connection" under IP properties, Advanced settings, "DNS" tab.

    7. Delete the outer NIC IP address, disable Netlogon registration, and manually create the required records

    a. In DNS under the zone name, (your DNS domain name), delete the outer NIC's IP references for the "LdapIpAddress". If this is a GC, you will need to delete the GC IP record as well (the "GcIpAddress"). To do that, in the DNS console, under the zone name, you will see the _msdcs folder. Under that, you will see the _gc folder. To the right, you will see the IP address referencing the GC address. That is called the GcIpAddress. Delete the IP addresses referencing the outer NIC.

    i. To stop these two records from registering that information,
    use the steps provided in the links below:
    Private Network Interfaces on a Domain Controller Are Registered in
    DNShttp://support.microsoft.com/?id=295328

    ii. The one section of the article that disables these records is done with this registry entry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
    (Create this Multi-String Value under it):
    Registry value: DnsAvoidRegisterRecords
    Data type: REG_MULTI_SZ
    Values: LdapIpAddress
    GcIpAddress

    iii. Here is more information on these and other Netlogon Service records:

    Restrict the DNS SRV resource records updated by the Netlogon service

    [including GC]:

    http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windowsserver2003/proddocs/standard/sag_dns_pro_no_rr_in_ad.asp

    b. Then you will need to manually create these two records in DNS with the IP addresses that you need for the DC. To create the

    LdapIpAddress, create a new host under the domain, but leave the "hostname"
    field blank, and provide the internal IP of the DC, which results in a
    record that looks like:
    (same as parent) A 192.168.5.200 (192.168.5.200 is used for illustrative
    purposes)

    i. You need to also manually create the GcIpAddress as well, if this is a GC. That would be under the _msdcs._gc SRV record under the zone. It is created in the same fashion as the LdapIpAddress mentioned above.

    8. In the DNS console, right click the server name, choose properties, then under the "Interfaces" tab, force it only to listen to the internal NIC's IP address, and not the IP address of the outer NIC.

    9. Since this is also a DNS server, the IPs from all NICs will register,
    even if you tell it not to in the NIC properties. See this to show you how
    to stop that behavior (this procedure is for Windows 2000, but will also
    work for Windows 2003):
    275554 - The Host's A Record Is Registered in DNS After You Choose Not to
    Register the Connection's Address:
    http://support.microsoft.com/?id=275554

    10. If you haven't done so, configure a forwarder. You can use 4.2.2.2 if
    not sure which DNS to forward to until you've got the DNS address of your
    ISP.
    How to set a forwarder? Good question. Depending on your operating
    system,choose one of the following articles:

    300202 - HOW TO: Configure DNS for Internet Access in Windows 2000 http://support.microsoft.com/?id=300202&FR=1

    323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
    (How to configure a forwarder):
    http://support.microsoft.com/d/id?=323380

    Active Directory communication fails on multihomed domain controllers http://support.microsoft.com/kb/272294

    <==*** Some additional reading ***==>
    More links to read up and understand what is going on:

    292822 - Name Resolution and Connectivity Issues on Windows 2000 Domain
    Controller with Routing and Remote Access and DNS Insta {DNS and RRAS and
    unwanted IPs registering]:
    http://support.microsoft.com/?id=292822

    Active Directory communication fails on multihomed domain controllers http://support.microsoft.com/kb/272294

    246804 - How to enable or disable DNS updates in Windows 2000 and in Windows
    Server 2003
    http://support.microsoft.com/?id=246804

    295328 - Private Network Interfaces on a Domain Controller Are Registered in
    DNS
    [also shows DnsAvoidRegisterRecords LdapIpAddress to avoid reg sameasparent
    private IP]:
    http://support.microsoft.com/?id=295328

    306602 - How to Optimize the Location of a DC or GC That Resides Outside of
    a Client's
    Site [Includes info LdapIpAddress and GcIpAddress information and the SRV
    mnemonic values]:
    http://support.microsoft.com/?id=306602

    825036 - Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003 (including how-to configure a forwarder): http://support.microsoft.com/default.aspx?scid=kb;en-us;825036

    291382 - Frequently asked questions about Windows 2000 DNS and Windows
    Server 2003 DNS
    http://support.microsoft.com/?id=291382

    296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
    [Registry Entry]:
    http://support.microsoft.com/?id=296379

    Rid Pool Errors and other mutlhomed DC errors, and how to configure a multihomed DC, Ace Fekay, 24 Feb 2006 http://www.ureader.com/message/3244572.aspx

    _________________________ +++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++

    --
    Regards,
    Ace


    This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

    Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
    Microsoft MVP - Directory Services
    Microsoft Certified Trainer

    Infinite Diversities in Infinite Combinations

    Having difficulty reading or finding responses to your post?
    Instead of the website you're using, try using OEx (Outlook Express
    or any other newsreader), and configure a news account, pointing to
    news.microsoft.com. Anonymous access. It's free - no username or password
    required nor do you need a Newsgroup Usenet account with your ISP. It
    connects directly to the Microsoft Public Newsgroups. OEx allows you
    o easily find, track threads, cross-post, sort by date, poster's name,
    watched threads or subject. It's easy:

    How to Configure OEx for Internet News
    http://support.microsoft.com/?id=171164


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
    Saturday, September 12, 2009 8:25 PM

All replies

  • Hello,

    you have to use the existing domain DNS server 192.168.16.2 on the NIC and not the other ones, i assume the ISPs DNS server or some external one. Remove them from the NIC complete.
    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, September 10, 2009 1:00 PM
  • The DNS server IP address should be configured on the Forwarders tab of your DNS Server Properties dialog box (DNS Management console) - not on the DNS tab of Advanced TCP/IP Settings of the network adapter Properties dialog box on any of the computers that are members of the AD domain (including domain controllers).

    As Meinolf has pointed out, the server you are trying to promote (as well as the current domain controller) should be pointing to the IP address of the AD-integrated DNS server (i.e. your current DC) in their IP configuration...

    hth
    Marcin

    Thursday, September 10, 2009 1:11 PM
  • Hello,

    Thanks for the quck response.

    I tried this but the same error still comes up (without the ISP IP)

    I looked at the DC and opened the DNS property. I run the test on the monitor tab and it failed. All clients are OK to access the server and internet. Any idea if this could be the root of the problem? And if yes how to fix it?


    Kind Regards


    Richard
    Thursday, September 10, 2009 1:12 PM
  • Wait... From his description, 192.168.16.2 is the IP of the DC that he's trying to bring up into the existing domain.  If that's correct, you'll need to also include the IP address of the exiting DC in the Domain so that it can do DNS lookups. 

    Thursday, September 10, 2009 1:18 PM
  • Richard,

    Make sure that the DC points to itself as its only DNS server. Then stop and start its Netlogon service.

    Afterwards, verify that _ldap._tcp.dc._msdcs.bridgelimited.local contains the appropriate SRV record (this should be a record containing a fully qualified domain name of the DC). If not, post the output of :
    - IPCONFIG /ALL from the DC and the server you are trying to promote to a DC
    - DCDIAG /c /v from the DC

    hth
    Marcin
    Thursday, September 10, 2009 1:18 PM
  • Hello,

    as Marcin said the ISPs DNS server should not be used on any NIC in the domain. Please post an unedited ipconfig /all from the DC so we cna check your settings to exclude this as a problem.
    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, September 10, 2009 1:22 PM
  • Thanks for your comment.

    192.168.16.2 is the existing DC The new one is 192.168.16.3

    Kind Regards


    Richard
    Thursday, September 10, 2009 1:35 PM
  • Hello,

    Thanks for your reply.

    The IPCONFIG is

    Windows IP Configuration

     

       Host Name . . . . . . . . . . . . : bridgeserver

       Primary Dns Suffix  . . . . . . . : BridgeLimited.local

       Node Type . . . . . . . . . . . . : Unknown

       IP Routing Enabled. . . . . . . . : Yes

       WINS Proxy Enabled. . . . . . . . : Yes

       DNS Suffix Search List. . . . . . : BridgeLimited.local

     

    Ethernet adapter Hamachi:

     

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Hamachi Network Interface

       Physical Address. . . . . . . . . : 00-23-C3-74-D5-2D

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : No

       IP Address. . . . . . . . . . . . : 5.116.213.45

       Subnet Mask . . . . . . . . . . . : 255.0.0.0

       Default Gateway . . . . . . . . . :

       DHCP Server . . . . . . . . . . . : 5.0.0.1

       Lease Obtained. . . . . . . . . . : 10 September 2009 14:37:36

       Lease Expires . . . . . . . . . . : 10 September 2009 14:41:51

     

    Ethernet adapter Internet Connection:

     

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC #2

       Physical Address. . . . . . . . . : 00-C0-DF-13-0B-F6

       DHCP Enabled. . . . . . . . . . . : No

       IP Address. . . . . . . . . . . . : 192.168.16.13

       Subnet Mask . . . . . . . . . . . : 255.255.255.0

       Default Gateway . . . . . . . . . : 192.168.16.9

       DNS Servers . . . . . . . . . . . : 192.168.16.2

       NetBIOS over Tcpip. . . . . . . . : Disabled

     

    Ethernet adapter Server Local Area Connection:

     

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC

       Physical Address. . . . . . . . . : 00-C0-DF-13-0B-F5

       DHCP Enabled. . . . . . . . . . . : No

       IP Address. . . . . . . . . . . . : 192.168.16.2

       Subnet Mask . . . . . . . . . . . : 255.255.255.0

       Default Gateway . . . . . . . . . :

       DNS Servers . . . . . . . . . . . : 192.168.16.2

       Primary WINS Server . . . . . . . : 192.168.16.2



    The DCDIAG is not recognised - server is 2003 R2


    Kind Regards

    Richard

    Thursday, September 10, 2009 1:43 PM
  • Hello,

    Thanks for your reply.

    The IPCONFIG is

    Windows IP Configuration

     

       Host Name . . . . . . . . . . . . : bridgeserver

       Primary Dns Suffix  . . . . . . . : BridgeLimited.local

       Node Type . . . . . . . . . . . . : Unknown

       IP Routing Enabled. . . . . . . . : Yes

       WINS Proxy Enabled. . . . . . . . : Yes

       DNS Suffix Search List. . . . . . : BridgeLimited.local

     

    Ethernet adapter Hamachi:

     

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Hamachi Network Interface

       Physical Address. . . . . . . . . : 00-23-C3-74-D5-2D

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : No

       IP Address. . . . . . . . . . . . : 5.116.213.45

       Subnet Mask . . . . . . . . . . . : 255.0.0.0

       Default Gateway . . . . . . . . . :

       DHCP Server . . . . . . . . . . . : 5.0.0.1

       Lease Obtained. . . . . . . . . . : 10 September 2009 14:37:36

       Lease Expires . . . . . . . . . . : 10 September 2009 14:41:51

     

    Ethernet adapter Internet Connection:

     

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC #2

       Physical Address. . . . . . . . . : 00-C0-DF-13-0B-F6

       DHCP Enabled. . . . . . . . . . . : No

       IP Address. . . . . . . . . . . . : 192.168.16.13

       Subnet Mask . . . . . . . . . . . : 255.255.255.0

       Default Gateway . . . . . . . . . : 192.168.16.9

       DNS Servers . . . . . . . . . . . : 192.168.16.2

       NetBIOS over Tcpip. . . . . . . . : Disabled

     

    Ethernet adapter Server Local Area Connection:

     

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC

       Physical Address. . . . . . . . . : 00-C0-DF-13-0B-F5

       DHCP Enabled. . . . . . . . . . . : No

       IP Address. . . . . . . . . . . . : 192.168.16.2

       Subnet Mask . . . . . . . . . . . : 255.255.255.0

       Default Gateway . . . . . . . . . :

       DNS Servers . . . . . . . . . . . : 192.168.16.2

       Primary WINS Server . . . . . . . : 192.168.16.2


    Kind Regards

    Richard

    Thursday, September 10, 2009 1:43 PM
  • Hello,

    How do I verify that _ldap._tcp.dc._msdcs.bridgelimited.local contains the appropriate SRV record please?

    Kind Regards


    Richard
    Thursday, September 10, 2009 1:46 PM
  • Hello,

    you have choosen a not optimal setup for the server. Having more then one NIC doesn't mean to use all with different ip addresses. Use either x.x.x.3 or x.x.x.2.

    Also the server is connected to the internet directly, anybody in the world can try to hack it. Is the server SBS version from windows? You should avoid this kind of configuration and place a router in the internet and connect a switch to the router, so you have an internal network with 192.168.x.x and the router as gateway to the internet.

    Also a DC should never run with RRAS enabled, if you need remote access use a member server to install this role.

    To run dcdiag you have to install the support\tools\suptools.msi from the 2003 installation disk, in 2008 it is included.
    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, September 10, 2009 1:49 PM
  • Hello,

    Thanks for your input. Much appreciated. Risking to sound stupid, can I just ask for your help again please.

    Yes I have two NIC's in the server - one going to the internal network (192.168.16.2) and the other to the router (x.x.x.13) for internet access. I thought this firewalls the two segments?

    I used VPN, but it stopped working a long time ago. Still can not figure out why. This is not important at the moment, but trying to get the new server to take over is - the old one is falling to bits.

    Kind Regards

    Richard
    Thursday, September 10, 2009 3:24 PM
  • The system you are using to separate two segments is your domain controller. Compromising it will essentially render your entire domain vulnerable.

    Set up a separate, hardware-based device to function as firewall/router (as Meinolf has advised) or install ISA on a dual homed Windows Server and use it instead...

    hth
    Marcin

    Thursday, September 10, 2009 3:39 PM
  • Hello,

    thanks for your help. Am I right in thinking dual horned means two NIC's, one to the router (internet) and the other to the internal network, which is what I have with ISA installed. Can you please let me know?

    Kind Regards

    Richard
    Thursday, September 10, 2009 3:47 PM
  • Yes - the term "dual-homed" designates a system with two network interfaces...
    If you have a separate ISA server, I don't see a point of having a dual-homed DC...

    hth
    Marcin

    Thursday, September 10, 2009 3:57 PM
  • Thanks!!!!


    The ISA is installed on the DC. I have only got one server at the moment. Desperate to join the new one, so I can give the old one a bit of TLC.


    Kind Regards

    Richard
    Thursday, September 10, 2009 4:15 PM
  • Managed to get the DCDIAG

    Here goes (I know my harddisk is failing - that's why I am desperate to get everything shifted to the new server).


    Domain Controller Diagnosis

    Performing initial setup:
       * Verifying that the local machine bridgeserver, is a DC.
       * Connecting to directory service on server bridgeserver.
       * Collecting site info.
       * Identifying all servers.
       * Identifying all NC cross-refs.
       * Found 1 DC(s). Testing 1 of them.
       Done gathering initial info.

    Doing initial required tests
      
       Testing server: Default-First-Site-Name\BRIDGESERVER
          Starting test: Connectivity
             * Active Directory LDAP Services Check
             * Active Directory RPC Services Check
             ......................... BRIDGESERVER passed test Connectivity

    Doing primary tests
      
       Testing server: Default-First-Site-Name\BRIDGESERVER
          Starting test: Replications
             * Replications Check
             * Replication Latency Check
                DC=ForestDnsZones,DC=BridgeLimited,DC=local
                   Latency information for 2 entries in the vector were ignored.
                      2 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC). 
                DC=DomainDnsZones,DC=BridgeLimited,DC=local
                   Latency information for 2 entries in the vector were ignored.
                      2 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC). 
                CN=Schema,CN=Configuration,DC=BridgeLimited,DC=local
                   Latency information for 2 entries in the vector were ignored.
                      2 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC). 
                CN=Configuration,DC=BridgeLimited,DC=local
                   Latency information for 2 entries in the vector were ignored.
                      2 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC). 
                DC=BridgeLimited,DC=local
                   Latency information for 2 entries in the vector were ignored.
                      2 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC). 
             * Replication Site Latency Check
             ......................... BRIDGESERVER passed test Replications
          Starting test: Topology
             * Configuration Topology Integrity Check
             * Analyzing the connection topology for DC=ForestDnsZones,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the connection topology for DC=DomainDnsZones,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the connection topology for CN=Schema,CN=Configuration,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the connection topology for CN=Configuration,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the connection topology for DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             ......................... BRIDGESERVER passed test Topology
          Starting test: CutoffServers
             * Configuration Topology Aliveness Check
             * Analyzing the alive system replication topology for DC=ForestDnsZones,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the alive system replication topology for DC=DomainDnsZones,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the alive system replication topology for CN=Schema,CN=Configuration,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the alive system replication topology for CN=Configuration,DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             * Analyzing the alive system replication topology for DC=BridgeLimited,DC=local.
             * Performing upstream (of target) analysis.
             * Performing downstream (of target) analysis.
             ......................... BRIDGESERVER passed test CutoffServers
          Starting test: NCSecDesc
             * Security Permissions Check for
               DC=ForestDnsZones,DC=BridgeLimited,DC=local
                (NDNC,Version 2)
             * Security Permissions Check for
               DC=DomainDnsZones,DC=BridgeLimited,DC=local
                (NDNC,Version 2)
             * Security Permissions Check for
               CN=Schema,CN=Configuration,DC=BridgeLimited,DC=local
                (Schema,Version 2)
             * Security Permissions Check for
               CN=Configuration,DC=BridgeLimited,DC=local
                (Configuration,Version 2)
             * Security Permissions Check for
               DC=BridgeLimited,DC=local
                (Domain,Version 2)
             ......................... BRIDGESERVER passed test NCSecDesc
          Starting test: NetLogons
             * Network Logons Privileges Check
             ......................... BRIDGESERVER passed test NetLogons
          Starting test: Advertising
             The DC BRIDGESERVER is advertising itself as a DC and having a DS.
             The DC BRIDGESERVER is advertising as an LDAP server
             The DC BRIDGESERVER is advertising as having a writeable directory
             The DC BRIDGESERVER is advertising as a Key Distribution Center
             The DC BRIDGESERVER is advertising as a time server
             The DS BRIDGESERVER is advertising as a GC.
             ......................... BRIDGESERVER passed test Advertising
          Starting test: KnowsOfRoleHolders
             Role Schema Owner = CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local
             Role Domain Owner = CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local
             Role PDC Owner = CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local
             Role Rid Owner = CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local
             Role Infrastructure Update Owner = CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local
             ......................... BRIDGESERVER passed test KnowsOfRoleHolders
          Starting test: RidManager
             * Available RID Pool for the Domain is 2609 to 1073741823
             * bridgeserver.BridgeLimited.local is the RID Master
             * DsBind with RID Master was successful
             * rIDAllocationPool is 2109 to 2608
             * rIDPreviousAllocationPool is 2109 to 2608
             * rIDNextRID: 2121
             ......................... BRIDGESERVER passed test RidManager
          Starting test: MachineAccount
             * SPN found :LDAP/bridgeserver.BridgeLimited.local/BridgeLimited.local
             * SPN found :LDAP/bridgeserver.BridgeLimited.local
             * SPN found :LDAP/BRIDGESERVER
             * SPN found :LDAP/bridgeserver.BridgeLimited.local/BRIDGELIMITED
             * SPN found :LDAP/96d36b0b-a148-4c2f-b3d3-8c2ac83fcaf9._msdcs.BridgeLimited.local
             * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/96d36b0b-a148-4c2f-b3d3-8c2ac83fcaf9/BridgeLimited.local
             * SPN found :HOST/bridgeserver.BridgeLimited.local/BridgeLimited.local
             * SPN found :HOST/bridgeserver.BridgeLimited.local
             * SPN found :HOST/BRIDGESERVER
             * SPN found :HOST/bridgeserver.BridgeLimited.local/BRIDGELIMITED
             * SPN found :GC/bridgeserver.BridgeLimited.local/BridgeLimited.local
             ......................... BRIDGESERVER passed test MachineAccount
          Starting test: Services
             * Checking Service: Dnscache
             * Checking Service: NtFrs
             * Checking Service: IsmServ
                IsmServ Service is stopped on [BRIDGESERVER]
             * Checking Service: kdc
             * Checking Service: SamSs
             * Checking Service: LanmanServer
             * Checking Service: LanmanWorkstation
             * Checking Service: RpcSs
             * Checking Service: w32time
             * Checking Service: NETLOGON
             ......................... BRIDGESERVER failed test Services
          Starting test: OutboundSecureChannels
             * The Outbound Secure Channels test
             ** Did not run Outbound Secure Channels test
             because /testdomain: was not entered
             ......................... BRIDGESERVER passed test OutboundSecureChannels
          Starting test: ObjectsReplicated
             BRIDGESERVER is in domain DC=BridgeLimited,DC=local
             Checking for CN=BRIDGESERVER,OU=Domain Controllers,DC=BridgeLimited,DC=local in domain DC=BridgeLimited,DC=local on 1 servers
                Object is up-to-date on all servers.
             Checking for CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local in domain CN=Configuration,DC=BridgeLimited,DC=local on 1 servers
                Object is up-to-date on all servers.
             ......................... BRIDGESERVER passed test ObjectsReplicated
          Starting test: frssysvol
             * The File Replication Service SYSVOL ready test
             File Replication Service's SYSVOL is ready
             ......................... BRIDGESERVER passed test frssysvol
          Starting test: frsevent
             * The File Replication Service Event log test
             ......................... BRIDGESERVER passed test frsevent
          Starting test: kccevent
             * The KCC Event log test
             Found no KCC errors in Directory Service Event log in the last 15 minutes.
             ......................... BRIDGESERVER passed test kccevent
          Starting test: systemlog
             * The System Event log test
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:47:27
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:47:41
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:47:55
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:48:09
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:48:23
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:48:38
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:48:52
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:49:06
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:49:20
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:49:54
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:50:08
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:50:22
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:51:33
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:51:53
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:52:07
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:52:21
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:52:35
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:52:49
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:53:03
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:53:17
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:53:31
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   16:53:45
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:12:23
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:12:37
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:12:51
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:13:05
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:13:19
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:13:33
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:13:47
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:14:01
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:14:15
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:15:24
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:15:38
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:15:53
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:16:07
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:16:21
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:16:35
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:16:49
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:17:03
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             An Error Event occured.  EventID: 0xC0040075
                Time Generated: 09/10/2009   17:17:17
                Event String: The driver for device \Device\Scsi\hpt3xx1

    detected a port timeout due to prolonged

    inactivity. All associated busses were reset in

    an effort to clear the condition.
             ......................... BRIDGESERVER failed test systemlog
          Starting test: VerifyReplicas
             ......................... BRIDGESERVER passed test VerifyReplicas
          Starting test: VerifyReferences
             The system object reference (serverReference)

             CN=BRIDGESERVER,OU=Domain Controllers,DC=BridgeLimited,DC=local and

             backlink on

             CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local

             are correct.
             The system object reference (frsComputerReferenceBL)

             CN=BRIDGESERVER,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=BridgeLimited,DC=local

             and backlink on

             CN=BRIDGESERVER,OU=Domain Controllers,DC=BridgeLimited,DC=local are

             correct.
             The system object reference (serverReferenceBL)

             CN=BRIDGESERVER,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=BridgeLimited,DC=local

             and backlink on

             CN=NTDS Settings,CN=BRIDGESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BridgeLimited,DC=local

             are correct.
             ......................... BRIDGESERVER passed test VerifyReferences
          Starting test: VerifyEnterpriseReferences
             ......................... BRIDGESERVER passed test VerifyEnterpriseReferences
      
       Running partition tests on : ForestDnsZones
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
      
       Running partition tests on : DomainDnsZones
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
      
       Running partition tests on : Schema
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
      
       Running partition tests on : Configuration
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
      
       Running partition tests on : BridgeLimited
          Starting test: CrossRefValidation
             ......................... BridgeLimited passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... BridgeLimited passed test CheckSDRefDom
      
       Running enterprise tests on : BridgeLimited.local
          Starting test: Intersite
             Skipping site Default-First-Site-Name, this site is outside the scope

             provided by the command line arguments provided.
             ......................... BridgeLimited.local passed test Intersite
          Starting test: FsmoCheck
             GC Name: \\bridgeserver.BridgeLimited.local
             Locator Flags: 0xe00003fd
             PDC Name: \\bridgeserver.BridgeLimited.local
             Locator Flags: 0xe00003fd
             Time Server Name: \\bridgeserver.BridgeLimited.local
             Locator Flags: 0xe00003fd
             Preferred Time Server Name: \\bridgeserver.BridgeLimited.local
             Locator Flags: 0xe00003fd
             KDC Name: \\bridgeserver.BridgeLimited.local
             Locator Flags: 0xe00003fd
             ......................... BridgeLimited.local passed test FsmoCheck



    The only thing I can see (other then the HDD) is the

    IsmServ Service is stopped on [BRIDGESERVER]


    Hope you can help. Pretty please.


    Kind Regards


    Richard

    Thursday, September 10, 2009 4:50 PM
  • Hi,

    On the Domain controller do the following things

    Nslookup and see weather it is pointing to your Local DNS server (FQDN) and IP.

    Result must come in this way
    Default:DC.bridgelimited.local
    Address: 196.168.16.2

    as said if you are using public DNS server IP as secondary try removing it and use it in forwaders.

    On the TCP/IP connections giv ethe primary DNS server Ip as the Local domain controller IP since DNS service is hosted on it.

    Try restating DNS server service and check. if not than ping me back i'll provide the procedure to manually update DNS SRV records of domain controller in your DNS server.

    • Proposed as answer by leung_ms Friday, April 12, 2013 8:42 AM
    • Unproposed as answer by leung_ms Friday, April 12, 2013 8:43 AM
    Thursday, September 10, 2009 5:59 PM
  • Thanks,

    I think the restarting of the DNS has done the trick. Much appreciated.


    Kind Regards

    Richard
    • Proposed as answer by Hari Bylapudi Thursday, September 10, 2009 7:30 PM
    Thursday, September 10, 2009 6:44 PM
  • Hello again,

    Got further this time, but....

    running dcpromo on the new server (2008), everything looks OK until I get to the Additional Domain Controller Options page; I can not unckeck the DNS server box (greyed out). Additional information is:


    The DNS Server service is already installed on this server.

    There is currently 1 DNS server that is registered as an authoritative name server for this domain.

    A domain controller running Windows Server 2008 could not be located in this domain. To install a read-only domain controller, the domain must have a domain controller running Windows Server 2008.

    You cannot install a read-only domain controller at this time. You must first run "adprep /rodcprep" from a command window on any computer in this forest. The Adprep utility is available on the Windows Server 2008 installation media in the \sources\adprep folder.

    Carried on to see what happens; and it eventually comes up with

    A delegation for this DNS server cannot be created because the authoritative parent zone cannot be found or it does not run Windows DNS server. To enable reliable DNS name resolution from outside the domain BridgeLimited.local, you should create a delegation to this DNS server manually in the parent zone.


    I continued and it came up with

    The operation failed because:
    Active Directory Domain Services coul not install
    The replication operation failed to allocate memory

    Thanks in advance for your help

    Kind Regards


    Richard

    Thursday, September 10, 2009 7:52 PM
  • Hello,

    ISA should not run on the DC, use a member server with 2 NICs as described by Marcin before. Basically a DC should only do it's basic job, AD, DNS, GC and maybe DHCP, if no member server can do this job.

    All other applications and services should run on member servers. Keep in mind the DCs are the heart of your domain, if they are compromised full access to the network is possible.

    Whenever it is possible do not use a DC to separate networks, ISA, switches with VPN or routers are the better solution.

    Are you able to start the InterSite messaging service? If not which error is shown and listed in the event viewer?
    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, September 11, 2009 7:21 AM
  • Hello,

    if the DNS server role is installed the DNS messages are expected.

    If you don't run adprep /rodcprep you are not able to install a RODC, which also requires one 2008 RWDC in the domain, so expected.

    The delgation message is informational.

    Please post an unedited ipconfig /all from the 2008 and the exisitng DC. Also i would uninstall the DNS server role before promoting it.
    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
    Friday, September 11, 2009 7:32 AM
  • Hello,

    I have removed the DNS server role and unchecked the DNS server check box in the additional domain controller options during dcpromo; same error still comes up:

    The operation failed because:
    Active Directory Domain Services coul not install
    The replication operation failed to allocate memory



    The 2008 IPconfig is


    Windows IP Configuration

       Host Name . . . . . . . . . . . . : BRIDGESERVER2
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Broadcast
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Local Area Connection 2:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek RTL8168/8111 Family PCI-E Gigabit Ethernet NIC (NDIS 6.0) #2
       Physical Address. . . . . . . . . : 00-50-8D-97-FE-0B
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::5c46:ec1:d2e4:ef70%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.16.3(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.16.2
       DNS Servers . . . . . . . . . . . : 192.168.16.2
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Local Area Connection:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek RTL8168/8111 Family PCI-E Gigabit Ethernet NIC (NDIS 6.0)
       Physical Address. . . . . . . . . : 00-50-8D-97-FE-0C
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 8:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{E9E39BED-A37F-42E1-858D-51BD199359B6}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 9:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{F47BB09B-EA28-43A9-8700-9D6FAB04C414}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 11:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 02-00-54-55-4E-01
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes


    and the excisting server is


      Host Name . . . . . . . . . . . . : bridgeserver

       Primary Dns Suffix  . . . . . . . : BridgeLimited.local

       Node Type . . . . . . . . . . . . : Unknown

       IP Routing Enabled. . . . . . . . : Yes

       WINS Proxy Enabled. . . . . . . . : Yes

       DNS Suffix Search List. . . . . . : BridgeLimited.local

     

    Ethernet adapter Hamachi:

     

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Hamachi Network Interface

       Physical Address. . . . . . . . . : 00-23-C3-74-D5-2D

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : No

       IP Address. . . . . . . . . . . . : 5.116.213.45

       Subnet Mask . . . . . . . . . . . : 255.0.0.0

       Default Gateway . . . . . . . . . :

       DHCP Server . . . . . . . . . . . : 5.0.0.1

       Lease Obtained. . . . . . . . . . : 10 September 2009 14:37:36

       Lease Expires . . . . . . . . . . : 10 September 2009 14:41:51

     

    Ethernet adapter Internet Connection:

     

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC #2

       Physical Address. . . . . . . . . : 00-C0-DF-13-0B-F6

       DHCP Enabled. . . . . . . . . . . : No

       IP Address. . . . . . . . . . . . : 192.168.16.13

       Subnet Mask . . . . . . . . . . . : 255.255.255.0

       Default Gateway . . . . . . . . . : 192.168.16.9

       DNS Servers . . . . . . . . . . . : 192.168.16.2

       NetBIOS over Tcpip. . . . . . . . : Disabled

     

    Ethernet adapter Server Local Area Connection:

     

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC

       Physical Address. . . . . . . . . : 00-C0-DF-13-0B-F5

       DHCP Enabled. . . . . . . . . . . : No

       IP Address. . . . . . . . . . . . : 192.168.16.2

       Subnet Mask . . . . . . . . . . . : 255.255.255.0

       Default Gateway . . . . . . . . . :

       DNS Servers . . . . . . . . . . . : 192.168.16.2

       Primary WINS Server . . . . . . . : 192.168.16.2


    Thanks again for your help


    Kind Regards

    Richard

    Friday, September 11, 2009 1:08 PM
  • Thanks for the advise

    I only had one server running, hence this is another reason why I desperately want to get the second server up and running to take over, then I can use the old server (after a bit of hardware replacement) to take on the member role. Just pre-emptying this, should I move the DNS role over at this stage or delegate it later?

    Intersite messaging was disabled. I enabled it and started manually. Runs OK.

    Run dcpromo again on the 2008, came up with the same error (The replication operation failed to allocate memory).

    Kind Regarrds

    Richard
    Friday, September 11, 2009 1:49 PM
  • Hello,

    you have still the ip configuration with 2 ip addresses for the LAN and an external, please follow the advises above and reconfigure the server ip addressing.


    Again, MULTIHOMING Domain controllers is not recommended, it always results in multiple problems.
    -----------------------------------------------------------------------
    1. Domain Controllers should not be multi-homed
    2. Being a VPN Server and even simply running RRAS makes it multi-homed.
    3. DNS,..even just all by itself, is better on a single homed machine.
    4. Domain Controllers with the PDF Role are automatically Domain Master
    Browser. Master Browsers should not be multi-homed

    272294 - Active Directory Communication Fails on Multihomed Domain Controllers http://support.microsoft.com/default.aspx?scid=kb;en-us;272294

    191611 - Symptoms of Multihomed Browsers
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;191611

    Phillip Windell
    www.wandtv.com

    The views expressed, are my own and not those of my employer, or Microsoft, or anyone else associated with me, including my cats. -----------------------------------------------------


    See also:

    Multihomed DCs, DNS, RRAS servers.
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++
    Below are the manual steps in more detail, which I had outlined in the above
    paragraph:

    Honestly, multi-homed DCs are not recommended because of the associated issues that can occur, as you've encountered. We usually recommend purchasing an inexpensive Linksys, DLink, etc, Cable/DSL router to perform NAT for you, take out the extra NIC off the DC, but still let the DC handle DHCP (and not the router).

    Little background on AD and DNS:
    First, just to get this out of the way, if you have your ISP's DNS addresses
    in your IP configuration (DCs and clients), they need to be REMOVED.

    If the ISP's DNS is in there, this will cause additional problems.

    Also, AD registers certain records in DNS in the form of SRV records that signify AD's resource and service locations. When there are multiple NICs, each NIC registers. IF a client, or another DC queries DNS for this DC, it may get the wrong record. One factor controlling this is Round Robin. If a DC or client on another subnet that the DC is not configured on queries for it, Round Robin will kick in offering one or the other. If the wrong one gets offered, it may not have a route to it. On the other hand, Subnetmask Priortization will ensure a querying client will get an IP that corresponds to the subnet it's on, which will work. To insure everything works, stick with one NIC.

    Since this DC is multi-homed, it requires additional configuration to prevent the public interface addresses from being registered in DNS. This creates a problem for internal clients locating AD to authenticate and find other services and resources such as the Global Catalog, file sharing and the SYSVOL DFS share and can cause GPO errors with Userenv 1000 events to be logged, authenticating to shares and printers, logging on takes forever, among numerous other issues.

    But if you like, there are some registry changes to eliminate the registration of the external NIC. Here's the whole list of manual steps to follow.

    But believe me, it's much easier to just get a separate NAT device or multihome a non-DC then having to alter the DC. - Good luck!

    1. Insure that all the NICS only point to your internal DNS server(s) only and none others, such as your ISP's DNS servers' IP addresses.

    2. In Network & Dialup properties, Advanced Menu item, Advanced Settings, move the internal NIC (the network that AD is on) to the top of the binding order (top of the list).

    3. Disable the ability for the outer NIC to register. The procedure, as
    mentioned, involves identifying the outer NIC's GUID number. This link will
    show you how:
    246804 - How to Enable-Disable Windows 2000 Dynamic DNS Registrations (per
    NIC too):
    http://support.microsoft.com/?id=246804

    4. Disable NetBIOS on the outside NIC. That is performed by choosing to
    disable NetBIOS in IP Properties, Advanced, and you will find that under the
    "WINS" tab. You may want to look at step #3 in the article to show you how
    to disable NetBIOS on the RRAS interfaces if this is a RRAS server.
    296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
    [Registry Entry]:
    http://support.microsoft.com/?id=296379

    Note: A standard Windows service, called the "Browser service", provides the list of machines, workgroup and domain names that you see in "My Network Places" (or the legacy term "Network Neighborhood"). The Browser service relies on the NetBIOS service. One major requirement of NetBIOS service is a machine can only have one name to one IP address. It's sort of a fingerprint. You can't have two brothers named Darrell. A multihomed machine will cause duplicate name errors on itself because Windows sees itself with the same name in the Browse List (My Network Places), but with different IPs. You can only have one, hence the error generated.

    5. Disable the "File and Print Service" and disable the "MS Client Service" on the outer NIC. That is done in NIC properties by unchecking the respective service under the general properties page. If you need these services on the outside NIC (which is unlikely), which allow other machines to connect to your machine for accessing resource on your machine (shared folders, printers, etc.), then you will probably need to keep them enabled.

    6. Uncheck "Register this connection" under IP properties, Advanced settings, "DNS" tab.

    7. Delete the outer NIC IP address, disable Netlogon registration, and manually create the required records

    a. In DNS under the zone name, (your DNS domain name), delete the outer NIC's IP references for the "LdapIpAddress". If this is a GC, you will need to delete the GC IP record as well (the "GcIpAddress"). To do that, in the DNS console, under the zone name, you will see the _msdcs folder. Under that, you will see the _gc folder. To the right, you will see the IP address referencing the GC address. That is called the GcIpAddress. Delete the IP addresses referencing the outer NIC.

    i. To stop these two records from registering that information,
    use the steps provided in the links below:
    Private Network Interfaces on a Domain Controller Are Registered in
    DNShttp://support.microsoft.com/?id=295328

    ii. The one section of the article that disables these records is done with this registry entry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
    (Create this Multi-String Value under it):
    Registry value: DnsAvoidRegisterRecords
    Data type: REG_MULTI_SZ
    Values: LdapIpAddress
    GcIpAddress

    iii. Here is more information on these and other Netlogon Service records:

    Restrict the DNS SRV resource records updated by the Netlogon service

    [including GC]:

    http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windowsserver2003/proddocs/standard/sag_dns_pro_no_rr_in_ad.asp

    b. Then you will need to manually create these two records in DNS with the IP addresses that you need for the DC. To create the

    LdapIpAddress, create a new host under the domain, but leave the "hostname"
    field blank, and provide the internal IP of the DC, which results in a
    record that looks like:
    (same as parent) A 192.168.5.200 (192.168.5.200 is used for illustrative
    purposes)

    i. You need to also manually create the GcIpAddress as well, if this is a GC. That would be under the _msdcs._gc SRV record under the zone. It is created in the same fashion as the LdapIpAddress mentioned above.

    8. In the DNS console, right click the server name, choose properties, then under the "Interfaces" tab, force it only to listen to the internal NIC's IP address, and not the IP address of the outer NIC.

    9. Since this is also a DNS server, the IPs from all NICs will register,
    even if you tell it not to in the NIC properties. See this to show you how
    to stop that behavior (this procedure is for Windows 2000, but will also
    work for Windows 2003):
    275554 - The Host's A Record Is Registered in DNS After You Choose Not to
    Register the Connection's Address:
    http://support.microsoft.com/?id=275554

    10. If you haven't done so, configure a forwarder. You can use 4.2.2.2 if
    not sure which DNS to forward to until you've got the DNS address of your
    ISP.
    How to set a forwarder? Good question. Depending on your operating
    system,choose one of the following articles:

    300202 - HOW TO: Configure DNS for Internet Access in Windows 2000 http://support.microsoft.com/?id=300202&FR=1

    323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
    (How to configure a forwarder):
    http://support.microsoft.com/d/id?=323380

    Active Directory communication fails on multihomed domain controllers http://support.microsoft.com/kb/272294

    <==*** Some additional reading ***==>
    More links to read up and understand what is going on:

    292822 - Name Resolution and Connectivity Issues on Windows 2000 Domain
    Controller with Routing and Remote Access and DNS Insta {DNS and RRAS and
    unwanted IPs registering]:
    http://support.microsoft.com/?id=292822

    Active Directory communication fails on multihomed domain controllers http://support.microsoft.com/kb/272294

    246804 - How to enable or disable DNS updates in Windows 2000 and in Windows
    Server 2003
    http://support.microsoft.com/?id=246804

    295328 - Private Network Interfaces on a Domain Controller Are Registered in
    DNS
    [also shows DnsAvoidRegisterRecords LdapIpAddress to avoid reg sameasparent
    private IP]:
    http://support.microsoft.com/?id=295328

    306602 - How to Optimize the Location of a DC or GC That Resides Outside of
    a Client's
    Site [Includes info LdapIpAddress and GcIpAddress information and the SRV
    mnemonic values]:
    http://support.microsoft.com/?id=306602

    825036 - Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003 (including how-to configure a forwarder): http://support.microsoft.com/default.aspx?scid=kb;en-us;825036

    291382 - Frequently asked questions about Windows 2000 DNS and Windows
    Server 2003 DNS
    http://support.microsoft.com/?id=291382

    296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
    [Registry Entry]:
    http://support.microsoft.com/?id=296379

    Rid Pool Errors and other mutlhomed DC errors, and how to configure a multihomed DC, Ace Fekay, 24 Feb 2006 http://www.ureader.com/message/3244572.aspx

    _________________________ +++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++

    --
    Regards,
    Ace


    This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

    Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
    Microsoft MVP - Directory Services
    Microsoft Certified Trainer

    Infinite Diversities in Infinite Combinations

    Having difficulty reading or finding responses to your post?
    Instead of the website you're using, try using OEx (Outlook Express
    or any other newsreader), and configure a news account, pointing to
    news.microsoft.com. Anonymous access. It's free - no username or password
    required nor do you need a Newsgroup Usenet account with your ISP. It
    connects directly to the Microsoft Public Newsgroups. OEx allows you
    o easily find, track threads, cross-post, sort by date, poster's name,
    watched threads or subject. It's easy:

    How to Configure OEx for Internet News
    http://support.microsoft.com/?id=171164


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
    Saturday, September 12, 2009 8:25 PM
  • HA YES THE ALL IN ONE BOX CONFIG........SBS,ESB, ETC................

    ALL EGGS IN ONE BASKET? NOT THE BEST PRACTICE!!!!!!!

    Setup Active Directory and DNS in one server with one NIC!!!!!!!!!!!!  Use  DHCP from the router (modify its config by using the local DNS from the DC ). You will also need to modify your DC to forward to a public DNS (such as your ISP) so that it can resolve foreign URLs for your AD machines.  Your network would look like this.

       Internet
              |
          public IP
           router
         192.168.16.9       
                |
               DC
         192.168.16.2  DNS 192.168.16.2   GATE  192.168.16.9
                 |
            clients
         192.168.16.X  DNS 192.168.16.2   GATE  192.168.1.9
               

    Wednesday, September 16, 2009 2:15 PM
  • MR WEBER,

    BEST PRACTICE FOR DHCP!!!!!!!!!!!!!!!!!!!!!

    It is always better to use a separate DHCP server or divice that is not set up with Active Directory domain services WITH DNS.  

    It seems to me that if you authorize DHCP in a domain controller that configuration will require a lot of babysitting (monitoring resource records, highjacking, etc.).  

     Setup Active Directory and DNS in one server with one NIC!!!!!!!!!!!!  Use  DHCP from the router (modify its config by using the local DNS from the DC ). You will also need to modify your DC to forward to a public DNS (such as your ISP) so that it can resolve foreign URLs for your AD machines.  

    THIS COMES FROM MICROSOFT'S ADVICE......
    CAME TO ME FROM kellyv@microsoft.com.

    A DNS EXPERT!!!!!!!!!!!!!!!!!!!!

                 

    Wednesday, September 16, 2009 2:27 PM
  • Thanks for the advise

    I only had one server running, hence this is another reason why I desperately want to get the second server up and running to take over, then I can use the old server (after a bit of hardware replacement) to take on the member role. Just pre-emptying this, should I move the DNS role over at this stage or delegate it later?

    Intersite messaging was disabled. I enabled it and started manually. Runs OK.

    Run dcpromo again on the 2008, came up with the same error (The replication operation failed to allocate memory).

    Kind Regarrds

    Richard
    Hi! I've been reading through this post and im desperate to try and find out what it was that fixed your issue as i to am recieving the "The replication operation failed to allocate memory" error! Bizarrely i've also got a hard drive crash imminent on our existing 2003 DC.

    I would be incredibly apprechiative if you could help me resolve this issue because i've googled no end and not found any information which has helped me.
    Monday, November 09, 2009 10:33 AM