192.168.1.xxx devices cannot ping to 192.168.0.xxx with same subnet mask 255.255.255.0
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I am not a network person but do take care of a church's network. Now we need to setup a NAS file server that needs to be accessible by all 192.168.1.xxx devices.
Since the Netgear WNDR800 router owned by the church has all 4 LAN ports used up, so I hook up the server to 1 of the 3 empty LAN ports for the TPLink Router (green in attachedenter image description here) that is supplied by the ISP (need to return to the ISP once no more buying Internet service from them).
The server get an IP 192.168.0.xxx once hooked to TPLink but all church owned devices with IP 192.168.1.xxx cannot communicate with this server. I am not sure what's missing.
networking ip-address
asked Jan 29 at 14:59
Rita LiRita Li
32
add a comment |
I am not a network person but do take care of a church's network. Now we need to setup a NAS file server that needs to be accessible by all 192.168.1.xxx devices.
Since the Netgear WNDR800 router owned by the church has all 4 LAN ports used up, so I hook up the server to 1 of the 3 empty LAN ports for the TPLink Router (green in attachedenter image description here) that is supplied by the ISP (need to return to the ISP once no more buying Internet service from them).
The server get an IP 192.168.0.xxx once hooked to TPLink but all church owned devices with IP 192.168.1.xxx cannot communicate with this server. I am not sure what's missing.
networking ip-address
asked Jan 29 at 14:59
Rita LiRita Li
32
"The server get an IP 192.168.0.xxx" - By Server do you mean NAS? It sounds as if the default gateway in the NAS is preset, so I would advise digging out the NAS manual to determine how to edit the default gateway value to 192.168.1.xxx
– spikey_richie
Jan 29 at 15:20
You have the WAN port on the WNDR3800 connected to the LAN port on the TPLink router. Similarly, you have the TPLink router's WAN port connected to the Fiber Router's LAN port. This creates a confusing combination of multiple LANs that is completely unnecessary and counterproductive. You should have one LAN unless there are good grounds for separation and the consequences of such separation are well understood.
– David Schwartz
Jan 29 at 18:58
The fiber router and the TPLink router belong to the ISP that I cannot manage, ISP tech people come in and set these 2 devices up then use a LAN cable to connect from the TPLink router LAN port to the church owned Netgear WNDR3800 WAN port while we changed the service requesting for fiber connection
– Rita Li
Jan 30 at 11:36
add a comment |
I am not a network person but do take care of a church's network. Now we need to setup a NAS file server that needs to be accessible by all 192.168.1.xxx devices.
Since the Netgear WNDR800 router owned by the church has all 4 LAN ports used up, so I hook up the server to 1 of the 3 empty LAN ports for the TPLink Router (green in attachedenter image description here) that is supplied by the ISP (need to return to the ISP once no more buying Internet service from them).
The server get an IP 192.168.0.xxx once hooked to TPLink but all church owned devices with IP 192.168.1.xxx cannot communicate with this server. I am not sure what's missing.
networking ip-address
asked Jan 29 at 14:59
Rita LiRita Li
32
I am not a network person but do take care of a church's network. Now we need to setup a NAS file server that needs to be accessible by all 192.168.1.xxx devices.
Since the Netgear WNDR800 router owned by the church has all 4 LAN ports used up, so I hook up the server to 1 of the 3 empty LAN ports for the TPLink Router (green in attachedenter image description here) that is supplied by the ISP (need to return to the ISP once no more buying Internet service from them).
The server get an IP 192.168.0.xxx once hooked to TPLink but all church owned devices with IP 192.168.1.xxx cannot communicate with this server. I am not sure what's missing.
networking ip-address
networking ip-address
asked Jan 29 at 14:59
Rita LiRita Li
32
asked Jan 29 at 14:59
Rita LiRita Li
32
asked Jan 29 at 14:59
Rita LiRita Li
32
asked Jan 29 at 14:59
Rita LiRita Li
32
asked Jan 29 at 14:59
Rita LiRita Li
32
32
"The server get an IP 192.168.0.xxx" - By Server do you mean NAS? It sounds as if the default gateway in the NAS is preset, so I would advise digging out the NAS manual to determine how to edit the default gateway value to 192.168.1.xxx
– spikey_richie
Jan 29 at 15:20
You have the WAN port on the WNDR3800 connected to the LAN port on the TPLink router. Similarly, you have the TPLink router's WAN port connected to the Fiber Router's LAN port. This creates a confusing combination of multiple LANs that is completely unnecessary and counterproductive. You should have one LAN unless there are good grounds for separation and the consequences of such separation are well understood.
– David Schwartz
Jan 29 at 18:58
The fiber router and the TPLink router belong to the ISP that I cannot manage, ISP tech people come in and set these 2 devices up then use a LAN cable to connect from the TPLink router LAN port to the church owned Netgear WNDR3800 WAN port while we changed the service requesting for fiber connection
– Rita Li
Jan 30 at 11:36
add a comment |
"The server get an IP 192.168.0.xxx" - By Server do you mean NAS? It sounds as if the default gateway in the NAS is preset, so I would advise digging out the NAS manual to determine how to edit the default gateway value to 192.168.1.xxx
– spikey_richie
Jan 29 at 15:20
You have the WAN port on the WNDR3800 connected to the LAN port on the TPLink router. Similarly, you have the TPLink router's WAN port connected to the Fiber Router's LAN port. This creates a confusing combination of multiple LANs that is completely unnecessary and counterproductive. You should have one LAN unless there are good grounds for separation and the consequences of such separation are well understood.
– David Schwartz
Jan 29 at 18:58
The fiber router and the TPLink router belong to the ISP that I cannot manage, ISP tech people come in and set these 2 devices up then use a LAN cable to connect from the TPLink router LAN port to the church owned Netgear WNDR3800 WAN port while we changed the service requesting for fiber connection
– Rita Li
Jan 30 at 11:36
"The server get an IP 192.168.0.xxx" - By Server do you mean NAS? It sounds as if the default gateway in the NAS is preset, so I would advise digging out the NAS manual to determine how to edit the default gateway value to 192.168.1.xxx
– spikey_richie
Jan 29 at 15:20
"The server get an IP 192.168.0.xxx" - By Server do you mean NAS? It sounds as if the default gateway in the NAS is preset, so I would advise digging out the NAS manual to determine how to edit the default gateway value to 192.168.1.xxx
– spikey_richie
Jan 29 at 15:20
You have the WAN port on the WNDR3800 connected to the LAN port on the TPLink router. Similarly, you have the TPLink router's WAN port connected to the Fiber Router's LAN port. This creates a confusing combination of multiple LANs that is completely unnecessary and counterproductive. You should have one LAN unless there are good grounds for separation and the consequences of such separation are well understood.
– David Schwartz
Jan 29 at 18:58
You have the WAN port on the WNDR3800 connected to the LAN port on the TPLink router. Similarly, you have the TPLink router's WAN port connected to the Fiber Router's LAN port. This creates a confusing combination of multiple LANs that is completely unnecessary and counterproductive. You should have one LAN unless there are good grounds for separation and the consequences of such separation are well understood.
– David Schwartz
Jan 29 at 18:58
The fiber router and the TPLink router belong to the ISP that I cannot manage, ISP tech people come in and set these 2 devices up then use a LAN cable to connect from the TPLink router LAN port to the church owned Netgear WNDR3800 WAN port while we changed the service requesting for fiber connection
– Rita Li
Jan 30 at 11:36
The fiber router and the TPLink router belong to the ISP that I cannot manage, ISP tech people come in and set these 2 devices up then use a LAN cable to connect from the TPLink router LAN port to the church owned Netgear WNDR3800 WAN port while we changed the service requesting for fiber connection
– Rita Li
Jan 30 at 11:36
add a comment |
1 Answer
1
active
oldest
votes
A Router creates a new network for all LAN ports and redirects traffic based on NAT rules to the WAN port.
Because your situation has 2 routers, you have 2 different networks. Because one router is connected to the wan port of another router, these networks are shielded from eachother. You can do a lot with portforwarding, but unfortunately not enough.
What you need to do is buy a network switch to extend the amount of ports from the netgear router. You unplug one network cable from the netgear router, plug the switch into it, and plug the removed cable back into the switch. You then plugin the NAS into another free LAN port on the switch.
If you have another router laying around, you can use it as a switch, as long as you don't use the WAN port. Unfortunately for your situation, you cannot change the Netgear router to accomodate this because that means you have to do all the configuration through the TP Link switch, which you don't manage.
answered Jan 29 at 18:18
LPChipLPChip
36.8k55588
You are correct that I cannot manage the TPLink router loaned from the ISP since we are not given the admin password for this router. I also think installing a network switch to the Netgear router to give more ports should fix the problem but I can't explain why & glad that you shed the light what is the reason behind. Thanks
– Rita Li
Jan 30 at 16:09
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%2f1399684%2f192-168-1-xxx-devices-cannot-ping-to-192-168-0-xxx-with-same-subnet-mask-255-255%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
A Router creates a new network for all LAN ports and redirects traffic based on NAT rules to the WAN port.
Because your situation has 2 routers, you have 2 different networks. Because one router is connected to the wan port of another router, these networks are shielded from eachother. You can do a lot with portforwarding, but unfortunately not enough.
What you need to do is buy a network switch to extend the amount of ports from the netgear router. You unplug one network cable from the netgear router, plug the switch into it, and plug the removed cable back into the switch. You then plugin the NAS into another free LAN port on the switch.
If you have another router laying around, you can use it as a switch, as long as you don't use the WAN port. Unfortunately for your situation, you cannot change the Netgear router to accomodate this because that means you have to do all the configuration through the TP Link switch, which you don't manage.
answered Jan 29 at 18:18
LPChipLPChip
36.8k55588
You are correct that I cannot manage the TPLink router loaned from the ISP since we are not given the admin password for this router. I also think installing a network switch to the Netgear router to give more ports should fix the problem but I can't explain why & glad that you shed the light what is the reason behind. Thanks
– Rita Li
Jan 30 at 16:09
add a comment |
A Router creates a new network for all LAN ports and redirects traffic based on NAT rules to the WAN port.
Because your situation has 2 routers, you have 2 different networks. Because one router is connected to the wan port of another router, these networks are shielded from eachother. You can do a lot with portforwarding, but unfortunately not enough.
What you need to do is buy a network switch to extend the amount of ports from the netgear router. You unplug one network cable from the netgear router, plug the switch into it, and plug the removed cable back into the switch. You then plugin the NAS into another free LAN port on the switch.
If you have another router laying around, you can use it as a switch, as long as you don't use the WAN port. Unfortunately for your situation, you cannot change the Netgear router to accomodate this because that means you have to do all the configuration through the TP Link switch, which you don't manage.
answered Jan 29 at 18:18
LPChipLPChip
36.8k55588
You are correct that I cannot manage the TPLink router loaned from the ISP since we are not given the admin password for this router. I also think installing a network switch to the Netgear router to give more ports should fix the problem but I can't explain why & glad that you shed the light what is the reason behind. Thanks
– Rita Li
Jan 30 at 16:09
add a comment |
A Router creates a new network for all LAN ports and redirects traffic based on NAT rules to the WAN port.
Because your situation has 2 routers, you have 2 different networks. Because one router is connected to the wan port of another router, these networks are shielded from eachother. You can do a lot with portforwarding, but unfortunately not enough.
What you need to do is buy a network switch to extend the amount of ports from the netgear router. You unplug one network cable from the netgear router, plug the switch into it, and plug the removed cable back into the switch. You then plugin the NAS into another free LAN port on the switch.
If you have another router laying around, you can use it as a switch, as long as you don't use the WAN port. Unfortunately for your situation, you cannot change the Netgear router to accomodate this because that means you have to do all the configuration through the TP Link switch, which you don't manage.
answered Jan 29 at 18:18
LPChipLPChip
36.8k55588
A Router creates a new network for all LAN ports and redirects traffic based on NAT rules to the WAN port.
Because your situation has 2 routers, you have 2 different networks. Because one router is connected to the wan port of another router, these networks are shielded from eachother. You can do a lot with portforwarding, but unfortunately not enough.
What you need to do is buy a network switch to extend the amount of ports from the netgear router. You unplug one network cable from the netgear router, plug the switch into it, and plug the removed cable back into the switch. You then plugin the NAS into another free LAN port on the switch.
If you have another router laying around, you can use it as a switch, as long as you don't use the WAN port. Unfortunately for your situation, you cannot change the Netgear router to accomodate this because that means you have to do all the configuration through the TP Link switch, which you don't manage.
answered Jan 29 at 18:18
LPChipLPChip
36.8k55588
answered Jan 29 at 18:18
LPChipLPChip
36.8k55588
answered Jan 29 at 18:18
LPChipLPChip
36.8k55588
answered Jan 29 at 18:18
LPChipLPChip
36.8k55588
36.8k55588
You are correct that I cannot manage the TPLink router loaned from the ISP since we are not given the admin password for this router. I also think installing a network switch to the Netgear router to give more ports should fix the problem but I can't explain why & glad that you shed the light what is the reason behind. Thanks
– Rita Li
Jan 30 at 16:09
add a comment |
You are correct that I cannot manage the TPLink router loaned from the ISP since we are not given the admin password for this router. I also think installing a network switch to the Netgear router to give more ports should fix the problem but I can't explain why & glad that you shed the light what is the reason behind. Thanks
– Rita Li
Jan 30 at 16:09
You are correct that I cannot manage the TPLink router loaned from the ISP since we are not given the admin password for this router. I also think installing a network switch to the Netgear router to give more ports should fix the problem but I can't explain why & glad that you shed the light what is the reason behind. Thanks
– Rita Li
Jan 30 at 16:09
You are correct that I cannot manage the TPLink router loaned from the ISP since we are not given the admin password for this router. I also think installing a network switch to the Netgear router to give more ports should fix the problem but I can't explain why & glad that you shed the light what is the reason behind. Thanks
– Rita Li
Jan 30 at 16:09
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%2f1399684%2f192-168-1-xxx-devices-cannot-ping-to-192-168-0-xxx-with-same-subnet-mask-255-255%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
"The server get an IP 192.168.0.xxx" - By Server do you mean NAS? It sounds as if the default gateway in the NAS is preset, so I would advise digging out the NAS manual to determine how to edit the default gateway value to 192.168.1.xxx
– spikey_richie
Jan 29 at 15:20
You have the WAN port on the WNDR3800 connected to the LAN port on the TPLink router. Similarly, you have the TPLink router's WAN port connected to the Fiber Router's LAN port. This creates a confusing combination of multiple LANs that is completely unnecessary and counterproductive. You should have one LAN unless there are good grounds for separation and the consequences of such separation are well understood.
– David Schwartz
Jan 29 at 18:58
The fiber router and the TPLink router belong to the ISP that I cannot manage, ISP tech people come in and set these 2 devices up then use a LAN cable to connect from the TPLink router LAN port to the church owned Netgear WNDR3800 WAN port while we changed the service requesting for fiber connection
– Rita Li
Jan 30 at 11:36