Results 1 to 5 of 5

Thread: dc can't ping domain name

  1. #1
    Join Date
    May 2009
    Posts
    3

    dc can't ping domain name

    Hi all
    We have domain in our office. I recently have some problems in domian so I retrive dc' backup (Acronis True Image backup) and the problem doesn't solve. the dc doesn't ping domain name. clients find dns with nslookup but can't ping domain name (and so I can't join them to domain). all tests passed with dcdiag and netdiag.

    Any Idea?

  2. #2
    Join Date
    Jul 2004
    Posts
    135

    Re: dc can't ping domain name

    Well the only thing as of now i can suggest you is to run netdiag /test:dns, ipconfig /all from DC and from client workstation.

    Dont forget to post the results here.

  3. #3
    Join Date
    May 2009
    Posts
    3
    Thanks For Reply
    netdiag form DC:

    C:\Program Files\Support Tools>netdiag /test:dns

    ........

    Computer Name: BEHSAMAN-DC
    DNS Host Name: behsaman-dc.behsaman
    System info : Microsoft Windows Server 2003 (Build 3790)
    Processor : x86 Family 6 Model 8 Stepping 10, GenuineIntel
    List of installed hotfixes :
    Q147222


    Netcard queries test . . . . . . . : Passed



    Per interface results:

    Adapter : Local Area Connection

    Netcard queries test . . . : Passed


    Global results:


    Domain membership test . . . . . . : Passed


    NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
    NetBT_Tcpip_{7C79F685-30EC-4523-883B-DFBB3A4AAA01}
    1 NetBt transport currently configured.


    DNS test . . . . . . . . . . . . . : Passed
    PASS - All the DNS entries for DC are registered on DNS server '192.168.100.200'.


    The command completed successfully

    ------------------------------------------
    ipconfig from DC:

    C:\Program Files\Support Tools>ipconfig /all

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : behsaman-dc
    Primary Dns Suffix . . . . . . . : behsaman
    Node Type . . . . . . . . . . . . : Unknown
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : behsaman

    Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : D-Link DFE-530TX PCI Fast Ethernet Adapter (rev.C)
    Physical Address. . . . . . . . . : 00-50-BA-54-3A-00
    DHCP Enabled. . . . . . . . . . . : No
    IP Address. . . . . . . . . . . . : 192.168.100.200
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . :
    DNS Servers . . . . . . . . . . . : 192.168.100.200
    ------------------------------------------
    ipconfig from client:

    C:\Users\Administrator>ipconfig /all

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : mahdippc
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
    Physical Address. . . . . . . . . : 00-01-4A-F0-7B-FE
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::a8d5:ffdc:8f5f:10d5%10(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.100.241(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.100.50
    DNS Servers . . . . . . . . . . . : 192.168.100.200
    192.168.100.50
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Wireless LAN adapter Wireless Network Connection:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Atheros Wireless Network Adapter
    Physical Address. . . . . . . . . : 00-16-CE-03-35-85
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 2:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : isatap.{70BAE8AF-7442-4961-80F9-D61B8D593
    321}
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 10:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : isatap.{00C40CAA-F647-4859-B3FA-C3E90AEA1
    F59}
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 12:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : isatap.{094B9A9F-ACF2-4F33-89A8-E24DD4E8F
    7E6}
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    Thanks Florian
    This is the only DC in domian and DNS is running, as I said before the client can find it via nslookups

  4. #4
    Join Date
    Jun 2006
    Posts
    200

    Re: dc can't ping domain name

    I dont think too that images are not an option for backing up a DC. It will probably result in a USN rollback. You can confirm this from this Knowledge Base Article: http://support.microsoft.com/kb/875495

    Secondly, your domain is a single label domain which is also not the best option, see this article about additional DNS configuration:
    http://support.microsoft.com/kb/300684

  5. #5
    Join Date
    May 2009
    Posts
    3
    Thank you fro reply Paul
    the server with 192.168.100.50 is our internet gateway that has two NIC's that one connected to internet and another one connected to LAN and I use Keri Winroute Firewall to NAT betwwn these networks and also monitoring internet access.
    If I set default gateway to dc, the internet connection will be lost.
    Thanks again for your attention.

    thanks fo reply Meinolf
    I removed 192.168.100.50 from default gateway and dns of clients and dc, but the problem persists.
    I set DNS as forwarder to 192.168.100.50 and removed root hints before;
    but because we have problems in internet connection I also set alternative DNS to 192.168.100.50

    wonderfully I ping "behsaman." instead of "behsaman" andit worked.
    also I could join to domain with this name.

    Thank you all.
    I set the default gateway on DC and the problem solved.
    so DC can ping domain name but on client I remove DNS of router but I can't ping the domian name and also I can ping it by FQDN.

    Yes but doesn't work

Similar Threads

  1. Replies: 1
    Last Post: 16-09-2009, 10:11 AM
  2. Local DC does not response to ping on domain names
    By cyw77 in forum Windows Software
    Replies: 2
    Last Post: 28-07-2009, 01:34 PM
  3. Replies: 3
    Last Post: 05-02-2009, 02:27 PM
  4. Cannot ping Active Directory Domain Name
    By PhilTeale in forum Windows Server Help
    Replies: 5
    Last Post: 17-10-2008, 07:26 PM
  5. Cannot ping domain name
    By Daniel in forum Windows Server Help
    Replies: 1
    Last Post: 17-04-2007, 04:06 PM

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,526,473.66568 seconds with 17 queries