Can connect to Port-Forwarded IP on my WiFi, but not any other network
I port-forwarded my external IP to my IPv4, and it works perfectly on my WiFi network, but if I change the active network on my device, I can't access it. I am for sure that both IPs are correct and it is not a Windows Firewall issue either. There are no other programs conflicting with it because I have just wiped the host computer. What can I do?
networking wireless-networking router port-forwarding
asked Mar 25 '16 at 5:26
132ikl
63
add a comment |
I port-forwarded my external IP to my IPv4, and it works perfectly on my WiFi network, but if I change the active network on my device, I can't access it. I am for sure that both IPs are correct and it is not a Windows Firewall issue either. There are no other programs conflicting with it because I have just wiped the host computer. What can I do?
networking wireless-networking router port-forwarding
asked Mar 25 '16 at 5:26
132ikl
63
add a comment |
I port-forwarded my external IP to my IPv4, and it works perfectly on my WiFi network, but if I change the active network on my device, I can't access it. I am for sure that both IPs are correct and it is not a Windows Firewall issue either. There are no other programs conflicting with it because I have just wiped the host computer. What can I do?
networking wireless-networking router port-forwarding
asked Mar 25 '16 at 5:26
132ikl
63
I port-forwarded my external IP to my IPv4, and it works perfectly on my WiFi network, but if I change the active network on my device, I can't access it. I am for sure that both IPs are correct and it is not a Windows Firewall issue either. There are no other programs conflicting with it because I have just wiped the host computer. What can I do?
networking wireless-networking router port-forwarding
networking wireless-networking router port-forwarding
asked Mar 25 '16 at 5:26
132ikl
63
asked Mar 25 '16 at 5:26
132ikl
63
edited Mar 25 '16 at 23:46
asked Mar 25 '16 at 5:26
132ikl
63
asked Mar 25 '16 at 5:26
132ikl
63
asked Mar 25 '16 at 5:26
132ikl
63
63
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
I think you are accessing your external ip from your local area network. You can't access your port forwarded external ip from inside. Port forwarding only for accessing from outside.
answered Mar 25 '16 at 6:11
vembutech
5,36611317
Does that mean my port forwarding isn't set up correctly? What can I do?
– 132ikl
Mar 25 '16 at 6:15
For checking your port forward setup is works or not, check from outside ( not from your LAN ), by telnet. If you portforwarded 8080, do telnet. Telnet yourstaticip 8080.
– vembutech
Mar 25 '16 at 6:21
I checked before, it didn't work.
– 132ikl
Mar 25 '16 at 6:30
If telnet not works for your externalstatic ip for the port, there must be issue in port forwarding setup. Double check in your firewall/router.
– vembutech
Mar 25 '16 at 6:33
Okay. I'll get back to you tomorrow.
– 132ikl
Mar 25 '16 at 6:34
add a comment |
Two issues you might be facing:
- I'm not sure what you mean by "another network". A port forwarding rule only exists for the router on which you defined it. So if you define a port forwarding rule on your router and then switch to another WiFi network, the rule will not work because your computer is no longer using the router where the rule is defined.
- A port forwarding rule is IP address specific and does not work well with DHCP. If you then connect your laptop using the Ethernet port, for example, then your internal IP address will be different and the rule won't work. Also, both your internal and external IP addresses may change at any time because of DHCP. You can control this on your internal network, but there's nothing you can do about your ISP's policy.
How to do it right:
- Always use DHCP reservations (if your router supports that feature) or static IPs on your computer. Give EACH interface on your computer a different address and make two identical port forwarding rules; one for each. This will eliminate the DHCP problem.
- Use a dynamic DNS service such as No-IP or DynDNS to map your external IP address to a DNS name. These services offer an agent that you download to your computer that will keep your public DNS record in sync with the IP address your ISP gives you, so you can always reference it by name from anywhere on the Internet. This will solve the ISP DHCP problem.
You will need to do this for each network you attach your laptop to (assuming you have control of those networks).
answered Mar 25 '16 at 21:52
Wes Sayeed
10.7k32758
add a comment |
I just had this same issue with the same router that you are using in your screenshot (or at least the same software). If you click "(more)" at the top of the screen you will see there is an option to leave the external ip as 0.0.0.0 to forward all external traffic and leave the external ports at 0 if you don't need to switch them in this process. This took me almost a year of on-and-off troubleshooting and hopefully it will help you. As soon as i found these options, it began working as expected from outside my home network as well as inside.
answered Dec 4 at 2:06
Scott
1
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%2f1057113%2fcan-connect-to-port-forwarded-ip-on-my-wifi-but-not-any-other-network%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
I think you are accessing your external ip from your local area network. You can't access your port forwarded external ip from inside. Port forwarding only for accessing from outside.
answered Mar 25 '16 at 6:11
vembutech
5,36611317
Does that mean my port forwarding isn't set up correctly? What can I do?
– 132ikl
Mar 25 '16 at 6:15
For checking your port forward setup is works or not, check from outside ( not from your LAN ), by telnet. If you portforwarded 8080, do telnet. Telnet yourstaticip 8080.
– vembutech
Mar 25 '16 at 6:21
I checked before, it didn't work.
– 132ikl
Mar 25 '16 at 6:30
If telnet not works for your externalstatic ip for the port, there must be issue in port forwarding setup. Double check in your firewall/router.
– vembutech
Mar 25 '16 at 6:33
Okay. I'll get back to you tomorrow.
– 132ikl
Mar 25 '16 at 6:34
add a comment |
I think you are accessing your external ip from your local area network. You can't access your port forwarded external ip from inside. Port forwarding only for accessing from outside.
answered Mar 25 '16 at 6:11
vembutech
5,36611317
Does that mean my port forwarding isn't set up correctly? What can I do?
– 132ikl
Mar 25 '16 at 6:15
For checking your port forward setup is works or not, check from outside ( not from your LAN ), by telnet. If you portforwarded 8080, do telnet. Telnet yourstaticip 8080.
– vembutech
Mar 25 '16 at 6:21
I checked before, it didn't work.
– 132ikl
Mar 25 '16 at 6:30
If telnet not works for your externalstatic ip for the port, there must be issue in port forwarding setup. Double check in your firewall/router.
– vembutech
Mar 25 '16 at 6:33
Okay. I'll get back to you tomorrow.
– 132ikl
Mar 25 '16 at 6:34
add a comment |
I think you are accessing your external ip from your local area network. You can't access your port forwarded external ip from inside. Port forwarding only for accessing from outside.
answered Mar 25 '16 at 6:11
vembutech
5,36611317
I think you are accessing your external ip from your local area network. You can't access your port forwarded external ip from inside. Port forwarding only for accessing from outside.
answered Mar 25 '16 at 6:11
vembutech
5,36611317
answered Mar 25 '16 at 6:11
vembutech
5,36611317
answered Mar 25 '16 at 6:11
vembutech
5,36611317
answered Mar 25 '16 at 6:11
vembutech
5,36611317
5,36611317
Does that mean my port forwarding isn't set up correctly? What can I do?
– 132ikl
Mar 25 '16 at 6:15
For checking your port forward setup is works or not, check from outside ( not from your LAN ), by telnet. If you portforwarded 8080, do telnet. Telnet yourstaticip 8080.
– vembutech
Mar 25 '16 at 6:21
I checked before, it didn't work.
– 132ikl
Mar 25 '16 at 6:30
If telnet not works for your externalstatic ip for the port, there must be issue in port forwarding setup. Double check in your firewall/router.
– vembutech
Mar 25 '16 at 6:33
Okay. I'll get back to you tomorrow.
– 132ikl
Mar 25 '16 at 6:34
add a comment |
Does that mean my port forwarding isn't set up correctly? What can I do?
– 132ikl
Mar 25 '16 at 6:15
For checking your port forward setup is works or not, check from outside ( not from your LAN ), by telnet. If you portforwarded 8080, do telnet. Telnet yourstaticip 8080.
– vembutech
Mar 25 '16 at 6:21
I checked before, it didn't work.
– 132ikl
Mar 25 '16 at 6:30
If telnet not works for your externalstatic ip for the port, there must be issue in port forwarding setup. Double check in your firewall/router.
– vembutech
Mar 25 '16 at 6:33
Okay. I'll get back to you tomorrow.
– 132ikl
Mar 25 '16 at 6:34
Does that mean my port forwarding isn't set up correctly? What can I do?
– 132ikl
Mar 25 '16 at 6:15
Does that mean my port forwarding isn't set up correctly? What can I do?
– 132ikl
Mar 25 '16 at 6:15
For checking your port forward setup is works or not, check from outside ( not from your LAN ), by telnet. If you portforwarded 8080, do telnet. Telnet yourstaticip 8080.
– vembutech
Mar 25 '16 at 6:21
For checking your port forward setup is works or not, check from outside ( not from your LAN ), by telnet. If you portforwarded 8080, do telnet. Telnet yourstaticip 8080.
– vembutech
Mar 25 '16 at 6:21
I checked before, it didn't work.
– 132ikl
Mar 25 '16 at 6:30
I checked before, it didn't work.
– 132ikl
Mar 25 '16 at 6:30
If telnet not works for your externalstatic ip for the port, there must be issue in port forwarding setup. Double check in your firewall/router.
– vembutech
Mar 25 '16 at 6:33
If telnet not works for your externalstatic ip for the port, there must be issue in port forwarding setup. Double check in your firewall/router.
– vembutech
Mar 25 '16 at 6:33
Okay. I'll get back to you tomorrow.
– 132ikl
Mar 25 '16 at 6:34
Okay. I'll get back to you tomorrow.
– 132ikl
Mar 25 '16 at 6:34
add a comment |
Two issues you might be facing:
- I'm not sure what you mean by "another network". A port forwarding rule only exists for the router on which you defined it. So if you define a port forwarding rule on your router and then switch to another WiFi network, the rule will not work because your computer is no longer using the router where the rule is defined.
- A port forwarding rule is IP address specific and does not work well with DHCP. If you then connect your laptop using the Ethernet port, for example, then your internal IP address will be different and the rule won't work. Also, both your internal and external IP addresses may change at any time because of DHCP. You can control this on your internal network, but there's nothing you can do about your ISP's policy.
How to do it right:
- Always use DHCP reservations (if your router supports that feature) or static IPs on your computer. Give EACH interface on your computer a different address and make two identical port forwarding rules; one for each. This will eliminate the DHCP problem.
- Use a dynamic DNS service such as No-IP or DynDNS to map your external IP address to a DNS name. These services offer an agent that you download to your computer that will keep your public DNS record in sync with the IP address your ISP gives you, so you can always reference it by name from anywhere on the Internet. This will solve the ISP DHCP problem.
You will need to do this for each network you attach your laptop to (assuming you have control of those networks).
answered Mar 25 '16 at 21:52
Wes Sayeed
10.7k32758
add a comment |
Two issues you might be facing:
- I'm not sure what you mean by "another network". A port forwarding rule only exists for the router on which you defined it. So if you define a port forwarding rule on your router and then switch to another WiFi network, the rule will not work because your computer is no longer using the router where the rule is defined.
- A port forwarding rule is IP address specific and does not work well with DHCP. If you then connect your laptop using the Ethernet port, for example, then your internal IP address will be different and the rule won't work. Also, both your internal and external IP addresses may change at any time because of DHCP. You can control this on your internal network, but there's nothing you can do about your ISP's policy.
How to do it right:
- Always use DHCP reservations (if your router supports that feature) or static IPs on your computer. Give EACH interface on your computer a different address and make two identical port forwarding rules; one for each. This will eliminate the DHCP problem.
- Use a dynamic DNS service such as No-IP or DynDNS to map your external IP address to a DNS name. These services offer an agent that you download to your computer that will keep your public DNS record in sync with the IP address your ISP gives you, so you can always reference it by name from anywhere on the Internet. This will solve the ISP DHCP problem.
You will need to do this for each network you attach your laptop to (assuming you have control of those networks).
answered Mar 25 '16 at 21:52
Wes Sayeed
10.7k32758
add a comment |
Two issues you might be facing:
- I'm not sure what you mean by "another network". A port forwarding rule only exists for the router on which you defined it. So if you define a port forwarding rule on your router and then switch to another WiFi network, the rule will not work because your computer is no longer using the router where the rule is defined.
- A port forwarding rule is IP address specific and does not work well with DHCP. If you then connect your laptop using the Ethernet port, for example, then your internal IP address will be different and the rule won't work. Also, both your internal and external IP addresses may change at any time because of DHCP. You can control this on your internal network, but there's nothing you can do about your ISP's policy.
How to do it right:
- Always use DHCP reservations (if your router supports that feature) or static IPs on your computer. Give EACH interface on your computer a different address and make two identical port forwarding rules; one for each. This will eliminate the DHCP problem.
- Use a dynamic DNS service such as No-IP or DynDNS to map your external IP address to a DNS name. These services offer an agent that you download to your computer that will keep your public DNS record in sync with the IP address your ISP gives you, so you can always reference it by name from anywhere on the Internet. This will solve the ISP DHCP problem.
You will need to do this for each network you attach your laptop to (assuming you have control of those networks).
answered Mar 25 '16 at 21:52
Wes Sayeed
10.7k32758
Two issues you might be facing:
- I'm not sure what you mean by "another network". A port forwarding rule only exists for the router on which you defined it. So if you define a port forwarding rule on your router and then switch to another WiFi network, the rule will not work because your computer is no longer using the router where the rule is defined.
- A port forwarding rule is IP address specific and does not work well with DHCP. If you then connect your laptop using the Ethernet port, for example, then your internal IP address will be different and the rule won't work. Also, both your internal and external IP addresses may change at any time because of DHCP. You can control this on your internal network, but there's nothing you can do about your ISP's policy.
How to do it right:
- Always use DHCP reservations (if your router supports that feature) or static IPs on your computer. Give EACH interface on your computer a different address and make two identical port forwarding rules; one for each. This will eliminate the DHCP problem.
- Use a dynamic DNS service such as No-IP or DynDNS to map your external IP address to a DNS name. These services offer an agent that you download to your computer that will keep your public DNS record in sync with the IP address your ISP gives you, so you can always reference it by name from anywhere on the Internet. This will solve the ISP DHCP problem.
You will need to do this for each network you attach your laptop to (assuming you have control of those networks).
answered Mar 25 '16 at 21:52
Wes Sayeed
10.7k32758
answered Mar 25 '16 at 21:52
Wes Sayeed
10.7k32758
answered Mar 25 '16 at 21:52
Wes Sayeed
10.7k32758
answered Mar 25 '16 at 21:52
Wes Sayeed
10.7k32758
10.7k32758
add a comment |
add a comment |
I just had this same issue with the same router that you are using in your screenshot (or at least the same software). If you click "(more)" at the top of the screen you will see there is an option to leave the external ip as 0.0.0.0 to forward all external traffic and leave the external ports at 0 if you don't need to switch them in this process. This took me almost a year of on-and-off troubleshooting and hopefully it will help you. As soon as i found these options, it began working as expected from outside my home network as well as inside.
answered Dec 4 at 2:06
Scott
1
add a comment |
I just had this same issue with the same router that you are using in your screenshot (or at least the same software). If you click "(more)" at the top of the screen you will see there is an option to leave the external ip as 0.0.0.0 to forward all external traffic and leave the external ports at 0 if you don't need to switch them in this process. This took me almost a year of on-and-off troubleshooting and hopefully it will help you. As soon as i found these options, it began working as expected from outside my home network as well as inside.
answered Dec 4 at 2:06
Scott
1
add a comment |
I just had this same issue with the same router that you are using in your screenshot (or at least the same software). If you click "(more)" at the top of the screen you will see there is an option to leave the external ip as 0.0.0.0 to forward all external traffic and leave the external ports at 0 if you don't need to switch them in this process. This took me almost a year of on-and-off troubleshooting and hopefully it will help you. As soon as i found these options, it began working as expected from outside my home network as well as inside.
answered Dec 4 at 2:06
Scott
1
I just had this same issue with the same router that you are using in your screenshot (or at least the same software). If you click "(more)" at the top of the screen you will see there is an option to leave the external ip as 0.0.0.0 to forward all external traffic and leave the external ports at 0 if you don't need to switch them in this process. This took me almost a year of on-and-off troubleshooting and hopefully it will help you. As soon as i found these options, it began working as expected from outside my home network as well as inside.
answered Dec 4 at 2:06
Scott
1
answered Dec 4 at 2:06
Scott
1
answered Dec 4 at 2:06
Scott
1
answered Dec 4 at 2:06
Scott
1
1
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f1057113%2fcan-connect-to-port-forwarded-ip-on-my-wifi-but-not-any-other-network%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
