What's happening here? Ping
 

I'm supposed to be pinging 224, but it shows it pinging 183 which is
unreachable, yet then reports stats for 224.

C:\Users\Harryping 10.131.97.224

Pinging 10.131.97.224 with 32 bytes of data:
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.

Ping statistics for 10.131.97.224:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

What's happening here? Ping
 

Harry Bloomfield wrote:

I'm supposed to be pinging 224, but it shows it pinging 183 which is
unreachable, yet then reports stats for 224.

Not quite, your PC is 183, so 183 is saying 224 is unreachable

What's happening here? Ping
 

On 19 Apr 2021 at 21:59:45 BST, "Harry Bloomfield, Esq."
wrote:

I'm supposed to be pinging 224, but it shows it pinging 183 which is
unreachable, yet then reports stats for 224.

C:\Users\Harryping 10.131.97.224

Pinging 10.131.97.224 with 32 bytes of data:
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.

Ping statistics for 10.131.97.224:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

That looks just plain wrong. What operating system?

--
Roger Hayter

What's happening here? Ping
 

On 2021-04-20, Roger Hayter wrote:
On 19 Apr 2021 at 21:59:45 BST, "Harry Bloomfield, Esq."
wrote:

I'm supposed to be pinging 224, but it shows it pinging 183 which is
unreachable, yet then reports stats for 224.

C:\Users\Harryping 10.131.97.224

Pinging 10.131.97.224 with 32 bytes of data:
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.

Ping statistics for 10.131.97.224:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

That looks just plain wrong. What operating system?


Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Which OS do you think could interpret a failure message as success?


--
Ian

"Tamahome!!!" - "Miaka!!!"

What's happening here? Ping
 

On 19/04/2021 21:59, Harry Bloomfield wrote:
I'm supposed to be pinging 224, but it shows it pinging 183 which is
unreachable, yet then reports stats for 224.

C:\Users\Harryping 10.131.97.224

Pinging 10.131.97.224 with 32 bytes of data:
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.

Ping statistics for 10.131.97.224:
* Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

I'm a networking tyro but - unlike some other posters - that seems to me
neither wholly surprising nor a failure as such nor something to which
Unix and Linux are immune. Search for "ping gives result for a
different ip address" and you'll find examples of what can cause it.

Just don't ask me to resolve it :)


--
Robin
reply-to address is (intended to be) valid

What's happening here? Ping
 

On 20/04/2021 13:35, Robin wrote:
On 19/04/2021 21:59, Harry Bloomfield wrote:
I'm supposed to be pinging 224, but it shows it pinging 183 which is
unreachable, yet then reports stats for 224.

C:\Users\Harryping 10.131.97.224

Pinging 10.131.97.224 with 32 bytes of data:
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.

Ping statistics for 10.131.97.224:
** Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

I'm a networking tyro but - unlike some other posters - that seems to me
neither wholly surprising nor a failure as such nor something to which
Unix and Linux are immune.* Search for "ping gives result for a
different ip address" and you'll find examples of what can cause it.

Just don't ask me to resolve it :)

yeah, tracrt and nslookup time!

What's happening here? Ping
 

On 2021-04-20, Robin wrote:
On 19/04/2021 21:59, Harry Bloomfield wrote:
I'm supposed to be pinging 224, but it shows it pinging 183 which is
unreachable, yet then reports stats for 224.

C:\Users\Harryping 10.131.97.224

Pinging 10.131.97.224 with 32 bytes of data:
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.

Ping statistics for 10.131.97.224:
Â* Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

I'm a networking tyro but - unlike some other posters - that seems to me
neither wholly surprising nor a failure as such nor something to which
Unix and Linux are immune. Search for "ping gives result for a
different ip address" and you'll find examples of what can cause it.

No other OS I know of interprets an ICMP error response as a successful ping response :)

Hint: We're laughing at the summary line, not the host unreachable.


--
Ian

"Tamahome!!!" - "Miaka!!!"

What's happening here? Ping
 

On 19/04/2021 21:59, Harry Bloomfield wrote:
I'm supposed to be pinging 224, but it shows it pinging 183 which is
unreachable, yet then reports stats for 224.

C:\Users\Harryping 10.131.97.224

Pinging 10.131.97.224 with 32 bytes of data:
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.

Ping statistics for 10.131.97.224:
Â*Â* Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
do you have a split subnet?
in linux i would want to see your client subnet configuration and
default route with 'ifconfig -a' and 'route'. I cant remember the
windoze commands.


it LOOKS like your default route is 10.131.97.183, and you are subnetted
to some other /25 or so subnet

--
In theory, there is no difference between theory and practice.
In practice, there is.
-- Yogi Berra

What's happening here? Ping
 

On 19/04/2021 21:59, Harry Bloomfield wrote:
I'm supposed to be pinging 224, but it shows it pinging 183 which is
unreachable, yet then reports stats for 224.

C:\Users\Harryping 10.131.97.224

Pinging 10.131.97.224 with 32 bytes of data:
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.

Ping statistics for 10.131.97.224:
Â*Â* Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

use Cipconfig /all and tell us what it sez...

--
€œBut what a weak barrier is truth when it stands in the way of an
hypothesis!€�

Mary Wollstonecraft

What's happening here? Ping
 

On 20/04/2021 13:50, Ian wrote:
On 2021-04-20, Robin wrote:
On 19/04/2021 21:59, Harry Bloomfield wrote:
I'm supposed to be pinging 224, but it shows it pinging 183 which is
unreachable, yet then reports stats for 224.

