[Noobface80]

Hello my friends and foes; I am stuck with a dillema! I'm trying to ping a machine.

Sounds simple enough right?

WRONG!
(Unless you're a wizard that is)

Getting to the point, I am trying to ping from computer A to computer B where both are under the network of a home router. I have tried research and came to a link here:
Ping Different subnets using routing tables!

Which showed me how to use routing tables in order to specify a route, but to no avail. I know firewall usually blocks icmp requests to pc's, but I know that my route table isn't successful because when I try to traceroute the gateway, which works beautifully, but then when trying to traceroute the internal hoping it takes the route of the gateway, it doesnt even leave the network. I figure I'm doing it wrong, but I'm just trying to get a proper path to the client computer on the network; that's all I need. I dont care about firewall blocked icmp request packets! Just help me get there (if you can!)

[Gt403cyl]

Ok I might have this completely wrong but.....

Sounds like you are trying to ping PC A from PC B while both are on the same network and are having problems.....

What command are you using?

Example:
From PC A use CMD- "ping 192.168.0.xx"
You need to use the LAN IP....

[Armada]

If both computers are on the same network it is as simple as pinging the internal IP# of the other machine. (Easily obtained from the connected devices table in router settings) If the machine still does not reply to pings, it means they have a software firewall which disables said replies.

[Noobface80]

Sorry...I worded it wrong.




TLDR: I am trying to ping between 2 different computers on 2 different subnets and 2 different networks...

[Armada]

Sorry...I worded it wrong.




TLDR: I am trying to ping between 2 different computers on 2 different subnets and 2 different networks...

Ahhh yea, you need to add an IP table to connect a pipe between the 2 subnets.
Look into configuration of IP tables, you can likely do this straight from your router device too assuming it is a later model somewhere in advanced settings.

It is kind of odd you are running 2 subnets on a home network though. ❓

[Longdog]

Sorry...I worded it wrong.




TLDR: I am trying to ping between 2 different computers on 2 different subnets and 2 different networks...

ping ExternalIPHere -t

if that doesn't work someone has pinging disabled on their network.

[Armada]

ping ExternalIPHere -t

if that doesn't work someone has pinging disabled on their network.

You have clearly missed the networking problem here.

He is running 2 separate subnets within the same LAN environment.
IE:
192.168.1.X
192.186.2.X

These by default do not communicate together, so he has to create a link or pipeline between the two to communicate.

Spoiler (Click to View)

[Gt403cyl]

You have clearly missed the networking problem here.

He is running 2 separate subnets within the same LAN environment.
IE:
192.168.1.X
192.186.2.X

These by default do not communicate together, so he has to create a link or pipeline between the two to communicate.

Spoiler (Click to View)

They did also say on 2 different networks in their last reply....

So not sure...

[Armada]

They did also say on 2 different networks in their last reply....

So not sure...

Shit did not notice that lol

Ignore IP tables and deal with proper port forwarding then 😧

[Asdethprime]

I am trying to ping between 2 different computers on 2 different subnets and 2 different networks...

There are few things that has to be at play here:
1) The 2 different network need to have a LAN connection, with 2 routers/switches talking to each other.
2) You would need both the public IP and the internal IP of the router.

Only after that you will be able to ping a computer outside your network.

The reason you need a public IP is quite simple, computer on different networks have the same IP address.

The IP address of my switch is the same as yours. 192.168.0.1

This is the same IP address, anyone on a internal network would use to connect to their wifi box.

If you only give internal IP address the router will not be able to figure out where to send the packet.

Also could you type in the IP address of the 2 routers? Don't worry these are going to be internal IP. If the IP address of the 2 routers happen to be different then you will be able to follow the link you posted. If it's not you would need the public IP.

[Noobface80]

I need to ping from PC A to PC B.
Thanks Fam!

[Armada]

There are few things that has to be at play here:
1) The 2 different network need to have a LAN connection, with 2 routers/switches talking to each other.
2) You would need both the public IP and the internal IP of the router.

Only after that you will be able to ping a computer outside your network.

The reason you need a public IP is quite simple, computer on different networks have the same IP address.

The IP address of my switch is the same as yours. 192.168.0.1

This is the same IP address, anyone on a internal network would use to connect to their wifi box.

If you only give internal IP address the router will not be able to figure out where to send the packet.

Also could you type in the IP address of the 2 routers? Don't worry these are going to be internal IP. If the IP address of the 2 routers happen to be different then you will be able to follow the link you posted. If it's not you would need the public IP.

Technically inaccurate.
Only the Client machine (Machine he is trying to ping) needs its proper ports forwarded to the internal subnet and internal IP# and then network communication is no problem.

[Asdethprime]

Only the Client machine (Machine he is trying to ping) needs its proper ports forwarded to the internal subnet and internal IP# and then network communication is no problem.

How would that allow him, from a completely different network, to proble the client.

He can't reach the client directly what he is reaching is the switch/hub that runs the given subnet. Client forwarding port port to internal subnet would only allows a physically connected subnet to interact with him or once the packet reaches the switch to be forwarded to right direction. To reach the switch which will not be a differnet IP than the sending switch would need a public IP, no?

Remember, the attacker PC (lets just call him that) is on an entirely different network reachable only through the Internet. Without a public IP address how is port forwarding going to help?

Also you seem to be ignoring the fact that both the internal network will have same IP addresses. The IP address of your switch 192.168.0.1 is not unique outside your network. Since both client and attackers are on different network port forwarding won't work on its own.

---

I need to ping from PC A to PC B.
Thanks Fam!

Ping the public IP address of switch.

[Armada]

How would that allow him, from a completely different network, to proble the client.

He can't reach the client directly what he is reaching is the switch/hub that runs the given subnet. Client forwarding port port to internal subnet would only allows a physically connected subnet to interact with him or once the packet reaches the switch to be forwarded to right direction. To reach the switch which will not be a differnet IP than the sending switch would need a public IP, no?

Remember, the attacker PC (lets just call him that) is on an entirely different network reachable only through the Internet. Without a public IP address how is port forwarding going to help?

Also you seem to be ignoring the fact that both the internal network will have same IP addresses. The IP address of your switch 192.168.0.1 is not unique outside your network. Since both client and attackers are on different network port forwarding won't work on its own.

Perhaps take some basic networking classes?
Re-read what I stated.

The Residing machine and network need to have the port forwarding enabled to allow outside traffic to be directed to the other machines internal IP#. 🤦‍♂

---

I need to ping from PC A to PC B.
Thanks Fam!

Perfect example.

So Router Y needs to open ports and Forwards to PC B accordingly through the routers port forwarding settings. Voila 👍

Edit: Quick testing of ports of PC B is easily done from canyouseeme.org as well :)

[Asdethprime]

Perhaps take some basic networking classes?
Re-read what I stated.

The Residing machine and network need to have the port forwarding enabled to allow outside traffic to be directed to the other machines internal IP#.

---

Perfect example.

So Router Y needs to open ports and Forwards to PC B accordingly through the routers port forwarding settings. Voila 👍

Edit: Quick testing of ports of PC B is easily done from canyouseeme.org as well :)

I am still confused to what you are talking about.

Router Y in this case need to open a port to reach PC B. If it does not do so all you would be pinging is Router Y and not PC B. That much I agree, never disagreed that.

Router Y however is in a completely different network that yours and as such you can't open a port from Router Y or anything. Because, Router Y is not a router you can control.

So again, you would need the public IP (which is what I have said) and the router Y router X needs to be talking.

You were the one who came in saying "technically inaccurate". I am just wondering can you actually show me anything in my post that is "technically inaccurate" rather than simply a 🤦‍♂ ?