Problem with internet connection

Discussion in 'Server Networking' started by JN, Aug 25, 2009.

  1. JN

    JN Guest

    I have a problem with Windows 2008 server. There is AD and DNS server
    installed on the server. Some time I can reach only LAN. Diagnostic says
    there is a problem with DNS. DNS server cannot reach servers in the Internet.
    I also cannot ping to any address in the internet using TCPIP address. I can
    ping any PC on the LAN.
    Yesterday I lost static address of the LAN adapter after installation updates.
    JN, Aug 25, 2009
    1. Advertisements

  2. Hello JN,

    Please post an unedited ipconfig /all from the server. Sounds like DNS settings.

    Best regards

    Meinolf Weber
    Meinolf Weber [MVP-DS], Aug 25, 2009
    1. Advertisements

  3. JN

    JN Guest

    Konfigurace protokolu IP syst,mu Windows

    N zev hostitele . . . . . . . . . : susserver
    Prim rn? pý?pona DNS. . . . . . . : suskla.local
    Typ uzlu . . . . . . . . . . . . : hybridn?
    Povoleno smRrov n? IP . . . . . . : Ne
    WINS Proxy povoleno . . . . . . . : Ne
    Prohled vac? seznam pý?pon DNS. . : suskla.local

    It is in Czech, should I translate it?

    Adapter s?tR Ethernet LAN:

    Pý?pona DNS podle pýipojen? . . . :
    Popis . . . . . . . . . . . . . . : HP NC326i PCIe Dual Port Gigabit
    Server Adapter
    Fyzick Adresa. . . . . . . . . . : 00-24-81-A8-45-B2
    Protokol DHCP povolen . . . . . . : Ne
    Automatick konfigurace povolena : Ano
    Adresa IPv4 . . . . . . . . . . . :,)
    Maska pods?tR . . . . . . . . . . :
    Vechoz? br na . . . . . . . . . . :
    Servery DNS . . . . . . . . . . . :
    Rozhran? NetBios nad protokolem TCP/IP. . . . . . . . : Povoleno

    Adapt,r pro tunelov, pýipojen? Pýipojen? k m?stn? s?ti*:

    Stav m,dia . . . . . . . . . . . : odpojeno
    Pý?pona DNS podle pýipojen? . . . :
    Popis . . . . . . . . . . . . . . : Microsoft ISATAP Adapter
    Fyzick Adresa. . . . . . . . . . : 00-00-00-00-00-00-00-E0
    Protokol DHCP povolen . . . . . . : Ne
    Automatick konfigurace povolena : Ano
    JN, Aug 25, 2009
  4. Hello JN,

    It appears that the following are two ISP's DNS servers.

    They will need to be removed. Only leave in the following, assuming that
    both of these IP address are internal DNS on domain controllers.
    I suggest to setup a Forwarder. That is done in DNS properties, Forwarders
    tab. Use your two IP addresses.

    As for pinging, pings may probably be filtered on your firewall. If you can
    ping say,, and it resolves, but does not ping, but you can
    open a browser and works, then I wouldn't worry about it. If
    you really need ping to respond from the internet, I would look at your
    router/firewall to see if ICMP Echo is allowed.


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

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

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

    For urgent issues, please contact Microsoft PSS directly. Please check for regional support phone numbers.
    Ace Fekay [MCT], Aug 25, 2009
  5. Hello JN,

    As Ace already stated remove the does it belong to) and from the NIC and configure them as FORWARDERS under the DNS
    server properties in the DNS management console.

    Best regards

    Meinolf Weber
    Meinolf Weber [MVP-DS], Aug 25, 2009
  6. JN

    jn Guest

    Thank You now it works.
    It is resonable to use two network interfaces to speed up communication with
    How should I setup the second network interface?

    jn, Aug 30, 2009
  7. Hello JN,

    Nice to hear that you solved it.

    No. Having two NICs doesn't mean to use them. Depending on the hardware/NIC
    you maybe can use a teaming software to combine both physical NICs to a virtual,
    which then can be used for automatic failover or loadbalanced. HP has it
    and also Broadcom offers this as far as i know.

    Multihoming a server, using more then one ip address, can result in problems
    you don't wan't. For more details see:

    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;en-us;272294

    191611 - Symptoms of Multihomed Browsers;EN-US;191611

    Phillip Windell

    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

    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):

    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]:

    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

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

    (Create this Multi-String Value under it):
    Registry value: DnsAvoidRegisterRecords
    Data type: REG_MULTI_SZ
    Values: LdapIpAddress

    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]:

    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 ( is used for illustrative

    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:

    10. If you haven't done so, configure a forwarder. You can use if
    not sure which DNS to forward to until you've got the DNS address of your
    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

    323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
    (How to configure a forwarder):

    Active Directory communication fails on multihomed domain controllers

    <==*** 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]:

    Active Directory communication fails on multihomed domain controllers

    246804 - How to enable or disable DNS updates in Windows 2000 and in Windows
    Server 2003

    295328 - Private Network Interfaces on a Domain Controller Are Registered in
    [also shows DnsAvoidRegisterRecords LdapIpAddress to avoid reg sameasparent
    private IP]:

    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]:

    825036 - Best practices for DNS client settings in Windows 2000 Server and
    in Windows Server 2003 (including how-to configure a forwarder):;en-us;825036

    291382 - Frequently asked questions about Windows 2000 DNS and Windows
    Server 2003 DNS

    296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
    [Registry Entry]:

    Rid Pool Errors and other mutlhomed DC errors, and how to configure a multihomed
    DC, Ace Fekay, 24 Feb 2006

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


    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 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

    Best regards

    Meinolf Weber

    Meinolf Weber [MVP-DS], Aug 30, 2009

  8. As Meinolf said, two non-teamed NICs on a DC is not advisable. Meinolf gave
    you some info to read up on it.

    Ace Fekay [MCT], Aug 30, 2009
  9. JN

    JN Guest

    Thank You wery much for Your time and clear answers
    Have a nice time
    JN, Aug 31, 2009
  10. JN

    JN Guest

    Thank You wery much for Your time and clear answers
    Have a nice time
    JN, Aug 31, 2009
  11. Hello JN,

    You're welcome.

    Best regards

    Meinolf Weber

    Meinolf Weber [MVP-DS], Aug 31, 2009

  12. You are welcome!

    Ace Fekay [MCT], Aug 31, 2009
    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.