C:\Users\Harryping 10.131.97.224

Pinging 10.131.97.224 with 32 bytes of data:
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.

Ping statistics for 10.131.97.224:
Â* Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

I'm a networking tyro but - unlike some other posters - that seems to me
neither wholly surprising nor a failure as such nor something to which
Unix and Linux are immune. Search for "ping gives result for a
different ip address" and you'll find examples of what can cause it.

No other OS I know of interprets an ICMP error response as a successful ping response :)

Hint: We're laughing at the summary line, not the host unreachable.

While it does seem an odd way of doing it, there might be some sort of
sense to it. Having got a response back that the destination host was
unreachable does mean that the packets were not lost, just that they
could not be passed on, unlike if there were just no response and each
attempt timed out.

What's happening here? Ping
 

On 20/04/2021 13:50, Ian wrote:
On 2021-04-20, Robin wrote:
On 19/04/2021 21:59, Harry Bloomfield wrote:
I'm supposed to be pinging 224, but it shows it pinging 183 which is
unreachable, yet then reports stats for 224.

C:\Users\Harryping 10.131.97.224

Pinging 10.131.97.224 with 32 bytes of data:
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.

Ping statistics for 10.131.97.224:
Â* Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

I'm a networking tyro but - unlike some other posters - that seems to me
neither wholly surprising nor a failure as such nor something to which
Unix and Linux are immune. Search for "ping gives result for a
different ip address" and you'll find examples of what can cause it.

No other OS I know of interprets an ICMP error response as a successful ping response :)

Hint: We're laughing at the summary line, not the host unreachable.


Fair enough if I have been wrong in interrupting that as (to paraphrase)
no more than "I counted 4 packets out and I counted 4 replies, so none
were lost" - ie nothing about which if any address was reached.

--
Robin
reply-to address is (intended to be) valid

What's happening here? Ping
 

Roger Hayter wrote:

On 19 Apr 2021 at 21:59:45 BST, "Harry Bloomfield, Esq."
wrote:

I'm supposed to be pinging 224, but it shows it pinging 183 which is
unreachable, yet then reports stats for 224.

C:\Users\Harryping 10.131.97.224

Pinging 10.131.97.224 with 32 bytes of data:
Reply from 10.131.97.183: Destination host unreachable.

Ping statistics for 10.131.97.224:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

That looks just plain wrong. What operating system?

It's a perfectly normal windows message,

..183 is the machine doing the pinging of the .224 machine, the 183
machine is reporting that the 224 machine is not reachable, it's
different from "no reply".

What's happening here? Ping
 

SH wrote:

tracrt and nslookup time!

tracert won't help much as both addrs are on the same subnet (assuming
typical /24 masks) and if you can't ping by numeric addr, then DNS
doesn't enter into it.

What's happening here? Ping
 

On 19 Apr 2021 at 21:59:45 BST, "Harry Bloomfield, Esq."
wrote:

I'm supposed to be pinging 224, but it shows it pinging 183 which is
unreachable, yet then reports stats for 224.

C:\Users\Harryping 10.131.97.224

Pinging 10.131.97.224 with 32 bytes of data:
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.

Ping statistics for 10.131.97.224:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

It's .224 which is unreachable, and it is .183 which is telling you so. The
'unreachable' messages wouldn't be counted as replies (just as error messages)
by any sensible operating system and the summary should stay 100% loss.

--
Roger Hayter

What's happening here? Ping
 

On Mon, 19 Apr 2021 21:59:45 +0100, Harry Bloomfield, Esq. wrote:

I'm supposed to be pinging 224, but it shows it pinging 183 which is
unreachable, yet then reports stats for 224.

C:\Users\Harryping 10.131.97.224

Pinging 10.131.97.224 with 32 bytes of data:
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.

Ping statistics for 10.131.97.224:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Wonder if something is stuck in the ARP cache.

Try: arp -d *

(at elevated command prompt)



--
My posts are my copyright and if @diy_forums or Home Owners' Hub
wish to copy them they can pay me £1 a message.
Use the BIG mirror service in the UK: http://www.mirrorservice.org
*lightning surge protection* - a w_tom conductor

What's happening here? Ping
 

On 20/04/2021 15:02, Steve Walker wrote:
On 20/04/2021 13:50, Ian wrote:
On 2021-04-20, Robin wrote:
On 19/04/2021 21:59, Harry Bloomfield wrote:
I'm supposed to be pinging 224, but it shows it pinging 183 which is
unreachable, yet then reports stats for 224.

C:\Users\Harryping 10.131.97.224

Pinging 10.131.97.224 with 32 bytes of data:
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.
Reply from 10.131.97.183: Destination host unreachable.

Ping statistics for 10.131.97.224:
Â* Â* Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

I'm a networking tyro but - unlike some other posters - that seems to me
neither wholly surprising nor a failure as such nor something to which
Unix and Linux are immune.Â* Search for "ping gives result for a
different ip address" and you'll find examples of what can cause it.

No other OS I know of interprets an ICMP error response as a
successful ping response :)

Hint: We're laughing at the summary line, not the host unreachable.

While it does seem an odd way of doing it, there might be some sort of
sense to it. Having got a response back that the destination host was
unreachable does mean that the packets were not lost, just that they
could not be passed on, unlike if there were just no response and each
attempt timed out.

Unfortunately it might be as simple as the local connection saying 'I am
not on the same network as the destination'

--
New Socialism consists essentially in being seen to have your heart in
the right place whilst your head is in the clouds and your hand is in
someone else's pocket.