DNS error 4013

Discussion in 'DNS Server' started by jjbrisbane, Jul 23, 2009.

  1. jjbrisbane

    jjbrisbane Guest

    Hi i am getting the follow error:

    The DNS server is waiting for Active Directory Domain Services (AD DS) to
    signal that the initial synchronization of the directory has been completed.
    The DNS server service cannot start until the initial synchronization is
    complete because critical DNS data might not yet be replicated onto this
    domain controller. If events in the AD DS event log indicate that there is a
    problem with DNS name resolution, consider adding the IP address of another
    DNS server for this domain to the DNS server list in the Internet Protocol
    properties of this computer. This event will be logged every two minutes
    until AD DS has signaled that the initial synchronization has successfully
    completed.

    Some symptons around the network are security server taking long time to log
    on to domain, exchange 2007 email is backing up cause cant connect to edge
    server.

    any ideas how to fix?
    thanks
    jon
     
    jjbrisbane, Jul 23, 2009
    #1
    1. Advertisements

  2. Hello jjbrisbane,

    Let's start with an unedited ipconfig /all from the problem server and your
    DNS server.

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Jul 23, 2009
    #2
    1. Advertisements

  3. jjbrisbane

    jjbrisbane Guest

    its a windows 2008 EBS installation with the 3 servers
    (management/messaging/security)

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : Management
    Primary Dns Suffix . . . . . . . : kenmore.XXX.com.au
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : kenmore.XXX.com.au
    XXX.com.au
    com.au

    Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : HP NC7782 Gigabit Server Adapter
    Physical Address. . . . . . . . . : 00-18-FE-86-67-3E
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv4 Address. . . . . . . . . . . : 192.168.1.2(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.1.1
    DNS Servers . . . . . . . . . . . : 127.0.0.1
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : Messaging
    Primary Dns Suffix . . . . . . . : kenmore.XXX.com.au
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : kenmore.XXX.com.au
    XXX.com.au
    com.au

    Ethernet adapter Local Area Connection 3:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : HP NC7781 Gigabit Server Adapter
    Physical Address. . . . . . . . . : 00-13-21-AE-9F-88
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv4 Address. . . . . . . . . . . : 192.168.1.3(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.1.1
    DNS Servers . . . . . . . . . . . : 192.168.1.2
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : Security
    Primary Dns Suffix . . . . . . . : kenmore.XXX.com.au
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : Yes
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : kenmore.XXX.com.au
    XXX.com.au
    com.au

    PPP adapter TPG:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : TPG
    Physical Address. . . . . . . . . :
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv4 Address. . . . . . . . . . . : XXX.241.216.160(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.255
    Default Gateway . . . . . . . . . : 0.0.0.0
    DNS Servers . . . . . . . . . . . : 203.12.160.35
    203.12.160.36
    NetBIOS over Tcpip. . . . . . . . : Disabled

    Ethernet adapter Local Area Connection 2:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #2
    Physical Address. . . . . . . . . : 00-16-35-59-37-82
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . :
    fe80::3472:dc6e:d2e5:ce86%11(Preferred)
    Default Gateway . . . . . . . . . :
    DHCPv6 IAID . . . . . . . . . . . : 285218357
    DHCPv6 Client DUID. . . . . . . . :
    00-01-00-01-11-8B-60-6B-00-16-35-59-37-78
    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
    fec0:0:0:ffff::2%1
    fec0:0:0:ffff::3%1
    NetBIOS over Tcpip. . . . . . . . : Disabled

    Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
    Physical Address. . . . . . . . . : 00-16-35-59-37-78
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv4 Address. . . . . . . . . . . : 192.168.1.1(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . :
    DNS Servers . . . . . . . . . . . : 192.168.1.2
    192.168.1.3
    NetBIOS over Tcpip. . . . . . . . : Enabled

    thanks for your help
     
    jjbrisbane, Jul 23, 2009
    #3

  4. First recommendation is change the loopback (127.0.0.1) to 192.168.1.2 and 192.168.1.3 (if that server is a DC, if not, don't put it in)
    Second, remove the PPP adapter and those external DNS servers, 203.12.160.35 and 203.12.160.36 from Security, as well as disable IPv6.
    Assuming Messaging is a DC (not a good idea to install Exchange on a DC), set 192.168.1.3 as first DNS, and 192.168.1.2 as second.

    As far as the Edge server (assuming you are talking about Exchange 2007), did you import/export the EdgeSubscription correctly? How about the queues, did you try to set the queues to Retry the queues?

    --
    Ace

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

    Please reply back to the newsgroup or forum to benefit from collaboration among responding engineers, and to help others benefit from your resolution.

    Ace Fekay, MCT, MCSE, MCSA 2003 & 2000, MCSA Messaging
    Microsoft Certified Trainer

    http://twitter.com/acefekay

    For urgent issues, you may want to contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.
     
    Ace Fekay [MCT], Jul 23, 2009
    #4
  5. jjbrisbane

    jjbrisbane Guest

    Thanks Ace, i have made all the changes except i need the ppp adapter cause
    that is my internet connection. i am still experiencing the same issues. I
    have to reboot the messaging computer every 2 hours to clear those messages
    in the queue. the edge subscription is fine. the security server is still
    taking about 8 minutes to log on!!
    any other ideas?
    thanks
    Jon
     
    jjbrisbane, Jul 23, 2009
    #5

  6. It's what's causing the problem. Can you move that PPP to a non-DC and non-Exchange server? How about an inexpensive router to take care of that task?

    Ace
     
    Ace Fekay [MCT], Jul 23, 2009
    #6
  7. Hello jjbrisbane,

    Well, i am a bit late, so Ace already gave you the needed information in
    his excellent way as always. And the only way to solve your problem is to
    change the DNS part with the external addresses and the PPP at least to a
    machine without DC/Exchange installed. Some roles/applications should always
    run on dedicated servers, like AD, Exchange(also not recommended from MS),
    SQL for example.

    http://technet.microsoft.com/en-us/library/aa997407.aspx

    Best regards

    Meinolf Weber
     
    Meinolf Weber [MVP-DS], Jul 23, 2009
    #7
  8. jjbrisbane

    jjbrisbane Guest

    Thanks Guys, but the security server is not the dc the management is the
    primary and the messaging is the secondary. any other way around this cause
    it has been working fine for a month with the setup and now BOOM! the
    security server runs threat management gateway so it is designed to be the
    connection to the internet...
     
    jjbrisbane, Jul 24, 2009
    #8

  9. So let me get this straight. Your DCs are:
    Management (EBS 2008 Server) 192.168.1.2
    Messaging (Windows 2003 replica DC) 192.168.1.3 (with RRAS on it)

    Member servers:
    Security - Acting as the Gateway. (Windows 2008, dual homed with IPv6) 192.168.1.1

    Well, first thing as I mentioned earlier, is Exchange is on the DC. Not a good idea. Causes too many problems. On top of that, RRAS is on the DC. Complicates matters.

    If you cannot move the Exchange role off the DC, especially the RRAS role, which in your case RRAS is probably the cause of the issues with mail flow. Running RRAS on a DC effectively makes it a multihomed DC (more than one NIC and/or IP). In this case, I would suggest to alter the DC's DNS registration behavior in order to straighten it out first, so the proper DNS records for the DC get registered. It takes a few steps including registry entries. Please read through before making any changes to understand the reasons and the implications.

    ==================================================================
    ==================================================================
    Multihomed DCs, DNS, RRAS servers.
    By Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA
    First published: January, 2003, updated July, 2006
    ==============================================

    Multihomed DCs WILL cause numerous issues. It's highly recommended to single home all DCs and use a non-DC for the multihoming purposes. If it is the internet gateway, it is recommended to purchase an inexpensive, or cable/DLS router, or even better, a Cisco or similar firewall to perform the task, which if it is compromised by an internet attacker remotely, can further compromise the rest of the internal network.

    Also if attempting to use ICS on a DC, this further complicates matters with DC functionality, and cannot be fixed with the following steps outlined in this article.

    To explain why will require a 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. I usually see errors (GPOs not working, can't find the domain, RPC issues, etc), when the ISP's DNS servers are listed on a client, DCs and/or member servers, or with multihomed DCs. If you have an ISP's (or some other outside DNS server or even using your router as a DNS server) DNS addresses in your IP configuration (all DCs, member servers and clients), they need to be REMOVED and ONLY use the internal DNS server(s). This can be very problematic.

    Basically, AD requires DNS. DNS stores AD's resource and service locations in the form of SRV records, hence how everything that is part of the domain will find resources in the domain. If the ISP's DNS is configured in the any of the internal AD member machines' IP properties, (including all client machines and DCs), the machines will be asking the ISP's DNS 'where is the domain controller for my domain?", whenever it needs to perform a function, (such as a logon request, replication request, querying and applying GPOs, etc). Unfortunately, the ISP's DNS does not have that info and they reply with an "I dunno know", and things just fail. Unfortunately, the ISP's (or your router as a DNS server) DNS doesn't have information or records about your internal private AD domain, and they shouldn't have that sort of information.

    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 or simply use the internal networking routing to allow access. Here's the whole list of manual steps to follow.

    Another problem is the DC now becomes part of two Sites. This is another issue that can be problematic.

    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. If the both NICs are internal, I would suggest to pick a subnet, team the NICs and allow your internal routers handle the traffic between subnets - 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 DNS
    http://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/tr...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

    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/kb/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/kb/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 multihomed DC errors, and how to configure a multihomed DC, Ace Fekay, 24 Feb 2006
    http://www.ureader.com/message/3244572.aspx

    257623 257623 Domain Controller's Domain Name System Suffix Does Not Match Domain Name
    http://support.microsoft.com/?id=257623
    ==================================================================
    ==================================================================
    Ace
     
    Ace Fekay [MCT], Jul 24, 2009
    #9
  10. jjbrisbane

    jjbrisbane Guest

    Thanks ace, now i am confused more than ever..... Windows 2008 EBS is a 3
    server setup with the exchange server installed on the replica dc... i know
    it was previously not recommended but thats the way ms developed.... i think
    the best way to sort it out is to have a router handle the isp connection
    then put the threat management gateway after that before the internal lan...
    not sure how to configure!!
    thanks again

    Jon
     
    jjbrisbane, Jul 27, 2009
    #10
  11. Sorry, not meant to confuse you. Now realizing EBS is basically SBS on
    steroids, it's a bit different. I still have a feeling it's in the setup
    with the PPP thing causing the problem with the DC and Exchange not sending
    mail. In a regular operating system, RRAS is a stickler on a DC, same with
    Exchange, especially the combo. Exchange is a different story with SBS and
    EBS. I'm cross-posting this to the BS group to see if the experts over there
    can better help.

    In the meantime, check out the following new tool for EBS:

    The Microsoft EBS Team Blog : Microsoft IT Health Scanner Released!Microsoft
    Essential Business Server team is excited to announce the release of
    Microsoft IT Environment Health Scanner, the new diagnostic tool designed
    for ...
    http://blogs.technet.com/essentialb.../29/microsoft-it-health-scanner-released.aspx


    For the SBS folks in the SBS group, here's most of what transpired (minus my
    multihomed DC article): Sorry if it looks confusing. I tried to copy/paste
    most of it.
    ==============
    its a windows 2008 EBS installation with the 3 servers
    (management/messaging/security)

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : Management
    Primary Dns Suffix . . . . . . . : kenmore.XXX.com.au
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : kenmore.XXX.com.au
    XXX.com.au
    com.au

    Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : HP NC7782 Gigabit Server Adapter
    Physical Address. . . . . . . . . : 00-18-FE-86-67-3E
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv4 Address. . . . . . . . . . . : 192.168.1.2(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.1.1
    DNS Servers . . . . . . . . . . . : 127.0.0.1
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : Messaging
    Primary Dns Suffix . . . . . . . : kenmore.XXX.com.au
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : kenmore.XXX.com.au
    XXX.com.au
    com.au

    Ethernet adapter Local Area Connection 3:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : HP NC7781 Gigabit Server Adapter
    Physical Address. . . . . . . . . : 00-13-21-AE-9F-88
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv4 Address. . . . . . . . . . . : 192.168.1.3(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.1.1
    DNS Servers . . . . . . . . . . . : 192.168.1.2
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : Security
    Primary Dns Suffix . . . . . . . : kenmore.XXX.com.au
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : Yes
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : kenmore.XXX.com.au
    XXX.com.au
    com.au

    PPP adapter TPG:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : TPG
    Physical Address. . . . . . . . . :
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv4 Address. . . . . . . . . . . : XXX.241.216.160(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.255
    Default Gateway . . . . . . . . . : 0.0.0.0
    DNS Servers . . . . . . . . . . . : 203.12.160.35
    203.12.160.36
    NetBIOS over Tcpip. . . . . . . . : Disabled

    Ethernet adapter Local Area Connection 2:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
    #2
    Physical Address. . . . . . . . . : 00-16-35-59-37-82
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . :
    fe80::3472:dc6e:d2e5:ce86%11(Preferred)
    Default Gateway . . . . . . . . . :
    DHCPv6 IAID . . . . . . . . . . . : 285218357
    DHCPv6 Client DUID. . . . . . . . :
    00-01-00-01-11-8B-60-6B-00-16-35-59-37-78
    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
    fec0:0:0:ffff::2%1
    fec0:0:0:ffff::3%1
    NetBIOS over Tcpip. . . . . . . . : Disabled

    Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
    Physical Address. . . . . . . . . : 00-16-35-59-37-78
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv4 Address. . . . . . . . . . . : 192.168.1.1(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . :
    DNS Servers . . . . . . . . . . . : 192.168.1.2
    192.168.1.3
    NetBIOS over Tcpip. . . . . . . . : Enabled

    thanks for your help

    ==================

    Thanks Ace, i have made all the changes except i need the ppp adapter cause
    that is my internet connection. i am still experiencing the same issues. I
    have to reboot the messaging computer every 2 hours to clear those messages
    in the queue. the edge subscription is fine. the security server is still
    taking about 8 minutes to log on!!
    any other ideas?
    thanks
    Jon


    It's what's causing the problem. Can you move that PPP to a non-DC and
    non-Exchange server? How about an inexpensive router to take care of that
    task?

    Ace
    ============

    So let me get this straight. Your DCs are:
    Management (EBS 2008 Server) 192.168.1.2
    Messaging (Windows 2003 replica DC) 192.168.1.3 (with RRAS on it)

    Member servers:
    Security - Acting as the Gateway. (Windows 2008, dual homed with IPv6)
    192.168.1.1

    Well, first thing as I mentioned earlier, is Exchange is on the DC. Not a
    good idea. Causes too many problems. On top of that, RRAS is on the DC.
    Complicates matters.

    If you cannot move the Exchange role off the DC, especially the RRAS role,
    which in your case RRAS is probably the cause of the issues with mail flow.
    Running RRAS on a DC effectively makes it a multihomed DC (more than one NIC
    and/or IP). In this case, I would suggest to alter the DC's DNS registration
    behavior in order to straighten it out first, so the proper DNS records for
    the DC get registered. It takes a few steps including registry entries.
    Please read through before making any changes to understand the reasons and
    the implications.

    ====
    Multihomed DCs, DNS, RRAS servers.
    By Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA
    First published: January, 2003, updated July, 2006
    ==============================================
    [article snipped]

    =======================
     
    Ace Fekay [MCT], Jul 27, 2009
    #11
  12. Not to bounce you around again but I'd try posting this in the


    It sounds like you need a router in front, and then hand that static ip
    off to the security server, and from there do the rest of the
    messaging/management servers.

    And to folks in the DNS newsgroup, yes we know that putting Exchange on
    a DC is insane but we like it that way. When dealing with EBS or SBS
    just shoo people over to the newsgroups that they belong in and please
    don't tell them to uninstall anything.
     
    Susan Bradley, Jul 28, 2009
    #12
  13. Susan,

    With all do respect, I normaly do shoo folks to the right group, but it took
    me a few posts in the thread to finally realize it wasn't a regular WIndows
    installation. It didn't hit me at first when the poster mentioned EBS until
    after a couple of other posts. I know SBS/EBS works with multihoming, but
    like I said, if I caught on to it sooner, I wouldn't have posted my
    multihoming article and redirected the poster over to a more appropriate
    group.

    Ace
     
    Ace Fekay [MCT], Jul 28, 2009
    #13
  14. My apologies, that wasn't for you specifically but rather "placeholder"
    wording for google purposes in the future.

    EBS is a different beast and can get a bit tricky.
     
    Susan Bradley, Jul 28, 2009
    #14

  15. Oh, ok. I thought that was directed. I hope it's read by all to understand
    the differences and followed by anyone, including folks in our own groups to
    redirect it appropriately when someone asks for help with EBS.

    Thanks, and Cheers!

    Ace
     
    Ace Fekay [MCT], Jul 28, 2009
    #15
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.