Results 1 to 11 of 11

Thread: Can't ping DNS

  1. #1
    john Guest

    Can't ping DNS

    I have a small network running 2k3. My server is multi-homed. The
    server can get on the internet , but no workstation can.The machines
    can ping each other however, they can't ping the server and vice
    versa. I tried pinging the DNS from the machines but was not
    successful. I checked the firewall settings and it was not enabled.
    Please help.

  2. #2
    Lanwench [MVP - Exchange] Guest

    Re: Can't ping DNS

    I suggest you post this in microsoft.public.windows.server.sbs for the most
    expert help. Fully explain your setup (using ISA?) and include an *unedited*
    ipconfig /all from your server and one of your workstations.

  3. #3
    Meinolf Weber Guest

    Re: Can't ping DNS

    The big problem is your multihoming, especial if it is a domain controller.
    Please post an ipconfig /all from the server. Better change the way of connecting
    your network. Servers and workstations to switch, Internet router to the
    same switch and then reconfigure the servers DNS to forward requests to the
    ISP's DNS server.

    Have a look on this (from another posting) about multihoming DC's:

    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/tre...o_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...b;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

  4. #4
    Lanwench [MVP - Exchange] Guest
    I totally agree - but this is SBS, which is a bit special - that's why I
    recommended that the OP post in the SBS group to ensure he/she gets the most
    expert help.

    I have 2k3 datacenter.

    However, I agree with Meinholf (and myriad others) that multihomed DCs are
    bad news and are best avoided. *Especially* as you ain't running SBS.

  5. #5
    Kevin D. Goodknecht Sr. [MVP] Guest
    Can you run nslookup against your DNS and get an answer?
    Ping is not a tool for diagnosing DNS, but on that point of not being able
    to "ping" the server, have you configured RRAS?
    RRAS has it own firewall component which blocks ICMP on the external
    interface by default.
    If you have configured RRAS, make sure packet filters are not set up, or if
    packet filters are set up, make sure they are configured properly.

    Check that there is exception created for the Windows Firewall.

    Yep, from my post. I put that together long ago. I was going to post it too,
    but beat me too it!

  6. #6
    Ace Fekay [MVP] Guest

    Re: Can't ping DNS

    Multihoming a DC is inviting issues if not configured properly, unless the
    NICs are teamed. Follow the instructions that Meinolf posted to properly
    configure it or expect continued issues.

  7. #7
    Join Date
    Jan 2010
    Posts
    1

    Re: Can't ping DNS

    plz anybody help me out.
    problem is i cant ping the dns server from clients and exchange server,database server,isa server.
    we have got cisco pix firewall,cisco router ,
    all cables are connected to each other,all green lights are blinking.
    dcdiag test i have done,all test passed successfully.
    users cant access there shared folders and emails.
    some times it connects and run smoothly for 1 to 2 min ,then suddenly it disconnects.
    i cannot ping to my default gateway address from any of the servers.
    internet is down at the moment becoz of ISP provider.
    but i want to put all the users in intranet.
    plz help me out

  8. #8
    Ace Fekay [MVP-DS, MCT] Guest

    Re: Can't ping DNS

    "kynayyer" <kynayyer.44mufb@DoNotSpam.com> wrote in message
    news:kynayyer.44mufb@DoNotSpam.com...
    >
    > Hello,
    > plz anybody help me out.
    > problem is i cant ping the dns server from clients and exchange
    > server,database server,isa server.
    > we have got cisco pix firewall,cisco router ,
    > all cables are connected to each other,all green lights are blinking.
    > dcdiag test i have done,all test passed successfully.
    > users cant access there shared folders and emails.
    > some times it connects and run smoothly for 1 to 2 min ,then suddenly
    > it disconnects.
    > i cannot ping to my default gateway address from any of the servers.
    > internet is down at the moment becoz of ISP provider.
    > but i want to put all the users in intranet.
    > plz help me out
    > thx
    > khaja
    >
    >



    Hello Khaja,

    For starters, it would be very helpful if you posted an unedited ipconfig
    /all from your server, and from a sample workstation so we can get a better
    idea of your infrastructure's configuration.

    Thank you,

    --
    Ace

    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, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
    MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services

    If you feel this is an urgent issue and require immediate assistance, please
    contact Microsoft PSS directly. Please check http://support.microsoft.com
    for regional support phone numbers.



  9. #9
    Jonathan de Boyne Pollard Guest

    Re: Can't ping DNS



    problem is i cant ping the dns server from clients and exchange server,database server,isa server.
    i cannot ping to my default gateway address from any of the servers.




    Then your problem is a network connectivity problem, not a DNS problem. Remember that ping is not a DNS diagnosis tool.




    users cant access there shared folders and emails.
    some times it connects and run smoothly for 1 to 2 min ,then suddenly it disconnects.




    Solve your basic network connectivity problem first, before looking at application problems.



    we have got cisco pix firewall,cisco router, all cables are connected to each other,all green lights are blinking.




    So the next thing to look at is the layer immediately above the raw physical connections.&nbsp; Check that the operating systems are recognizing the network interface cards.&nbsp; What does Windows NT on the clients and servers report for the network interfaces?&nbsp; Are they up and connected?&nbsp; Once you've ensured that the network interfaces are up and connected, look at the IP addresses being assigned, the subnet masks, and the IP routing tables.




    All of this comes before leaping to the conclusion that there is a DNS problem. Remember: Prove that your problem really is a DNS problem.



  10. #10
    Otto Klemperer Guest

    Re: Can't ping DNS

    On Tue, 12 Jan 2010 21:19:58 +0000, Jonathan de Boyne Pollard
    <J.deBoynePollard-newsgroups@NTLWorld.COM> wrote:

    ><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
    ><html>
    ><head>
    > <meta content="text/html; charset=ISO-8859-1"
    > http-equiv="Content-Type">
    ></head>
    ><body bgcolor="#ffffff" text="#000000">
    ><blockquote cite="mid:kynayyer.44mufb@DoNotSpam.com" type="cite">
    > <p wrap="">problem is i cant ping the dns server from clients and
    >exchange server,database server,isa server.<br>
    >i cannot ping to my default gateway address from any of the servers.<br>
    > </p>
    ></blockquote>
    ><p>Then your problem is a network connectivity problem, not a DNS
    >problem. Remember that <a
    > href="http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/nslookup-results-different-to-ping.html"><code>ping</code>
    >is not a DNS diagnosis tool</a>.<br>
    ></p>
    ><blockquote cite="mid:kynayyer.44mufb@DoNotSpam.com" type="cite">
    > <p wrap="">users cant access there shared folders and emails.<br>
    >some times it connects and run smoothly for 1 to 2 min ,then suddenly
    >it disconnects.<br>
    > </p>
    ></blockquote>
    ><p>Solve your basic network connectivity problem first, before looking
    >at application problems.
    ></p>
    ><blockquote cite="mid:kynayyer.44mufb@DoNotSpam.com" type="cite">
    > <p wrap="">we have got cisco pix firewall,cisco router, all cables
    >are connected to each other,all green lights are blinking. <br>
    > </p>
    ></blockquote>
    ><p>So the next thing to look at is the layer immediately above the raw
    >physical connections.&nbsp; Check that the operating systems are recognizing
    >the network interface cards.&nbsp; What does Windows NT on the clients and
    >servers report for the network interfaces?&nbsp; Are they up and connected?&nbsp;
    >Once you've ensured that the network interfaces are up and connected,
    >look at the IP addresses being assigned, the subnet masks, and the IP
    >routing tables.<br>
    ></p>
    ><p>All of this comes <em>before</em> leaping to the conclusion that
    >there is a DNS problem. Remember: <a
    > href="http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/dns-narrow-problem-locus.html">Prove
    >that
    >your
    >problem
    >really is a DNS problem</a>.<br>
    ></p>
    ></body>
    ></html>


    I agree, it looks like a basic connectivity issue. That issue could be
    hiding additional issues further up the stack, but fix the
    connectivity first.


  11. #11
    Ace Fekay [MVP-DS, MCT] Guest

    Re: Can't ping DNS

    "Otto Klemperer" <otto9@puzzles.cu> wrote in message
    news:ehaqk5523bhlo5kd4osaja6ehhk2t3p5fd@4ax.com...
    > On Tue, 12 Jan 2010 21:19:58 +0000, Jonathan de Boyne Pollard
    > <J.deBoynePollard-newsgroups@NTLWorld.COM> wrote:
    >
    >><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
    >><html>
    >><head>
    >> <meta content="text/html; charset=ISO-8859-1"
    >> http-equiv="Content-Type">
    >></head>
    >><body bgcolor="#ffffff" text="#000000">
    >><blockquote cite="mid:kynayyer.44mufb@DoNotSpam.com" type="cite">
    >> <p wrap="">problem is i cant ping the dns server from clients and
    >>exchange server,database server,isa server.<br>
    >>i cannot ping to my default gateway address from any of the servers.<br>
    >> </p>
    >></blockquote>
    >><p>Then your problem is a network connectivity problem, not a DNS
    >>problem. Remember that <a
    >> href="http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/nslookup-results-different-to-ping.html"><code>ping</code>
    >>is not a DNS diagnosis tool</a>.<br>
    >></p>
    >><blockquote cite="mid:kynayyer.44mufb@DoNotSpam.com" type="cite">
    >> <p wrap="">users cant access there shared folders and emails.<br>
    >>some times it connects and run smoothly for 1 to 2 min ,then suddenly
    >>it disconnects.<br>
    >> </p>
    >></blockquote>
    >><p>Solve your basic network connectivity problem first, before looking
    >>at application problems.
    >></p>
    >><blockquote cite="mid:kynayyer.44mufb@DoNotSpam.com" type="cite">
    >> <p wrap="">we have got cisco pix firewall,cisco router, all cables
    >>are connected to each other,all green lights are blinking. <br>
    >> </p>
    >></blockquote>
    >><p>So the next thing to look at is the layer immediately above the raw
    >>physical connections.&nbsp; Check that the operating systems are
    >>recognizing
    >>the network interface cards.&nbsp; What does Windows NT on the clients and
    >>servers report for the network interfaces?&nbsp; Are they up and
    >>connected?&nbsp;
    >>Once you've ensured that the network interfaces are up and connected,
    >>look at the IP addresses being assigned, the subnet masks, and the IP
    >>routing tables.<br>
    >></p>
    >><p>All of this comes <em>before</em> leaping to the conclusion that
    >>there is a DNS problem. Remember: <a
    >> href="http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/dns-narrow-problem-locus.html">Prove
    >>that
    >>your
    >>problem
    >>really is a DNS problem</a>.<br>
    >></p>
    >></body>
    >></html>

    >
    > I agree, it looks like a basic connectivity issue. That issue could be
    > hiding additional issues further up the stack, but fix the
    > connectivity first.
    >




    It could be an ISA firewall client issue, as well. The poster stated that
    ping doesn't work, which could simply mean that ICMP is blocked in a policy
    for the installed ISA firewall client, or worse, the LAT is incorrect, or
    worse, the ISA firewall client policies are misconfigured, which can
    snowball into other issues. However there wasn't enough infrastructure
    configuration posted other than reported symptoms to ascertain if this is
    the issue.

    Ace

    Ace



Similar Threads

  1. Wireless cannot ping / ethernet can ping
    By Nereus in forum Networking & Security
    Replies: 6
    Last Post: 14-08-2010, 05:56 AM
  2. Replies: 3
    Last Post: 05-02-2009, 02:27 PM
  3. How to Ping?
    By Maximus() in forum Technology & Internet
    Replies: 5
    Last Post: 12-01-2009, 06:30 AM
  4. I can ping with IPv6. I can not ping with IPv4.
    By Eric Gamess in forum Vista Help
    Replies: 2
    Last Post: 04-05-2008, 01:31 AM
  5. Can resolve DNS, can ping IP, but can't ping by DNS??
    By Bryan L in forum Windows Server Help
    Replies: 14
    Last Post: 23-01-2007, 03:51 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,565,219.07525 seconds with 16 queries