Wrong Host answers a Ping request

Hi Experts.

It's a little curious. I've a problem with AppAssure and Replication, following in the debugging we found, that a PING from a CUSTOMER HOST to our HOST ends in a answer from A DIFFERENT HOST. And we don't find any source of this "PING RESPONSE"! See following ... and ideas how i can debug and find out why a wrong host is answering?

Our host: mypingu.homelinux.net

Customer 1 - Server 1 (W2k8 with AppAssure Replay4 Core and Agent):
PS C:\Users\install-oi> ping mypingu.homelinux.net -4
Ping wird ausgeführt für mypingu.homelinux.net [109.192.30.8] mit 32 Bytes Daten:
Antwort von 192.168.0.239: Bytes=32 Zeit=4ms TTL=255
Antwort von 192.168.0.239: Bytes=32 Zeit=4ms TTL=255
Antwort von 192.168.0.239: Bytes=32 Zeit=4ms TTL=255
Antwort von 192.168.0.239: Bytes=32 Zeit=4ms TTL=255
Ping-Statistik für 109.192.30.8:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
    (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 4ms, Maximum = 4ms, Mittelwert = 4ms
PS C:\Users\install-oi> tracert mypingu.homelinux.net
Routenverfolgung zu mypingu.homelinux.net [109.192.30.8] über maximal 30 Abschnitte:
  1     1 ms    <1 ms    <1 ms  192.168.1.10
  2     4 ms     8 ms     6 ms  192.168.0.239
Ablaufverfolgung beendet.
PS C:\Users\install-oi>
 
Customer 1 - Server 2 (SBS2008 with AppAssure Agent):
Copyright (c) 2006 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\install-oi>ping mypingu.homelinux.net
Ping wird ausgeführt für mypingu.homelinux.net [109.192.30.8] mit 32 Bytes Daten
:
Antwort von 109.192.30.8: Bytes=32 Zeit=18ms TTL=53
Antwort von 109.192.30.8: Bytes=32 Zeit=12ms TTL=53
Antwort von 109.192.30.8: Bytes=32 Zeit=17ms TTL=53
Antwort von 109.192.30.8: Bytes=32 Zeit=18ms TTL=53
Ping-Statistik für 109.192.30.8:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 12ms, Maximum = 18ms, Mittelwert = 16ms
C:\Users\install-oi>tracert mypingu.homelinux.net
Routenverfolgung zu mypingu.homelinux.net [109.192.30.8] über maximal 30 Abschni
tte:
  1    <1 ms    <1 ms    <1 ms  192.168.1.10
  2     7 ms     7 ms     6 ms  217.5.98.22
  3    14 ms     7 ms     6 ms  217.237.152.198
  4     6 ms     6 ms     6 ms  x320.str-m1.ip-bb.kabel-badenwuerttemberg.de [19
4.25.208.250]
  5     6 ms     6 ms    11 ms  ae0.str-m2.ip-bb.kabel-badenwuerttemberg.de [78.
42.40.5]
  6     7 ms     7 ms     7 ms  hsi-kbw-078-042-040-054.hsi3.kabel-badenwuerttem
berg.de [78.42.40.54]
  7     7 ms     9 ms     7 ms  172.30.1.45
  8     *        *        *     Zeitüberschreitung der Anforderung.
  9    15 ms    15 ms    17 ms  hsi-kbw-109-192-030-008.hsi6.kabel-badenwuerttem
berg.de [109.192.30.8]
Ablaufverfolgung beendet.
 
Customer 2r - Server 1 (with AppAssure Core and Agent):
C:\Dokumente und Einstellungen\Administrator>ping mypingu.homelinux.net
Ping wird ausgeführt für mypingu.homelinux.net [109.192.30.8] mit 32 Bytes Daten
:
Antwort von 192.168.211.213: Bytes=32 Zeit=4ms TTL=255
Antwort von 192.168.211.213: Bytes=32 Zeit=4ms TTL=255
Antwort von 192.168.211.213: Bytes=32 Zeit=4ms TTL=255
Antwort von 192.168.211.213: Bytes=32 Zeit=4ms TTL=255
Ping-Statistik für 109.192.30.8:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 4ms, Maximum = 4ms, Mittelwert = 4ms
C:\Dokumente und Einstellungen\Administrator>tracert mypingu.homelinux.net
Routenverfolgung zu mypingu.homelinux.net [109.192.30.8] über maximal 30 Abschni
tte:
  1    <1 ms    <1 ms    <1 ms  192.168.211.201
  2  192.168.211.201  meldet: Zielhost nicht erreichbar.
Ablaufverfolgung beendet.
C:\Dokumente und Einstellungen\Administrator>
 
Customer 3ra - Server 1:
C:\Dokumente und Einstellungen\Administrator>ping mypingu.homelinux.net
Ping wird ausgeführt für mypingu.homelinux.net [109.192.30.8] mit 32 Bytes Daten
:
Antwort von 109.192.30.8: Bytes=32 Zeit=69ms TTL=52
Antwort von 109.192.30.8: Bytes=32 Zeit=68ms TTL=52
Antwort von 109.192.30.8: Bytes=32 Zeit=69ms TTL=52
Antwort von 109.192.30.8: Bytes=32 Zeit=68ms TTL=52
Ping-Statistik für 109.192.30.8:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 68ms, Maximum = 69ms, Mittelwert = 68ms
C:\Dokumente und Einstellungen\Administrator>tracert mypingu.homelinux.net
Routenverfolgung zu mypingu.homelinux.net [109.192.30.8] über maximal 30 Abschni
tte:
  1     1 ms    <1 ms    <1 ms  192.168.238.1
  2   381 ms    63 ms    54 ms  217.5.98.8
  3    64 ms    54 ms   682 ms  217.237.152.110
  4    60 ms    59 ms    64 ms  s-ea4-i.S.DE.NET.DTAG.DE [62.154.22.106]
  5    62 ms    68 ms    76 ms  x320.str-m1.ip-bb.kabel-badenwuerttemberg.de [19
4.25.208.250]
  6    61 ms    61 ms    61 ms  ae0.STR-M2.ip-bb.kabel-badenwuerttemberg.de [78.
42.40.5]
  7    60 ms    60 ms    84 ms  HSI-KBW-078-042-040-054.hsi3.kabel-badenwuerttem
berg.de [78.42.40.54]
  8    94 ms    71 ms    69 ms  172.30.1.45
  9     *        *        *     Zeitüberschreitung der Anforderung.
 10    69 ms   116 ms   575 ms  HSI-KBW-109-192-030-008.hsi6.kabel-badenwuerttem
berg.de [109.192.30.8]
Ablaufverfolgung beendet.


ANY IDEA?!?!?

Greetings, Kai
LVL 1
kv0sAsked:
Who is Participating?
 
kv0sConnect With a Mentor Author Commented:
Solved. AppAssure Replay4 (Replication-Setup) was answering after a setup of replication.
0
 
Miguel Angel Perez MuñozCommented:
Is a DNS missconfigured. I suppose that one of this has this host locally and is resolving using this private IP.
0
 
jakethecatukCommented:
Hi,
The host that isn't resolving correctly, instead of using PING, try using NSLOOKUP to resolve the hostname as this will tell you what your DNS servers are seeing.

If the IP from DNS is showing incorrectly, then check the local DNS server for the incorrect entry and either correct it, or delete it.

If the IP from DNS is showing correctly, then the problem is local.  Check the hosts file on the local machine and delete any odd entries.
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
kv0sAuthor Commented:
Hi Thanks for the fast answer ...

DNS-Issue?
mypingu.homelinux.net [109.192.30.8]

That is really resolved correctly. Hosts empty, tried a "arp -d *" too.

The really curiosity is, why is a different "private-host" answering?

0
 
Miguel Angel Perez MuñozCommented:
Because is using internal dns and has internal IP...
0
 
jakethecatukCommented:
For customer 1, both servers are seeing 192.168.1.10 as the first hop for the tracert which I am guessing is going to be the local firewall.  The difference is how the firewall is handling the request.

For customer 1, are the servers on different VLAN's or anything like that?  Are you able to look at the firewall for customer 1 to see what is going on?

For customer 2, again, I would look at the firewall to see if that can give any clues.
0
 
Russell_VenableCommented:
192.168.1.10 should be the domain server handling the dns internally. Is 192.168.238.1 your firewall/router? It seems to be the one forwarding your traffic. Have you checked to see if router is setup properly for replication?
0
 
kv0sAuthor Commented:
No others has a solution provided which helps
0
All Courses

From novice to tech pro — start learning today.