none
Ping a computer returns Ip address of a different

    Question

  • hello,

    When i try pinging a machine with FQDN, it returns pinging computer(10.x.x.x), reply from 172.x.x.x

    In DNs, i see a host A record created with a differnt name that maps to Ip (10.x.x.x),

    Please advise


    kits

    Wednesday, April 11, 2012 5:11 AM

Answers

  • Hello,

    on the DNS servers configure and enable scavenging and cleanup incorrect entires manual until the configuration is done:

    http://blogs.technet.com/b/networking/archive/2008/03/19/don-t-be-afraid-of-dns-scavenging-just-be-patient.aspx


    Best regards

    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/

    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

    Wednesday, April 11, 2012 6:39 AM
  • Hello,

    I would agree with Meinolf.

    You have to clean up obsolete DNS records. This could be done using aging and Scavenging.

    More here: http://technet.microsoft.com/en-us/library/cc959277.aspx

    Just be patient and it will do the job for you.

    Note that aging and scavenging will not clean up static DNS records. For that, you have to delete manually all obsolete static DNS records.

    So that a client computer updates its DNS records, run ipconfig /registerdns and restart netlogon on it.


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

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    Wednesday, April 11, 2012 7:32 AM

All replies

  • Seems to be DNS issue.

    Do this,

    On the computer , run IPconfig /flushdns and IPconfig /registerdns.

    let us know the results.

    IF nothing works out,. Please run ipconfig /all and post the results here.

    Regards,

    _Prashant_


    MCSA|MCITP SA|Microsoft Exchange 2003 Blog - http://prashant1987.wordpress.com Disclaimer: This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    Wednesday, April 11, 2012 5:25 AM
  • Could it be a router issue.. As we have buld a no of Virtual machines and while pinging these machine.. we get a reply from same IP 10.x.x.x

    kits


    • Edited by fiona09 Wednesday, April 11, 2012 5:30 AM
    Wednesday, April 11, 2012 5:28 AM
  • Is it happening on multiple Virtual machines?

    If yes can you post ipconfig /all from one of the client computer?

    Also try pinging with ping -a IP address and let us know which host name it is resolving in DNS

    Regards,

    _Prashant_


    MCSA|MCITP SA|Microsoft Exchange 2003 Blog - http://prashant1987.wordpress.com Disclaimer: This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    Wednesday, April 11, 2012 5:32 AM
  • Posting the results

    nslookup
    Default Server:  ussbemdc01.emea.astrazeneca.net
    Address:  156.70.224.34

    > trisrl0012556
    Server:  ussbemdc01.emea.astrazeneca.net
    Address:  156.70.224.34

    Name:    trisrl0012556.emea.astrazeneca.net
    Address:  10.146.229.97

    >
    C:\Documents and Settings\>ping trisrl0012556

    Pinging trisrl0012556.emea.astrazeneca.net [10.146.229.97] with 32 bytes of data
    :

    Request timed out.
    Reply from 172.19.103.193: TTL expired in transit.

    Ping statistics for 10.146.229.97:
        Packets: Sent = 2, Received = 1, Lost = 1 (50% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms
    Control-C
    ^C
    C:\Documents and Settings\>ping -a 10.146.229.97

    Pinging esmdrl0066499.emea.astrazeneca.net [10.146.229.97] with 32 bytes of data
    :

    Reply from 172.19.103.193: TTL expired in transit.
    Reply from 172.19.103.193: TTL expired in transit.

    Ping statistics for 10.146.229.97:
        Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms
    Control-C
    ^C
    C:\Documents and Settings\>ping -a 172.19.103.193

    Pinging 172.19.103.193 with 32 bytes of data:

    Reply from 172.19.103.193: bytes=32 time=82ms TTL=246
    Reply from 172.19.103.193: bytes=32 time=82ms TTL=246
    Reply from 172.19.103.193: bytes=32 time=82ms TTL=246
    Reply from 172.19.103.193: bytes=32 time=82ms TTL=246

    Ping statistics for 172.19.103.193:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 82ms, Maximum = 82ms, Average = 82ms

    Please find nslookup and ping results for computer trisrl0012556


    kits

    Wednesday, April 11, 2012 5:49 AM
  • ping -a 172.119.103.193 is not returing with no Host record.

    Can you please check your Reverse lookup zone for this.

    I really think , IN DNS there is mismatch in PTR records.

    Regards,

    _Prashant_


    MCSA|MCITP SA|Microsoft Exchange 2003 Blog - http://prashant1987.wordpress.com Disclaimer: This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    Wednesday, April 11, 2012 6:07 AM
  • Hello,

    on the DNS servers configure and enable scavenging and cleanup incorrect entires manual until the configuration is done:

    http://blogs.technet.com/b/networking/archive/2008/03/19/don-t-be-afraid-of-dns-scavenging-just-be-patient.aspx


    Best regards

    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/

    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

    Wednesday, April 11, 2012 6:39 AM
  • Hello,

    I would agree with Meinolf.

    You have to clean up obsolete DNS records. This could be done using aging and Scavenging.

    More here: http://technet.microsoft.com/en-us/library/cc959277.aspx

    Just be patient and it will do the job for you.

    Note that aging and scavenging will not clean up static DNS records. For that, you have to delete manually all obsolete static DNS records.

    So that a client computer updates its DNS records, run ipconfig /registerdns and restart netlogon on it.


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

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    Wednesday, April 11, 2012 7:32 AM
  • Hi,

    I also agree with meinolf, however if this is a server that load balances then it may go to that machine but then bounce to another machine.

    Hope it helps.


    Lewis.j.Routledge

    Thursday, April 12, 2012 3:47 PM
  • hello, Please find details that has investigated so far:

    >In Wins, computer is mapped correctly with the IP

    >No records found in dns

    > while conencting to machine by IP, i get following error

    The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead of the name.

    >this computer is not load balanced

    > ipconfig flsuh and register has been done alredy on few but still same


    kits


    • Edited by fiona09 Friday, April 13, 2012 5:33 AM
    Friday, April 13, 2012 5:32 AM
  • Also i checked that dhcp server shows the same IP address assigned to a diffrent computer.. what needs to be done for the cleint to get correct IP

    kits

    Friday, April 13, 2012 5:45 AM
  • Hello,

    have you configured scavenging assuggested and manually removed obsolete entries from the DNS zonmes of the domain DNS server?

    Please post an unedited ipconfig /all from the machine you are trying to ping and the client you use for this.


    Best regards

    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/

    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

    Friday, April 13, 2012 6:25 AM
  • Hi,

    I don’t think DHCP server will lease same IP address to different computer. Did the trisrl0012556 computer have multiple IP addresses? Please enable scavenging on the DNS zone as Meinolf suggested. Also post the necessary information for further troubleshoot.

    An incorrect IP address is returned when you ping a server by using its NetBIOS name in Windows Server 2008 or in Windows Server 2008 R2

    http://support.microsoft.com/kb/981953


    Best Regards,

    Aiden


    Aiden Cao

    TechNet Community Support

    Monday, April 16, 2012 3:44 AM