Can't ping to computer but reverse ping can
So Computer 1 can ping to computer 2 but reverse it can't
Setup:
Router A (192.168.0.xxx) 255.255.255.0 > Router B (192.168.1.xxx) 255.255.255.0
So computer1 on Router B can ping to computer2 on router A but reverse can't.
Router B has a static IP adress (192.168.0.xxx).
Windows firewalls on both PC's are off. On both of the routers as well.
Can someone help?
windows internet ping subnet ipv4
edited Jul 4 '16 at 9:49
Karlo
5162621
asked Sep 26 '14 at 20:25
KhiemKhiem
112
add a comment |
So Computer 1 can ping to computer 2 but reverse it can't
Setup:
Router A (192.168.0.xxx) 255.255.255.0 > Router B (192.168.1.xxx) 255.255.255.0
So computer1 on Router B can ping to computer2 on router A but reverse can't.
Router B has a static IP adress (192.168.0.xxx).
Windows firewalls on both PC's are off. On both of the routers as well.
Can someone help?
windows internet ping subnet ipv4
edited Jul 4 '16 at 9:49
Karlo
5162621
asked Sep 26 '14 at 20:25
KhiemKhiem
112
192.168.x.x is a local/private IP address; your routers have NAT - en.wikipedia.org/wiki/Network_address_translation - separating you from the rest of the world... you'd need to port forward for ping to a machine behind NAT to work, otherwise only the router itself would even possibly respond, & not to a 192.168.x.x ping
– Tetsujin
Sep 26 '14 at 20:48
I don't get it, both routers are on the same network. I'm trying to ping computer1 to computer2 on the same network ?
– Khiem
Sep 26 '14 at 20:52
check for ICMP block in system are you using windows or linux?
– Lucas Tabares
Sep 26 '14 at 21:04
add a comment |
So Computer 1 can ping to computer 2 but reverse it can't
Setup:
Router A (192.168.0.xxx) 255.255.255.0 > Router B (192.168.1.xxx) 255.255.255.0
So computer1 on Router B can ping to computer2 on router A but reverse can't.
Router B has a static IP adress (192.168.0.xxx).
Windows firewalls on both PC's are off. On both of the routers as well.
Can someone help?
windows internet ping subnet ipv4
edited Jul 4 '16 at 9:49
Karlo
5162621
asked Sep 26 '14 at 20:25
KhiemKhiem
112
So Computer 1 can ping to computer 2 but reverse it can't
Setup:
Router A (192.168.0.xxx) 255.255.255.0 > Router B (192.168.1.xxx) 255.255.255.0
So computer1 on Router B can ping to computer2 on router A but reverse can't.
Router B has a static IP adress (192.168.0.xxx).
Windows firewalls on both PC's are off. On both of the routers as well.
Can someone help?
windows internet ping subnet ipv4
windows internet ping subnet ipv4
edited Jul 4 '16 at 9:49
Karlo
5162621
asked Sep 26 '14 at 20:25
KhiemKhiem
112
edited Jul 4 '16 at 9:49
Karlo
5162621
asked Sep 26 '14 at 20:25
KhiemKhiem
112
edited Jul 4 '16 at 9:49
Karlo
5162621
edited Jul 4 '16 at 9:49
Karlo
5162621
edited Jul 4 '16 at 9:49
Karlo
5162621
5162621
asked Sep 26 '14 at 20:25
KhiemKhiem
112
asked Sep 26 '14 at 20:25
KhiemKhiem
112
asked Sep 26 '14 at 20:25
KhiemKhiem
112
112
192.168.x.x is a local/private IP address; your routers have NAT - en.wikipedia.org/wiki/Network_address_translation - separating you from the rest of the world... you'd need to port forward for ping to a machine behind NAT to work, otherwise only the router itself would even possibly respond, & not to a 192.168.x.x ping
– Tetsujin
Sep 26 '14 at 20:48
I don't get it, both routers are on the same network. I'm trying to ping computer1 to computer2 on the same network ?
– Khiem
Sep 26 '14 at 20:52
check for ICMP block in system are you using windows or linux?
– Lucas Tabares
Sep 26 '14 at 21:04
add a comment |
192.168.x.x is a local/private IP address; your routers have NAT - en.wikipedia.org/wiki/Network_address_translation - separating you from the rest of the world... you'd need to port forward for ping to a machine behind NAT to work, otherwise only the router itself would even possibly respond, & not to a 192.168.x.x ping
– Tetsujin
Sep 26 '14 at 20:48
I don't get it, both routers are on the same network. I'm trying to ping computer1 to computer2 on the same network ?
– Khiem
Sep 26 '14 at 20:52
check for ICMP block in system are you using windows or linux?
– Lucas Tabares
Sep 26 '14 at 21:04
192.168.x.x is a local/private IP address; your routers have NAT - en.wikipedia.org/wiki/Network_address_translation - separating you from the rest of the world... you'd need to port forward for ping to a machine behind NAT to work, otherwise only the router itself would even possibly respond, & not to a 192.168.x.x ping
– Tetsujin
Sep 26 '14 at 20:48
192.168.x.x is a local/private IP address; your routers have NAT - en.wikipedia.org/wiki/Network_address_translation - separating you from the rest of the world... you'd need to port forward for ping to a machine behind NAT to work, otherwise only the router itself would even possibly respond, & not to a 192.168.x.x ping
– Tetsujin
Sep 26 '14 at 20:48
I don't get it, both routers are on the same network. I'm trying to ping computer1 to computer2 on the same network ?
– Khiem
Sep 26 '14 at 20:52
I don't get it, both routers are on the same network. I'm trying to ping computer1 to computer2 on the same network ?
– Khiem
Sep 26 '14 at 20:52
check for ICMP block in system are you using windows or linux?
– Lucas Tabares
Sep 26 '14 at 21:04
check for ICMP block in system are you using windows or linux?
– Lucas Tabares
Sep 26 '14 at 21:04
add a comment |
1 Answer
1
active
oldest
votes
In order to allow computers in the 192.168.0.x LAN to ping computers in the 192.168.1.x LAN, routerB must be configured to forward ICMP traffic between its WAN and LAN.
To do this, go to portforward.com, and search for instructions by routerB's model number. they have instructions for most common router models. configure routerB's NAT to allow ICMP echo packets, and you should then be able to ping inbound to routerB's LAN.
To understand whats happening, you must first understand that your computers are not on the same LAN, so in order to ping each other, routerB must pass the traffic between them. Your router however, sounds like a standard home/small-office router, which implements a pair of technologies called Stateful Packet Inspection, and Network Address Translation.
Every router has at least two networks, its inside (LAN), and its outside (WAN; everything outside the LAN, from its perspective). from routerA's perspective, its WAN is your ISPs network and the Internet at large, and its LAN is everything in the 192.168.0.x/24 network. routerB's LAN is the 192.168.1.x/24 network, and its WAN is routerA's LAN, the ISP netowrk, and everything else outside its LAN. So computers in routerA's LAN are in routerB's WAN.
NAT and SPI generally allow all hosts inside the LAN to connect to computers on the outside, and receive responses to those connections, but it prevents a computer on the WAN from initiating a connection to a computer on the LAN. This is why you can ping from 192.168.1.x (routerB's LAN) outward to 192.168.0.x(routerA's LAN and routerB's WAN). It is also why a computer in the routerB's WAN cannot connect inbound to a computer in routerB's LAN. You can however create a forwarding rule in NAT that allows specific types of connections to pass through the SPI, and initiate connections on the inside.
see more info here: http://en.wikipedia.org/wiki/Port_forwarding
answered Sep 26 '14 at 21:14
Frank ThomasFrank Thomas
27.4k25982
Cant really find it, Router B is Linksys E1000
– Khiem
Sep 26 '14 at 21:53
portforward.com/english/routers/port_forwarding/Linksys/…
– Frank Thomas
Sep 26 '14 at 22:06
It looks like your router does not support port forwarding for ICMP applications, so use this guide: ehow.com/how_8504133_enable-wan-ping-linksys-router.html
– Frank Thomas
Sep 26 '14 at 22:12
That was already unchecked ... what now ..
– Khiem
Sep 26 '14 at 22:20
on the same page disable SPI firewall. that MAY allow pings. ultimately, since your router is in the middle of the LAN, its safe to disable the firewall, but most routers don't give you the option to do so completely. better yet to use Bridge mode, but it doesn't look like your router supports that either. you may be able to cascade however: kb.linksys.com/Linksys/…
– Frank Thomas
Sep 27 '14 at 0:21
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f817331%2fcant-ping-to-computer-but-reverse-ping-can%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
In order to allow computers in the 192.168.0.x LAN to ping computers in the 192.168.1.x LAN, routerB must be configured to forward ICMP traffic between its WAN and LAN.
To do this, go to portforward.com, and search for instructions by routerB's model number. they have instructions for most common router models. configure routerB's NAT to allow ICMP echo packets, and you should then be able to ping inbound to routerB's LAN.
To understand whats happening, you must first understand that your computers are not on the same LAN, so in order to ping each other, routerB must pass the traffic between them. Your router however, sounds like a standard home/small-office router, which implements a pair of technologies called Stateful Packet Inspection, and Network Address Translation.
Every router has at least two networks, its inside (LAN), and its outside (WAN; everything outside the LAN, from its perspective). from routerA's perspective, its WAN is your ISPs network and the Internet at large, and its LAN is everything in the 192.168.0.x/24 network. routerB's LAN is the 192.168.1.x/24 network, and its WAN is routerA's LAN, the ISP netowrk, and everything else outside its LAN. So computers in routerA's LAN are in routerB's WAN.
NAT and SPI generally allow all hosts inside the LAN to connect to computers on the outside, and receive responses to those connections, but it prevents a computer on the WAN from initiating a connection to a computer on the LAN. This is why you can ping from 192.168.1.x (routerB's LAN) outward to 192.168.0.x(routerA's LAN and routerB's WAN). It is also why a computer in the routerB's WAN cannot connect inbound to a computer in routerB's LAN. You can however create a forwarding rule in NAT that allows specific types of connections to pass through the SPI, and initiate connections on the inside.
see more info here: http://en.wikipedia.org/wiki/Port_forwarding
answered Sep 26 '14 at 21:14
Frank ThomasFrank Thomas
27.4k25982
Cant really find it, Router B is Linksys E1000
– Khiem
Sep 26 '14 at 21:53
portforward.com/english/routers/port_forwarding/Linksys/…
– Frank Thomas
Sep 26 '14 at 22:06
It looks like your router does not support port forwarding for ICMP applications, so use this guide: ehow.com/how_8504133_enable-wan-ping-linksys-router.html
– Frank Thomas
Sep 26 '14 at 22:12
That was already unchecked ... what now ..
– Khiem
Sep 26 '14 at 22:20
on the same page disable SPI firewall. that MAY allow pings. ultimately, since your router is in the middle of the LAN, its safe to disable the firewall, but most routers don't give you the option to do so completely. better yet to use Bridge mode, but it doesn't look like your router supports that either. you may be able to cascade however: kb.linksys.com/Linksys/…
– Frank Thomas
Sep 27 '14 at 0:21
add a comment |
In order to allow computers in the 192.168.0.x LAN to ping computers in the 192.168.1.x LAN, routerB must be configured to forward ICMP traffic between its WAN and LAN.
To do this, go to portforward.com, and search for instructions by routerB's model number. they have instructions for most common router models. configure routerB's NAT to allow ICMP echo packets, and you should then be able to ping inbound to routerB's LAN.
To understand whats happening, you must first understand that your computers are not on the same LAN, so in order to ping each other, routerB must pass the traffic between them. Your router however, sounds like a standard home/small-office router, which implements a pair of technologies called Stateful Packet Inspection, and Network Address Translation.
Every router has at least two networks, its inside (LAN), and its outside (WAN; everything outside the LAN, from its perspective). from routerA's perspective, its WAN is your ISPs network and the Internet at large, and its LAN is everything in the 192.168.0.x/24 network. routerB's LAN is the 192.168.1.x/24 network, and its WAN is routerA's LAN, the ISP netowrk, and everything else outside its LAN. So computers in routerA's LAN are in routerB's WAN.
NAT and SPI generally allow all hosts inside the LAN to connect to computers on the outside, and receive responses to those connections, but it prevents a computer on the WAN from initiating a connection to a computer on the LAN. This is why you can ping from 192.168.1.x (routerB's LAN) outward to 192.168.0.x(routerA's LAN and routerB's WAN). It is also why a computer in the routerB's WAN cannot connect inbound to a computer in routerB's LAN. You can however create a forwarding rule in NAT that allows specific types of connections to pass through the SPI, and initiate connections on the inside.
see more info here: http://en.wikipedia.org/wiki/Port_forwarding
answered Sep 26 '14 at 21:14
Frank ThomasFrank Thomas
27.4k25982
Cant really find it, Router B is Linksys E1000
– Khiem
Sep 26 '14 at 21:53
portforward.com/english/routers/port_forwarding/Linksys/…
– Frank Thomas
Sep 26 '14 at 22:06
It looks like your router does not support port forwarding for ICMP applications, so use this guide: ehow.com/how_8504133_enable-wan-ping-linksys-router.html
– Frank Thomas
Sep 26 '14 at 22:12
That was already unchecked ... what now ..
– Khiem
Sep 26 '14 at 22:20
on the same page disable SPI firewall. that MAY allow pings. ultimately, since your router is in the middle of the LAN, its safe to disable the firewall, but most routers don't give you the option to do so completely. better yet to use Bridge mode, but it doesn't look like your router supports that either. you may be able to cascade however: kb.linksys.com/Linksys/…
– Frank Thomas
Sep 27 '14 at 0:21
add a comment |
In order to allow computers in the 192.168.0.x LAN to ping computers in the 192.168.1.x LAN, routerB must be configured to forward ICMP traffic between its WAN and LAN.
To do this, go to portforward.com, and search for instructions by routerB's model number. they have instructions for most common router models. configure routerB's NAT to allow ICMP echo packets, and you should then be able to ping inbound to routerB's LAN.
To understand whats happening, you must first understand that your computers are not on the same LAN, so in order to ping each other, routerB must pass the traffic between them. Your router however, sounds like a standard home/small-office router, which implements a pair of technologies called Stateful Packet Inspection, and Network Address Translation.
Every router has at least two networks, its inside (LAN), and its outside (WAN; everything outside the LAN, from its perspective). from routerA's perspective, its WAN is your ISPs network and the Internet at large, and its LAN is everything in the 192.168.0.x/24 network. routerB's LAN is the 192.168.1.x/24 network, and its WAN is routerA's LAN, the ISP netowrk, and everything else outside its LAN. So computers in routerA's LAN are in routerB's WAN.
NAT and SPI generally allow all hosts inside the LAN to connect to computers on the outside, and receive responses to those connections, but it prevents a computer on the WAN from initiating a connection to a computer on the LAN. This is why you can ping from 192.168.1.x (routerB's LAN) outward to 192.168.0.x(routerA's LAN and routerB's WAN). It is also why a computer in the routerB's WAN cannot connect inbound to a computer in routerB's LAN. You can however create a forwarding rule in NAT that allows specific types of connections to pass through the SPI, and initiate connections on the inside.
see more info here: http://en.wikipedia.org/wiki/Port_forwarding
answered Sep 26 '14 at 21:14
Frank ThomasFrank Thomas
27.4k25982
In order to allow computers in the 192.168.0.x LAN to ping computers in the 192.168.1.x LAN, routerB must be configured to forward ICMP traffic between its WAN and LAN.
To do this, go to portforward.com, and search for instructions by routerB's model number. they have instructions for most common router models. configure routerB's NAT to allow ICMP echo packets, and you should then be able to ping inbound to routerB's LAN.
To understand whats happening, you must first understand that your computers are not on the same LAN, so in order to ping each other, routerB must pass the traffic between them. Your router however, sounds like a standard home/small-office router, which implements a pair of technologies called Stateful Packet Inspection, and Network Address Translation.
Every router has at least two networks, its inside (LAN), and its outside (WAN; everything outside the LAN, from its perspective). from routerA's perspective, its WAN is your ISPs network and the Internet at large, and its LAN is everything in the 192.168.0.x/24 network. routerB's LAN is the 192.168.1.x/24 network, and its WAN is routerA's LAN, the ISP netowrk, and everything else outside its LAN. So computers in routerA's LAN are in routerB's WAN.
NAT and SPI generally allow all hosts inside the LAN to connect to computers on the outside, and receive responses to those connections, but it prevents a computer on the WAN from initiating a connection to a computer on the LAN. This is why you can ping from 192.168.1.x (routerB's LAN) outward to 192.168.0.x(routerA's LAN and routerB's WAN). It is also why a computer in the routerB's WAN cannot connect inbound to a computer in routerB's LAN. You can however create a forwarding rule in NAT that allows specific types of connections to pass through the SPI, and initiate connections on the inside.
see more info here: http://en.wikipedia.org/wiki/Port_forwarding
answered Sep 26 '14 at 21:14
Frank ThomasFrank Thomas
27.4k25982
edited Sep 26 '14 at 21:52
answered Sep 26 '14 at 21:14
Frank ThomasFrank Thomas
27.4k25982
answered Sep 26 '14 at 21:14
Frank ThomasFrank Thomas
27.4k25982
answered Sep 26 '14 at 21:14
Frank ThomasFrank Thomas
27.4k25982
27.4k25982
Cant really find it, Router B is Linksys E1000
– Khiem
Sep 26 '14 at 21:53
portforward.com/english/routers/port_forwarding/Linksys/…
– Frank Thomas
Sep 26 '14 at 22:06
It looks like your router does not support port forwarding for ICMP applications, so use this guide: ehow.com/how_8504133_enable-wan-ping-linksys-router.html
– Frank Thomas
Sep 26 '14 at 22:12
That was already unchecked ... what now ..
– Khiem
Sep 26 '14 at 22:20
on the same page disable SPI firewall. that MAY allow pings. ultimately, since your router is in the middle of the LAN, its safe to disable the firewall, but most routers don't give you the option to do so completely. better yet to use Bridge mode, but it doesn't look like your router supports that either. you may be able to cascade however: kb.linksys.com/Linksys/…
– Frank Thomas
Sep 27 '14 at 0:21
add a comment |
Cant really find it, Router B is Linksys E1000
– Khiem
Sep 26 '14 at 21:53
portforward.com/english/routers/port_forwarding/Linksys/…
– Frank Thomas
Sep 26 '14 at 22:06
It looks like your router does not support port forwarding for ICMP applications, so use this guide: ehow.com/how_8504133_enable-wan-ping-linksys-router.html
– Frank Thomas
Sep 26 '14 at 22:12
That was already unchecked ... what now ..
– Khiem
Sep 26 '14 at 22:20
on the same page disable SPI firewall. that MAY allow pings. ultimately, since your router is in the middle of the LAN, its safe to disable the firewall, but most routers don't give you the option to do so completely. better yet to use Bridge mode, but it doesn't look like your router supports that either. you may be able to cascade however: kb.linksys.com/Linksys/…
– Frank Thomas
Sep 27 '14 at 0:21
Cant really find it, Router B is Linksys E1000
– Khiem
Sep 26 '14 at 21:53
Cant really find it, Router B is Linksys E1000
– Khiem
Sep 26 '14 at 21:53
portforward.com/english/routers/port_forwarding/Linksys/…
– Frank Thomas
Sep 26 '14 at 22:06
portforward.com/english/routers/port_forwarding/Linksys/…
– Frank Thomas
Sep 26 '14 at 22:06
It looks like your router does not support port forwarding for ICMP applications, so use this guide: ehow.com/how_8504133_enable-wan-ping-linksys-router.html
– Frank Thomas
Sep 26 '14 at 22:12
It looks like your router does not support port forwarding for ICMP applications, so use this guide: ehow.com/how_8504133_enable-wan-ping-linksys-router.html
– Frank Thomas
Sep 26 '14 at 22:12
That was already unchecked ... what now ..
– Khiem
Sep 26 '14 at 22:20
That was already unchecked ... what now ..
– Khiem
Sep 26 '14 at 22:20
on the same page disable SPI firewall. that MAY allow pings. ultimately, since your router is in the middle of the LAN, its safe to disable the firewall, but most routers don't give you the option to do so completely. better yet to use Bridge mode, but it doesn't look like your router supports that either. you may be able to cascade however: kb.linksys.com/Linksys/…
– Frank Thomas
Sep 27 '14 at 0:21
on the same page disable SPI firewall. that MAY allow pings. ultimately, since your router is in the middle of the LAN, its safe to disable the firewall, but most routers don't give you the option to do so completely. better yet to use Bridge mode, but it doesn't look like your router supports that either. you may be able to cascade however: kb.linksys.com/Linksys/…
– Frank Thomas
Sep 27 '14 at 0:21
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f817331%2fcant-ping-to-computer-but-reverse-ping-can%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
192.168.x.x is a local/private IP address; your routers have NAT - en.wikipedia.org/wiki/Network_address_translation - separating you from the rest of the world... you'd need to port forward for ping to a machine behind NAT to work, otherwise only the router itself would even possibly respond, & not to a 192.168.x.x ping
– Tetsujin
Sep 26 '14 at 20:48
I don't get it, both routers are on the same network. I'm trying to ping computer1 to computer2 on the same network ?
– Khiem
Sep 26 '14 at 20:52
check for ICMP block in system are you using windows or linux?
– Lucas Tabares
Sep 26 '14 at 21:04