port 80 closed after port forward and firewall settings
up vote
0
down vote
favorite
Currently I'm having an issue that only somehow started to appear within the last day or so and nothing about my network setup changed that would cause these issues.
I'm running a development webserver on my home PC just to test some things out and I've had IIS set up correctly and haven't messed with any of the bindings.
I have port 80 forwarded on my router as normal and until a few days ago, I was able to access my webserver perfectly fine through the external IP, but when I start working on it today, it seems like it's blocking all connections externally now.
I've double checked and even deleted and redone my port forwarding. I've double checked and redone my IIS bindings and I even tried opening my windows firewall on port 80 to no avail.
I have no idea what could have happened that suddenly made it stop working. I've checked my telnet and it reads "TCP 0.0.0.0:80 0.0.0.0:0 LISTENING" which seems to suggest that my computer is listening perfectly, but my router is blocking external connections for some reason.
Checking IIS logs confirms this as IIS doesn't receive ANY connection attempts when I try to connect using a public IP.
Again, I check my port forwarding and everything is set up correctly.
I check my ports with an online port scanner and it shows port 80 and 443 as closed still. I've even tried setting up a Dynamic DNS which still didn't work.
I have no idea what to check now and it seems like it just randomly stopped working for absolutely no reason what so ever.
My router appears to be blocking ports for some reason, even after explicitly forwarding them and I need some assistance where to go from here.
iis firewall router port-forwarding
asked Nov 19 at 17:27
Kats
11
migrated from serverfault.com Nov 19 at 17:30
This question came from our site for system and network administrators.
|
show 5 more comments
up vote
0
down vote
favorite
Currently I'm having an issue that only somehow started to appear within the last day or so and nothing about my network setup changed that would cause these issues.
I'm running a development webserver on my home PC just to test some things out and I've had IIS set up correctly and haven't messed with any of the bindings.
I have port 80 forwarded on my router as normal and until a few days ago, I was able to access my webserver perfectly fine through the external IP, but when I start working on it today, it seems like it's blocking all connections externally now.
I've double checked and even deleted and redone my port forwarding. I've double checked and redone my IIS bindings and I even tried opening my windows firewall on port 80 to no avail.
I have no idea what could have happened that suddenly made it stop working. I've checked my telnet and it reads "TCP 0.0.0.0:80 0.0.0.0:0 LISTENING" which seems to suggest that my computer is listening perfectly, but my router is blocking external connections for some reason.
Checking IIS logs confirms this as IIS doesn't receive ANY connection attempts when I try to connect using a public IP.
Again, I check my port forwarding and everything is set up correctly.
I check my ports with an online port scanner and it shows port 80 and 443 as closed still. I've even tried setting up a Dynamic DNS which still didn't work.
I have no idea what to check now and it seems like it just randomly stopped working for absolutely no reason what so ever.
My router appears to be blocking ports for some reason, even after explicitly forwarding them and I need some assistance where to go from here.
iis firewall router port-forwarding
asked Nov 19 at 17:27
Kats
11
migrated from serverfault.com Nov 19 at 17:30
This question came from our site for system and network administrators.
Hi, please check with your ISP, a lot of ISP will block HTTP/HTTPS port to prevent business use on residential users.
– yagmoth555
Nov 19 at 17:30
This makes sense, but is confusing because why would it have just started a day or so ago and hasn't been consistent? Will changing the port help in any way?
– Kats
Nov 19 at 17:39
Yes you can try, it would rule out the ISP part
– yagmoth555
Nov 19 at 17:41
Running a server to the public Internet is a violation of your residential terms of service. Your ISP may have started running CGN. What address do you have on the WAN connection of your router; is it in Private (10.0.0.0/8,172.16.0.0/12, or192.168.0.0/16) or Shared (100.64.0.0/10) address space? If so, you would need to forward on the ISP NAPT router, which you cannot do.
– Ron Maupin
Nov 19 at 17:41
What do you mean on my WAN connection of my router? My local address is a 192.168.x.x address if that's what your asking.
– Kats
Nov 19 at 17:46
|
show 5 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Currently I'm having an issue that only somehow started to appear within the last day or so and nothing about my network setup changed that would cause these issues.
I'm running a development webserver on my home PC just to test some things out and I've had IIS set up correctly and haven't messed with any of the bindings.
I have port 80 forwarded on my router as normal and until a few days ago, I was able to access my webserver perfectly fine through the external IP, but when I start working on it today, it seems like it's blocking all connections externally now.
I've double checked and even deleted and redone my port forwarding. I've double checked and redone my IIS bindings and I even tried opening my windows firewall on port 80 to no avail.
I have no idea what could have happened that suddenly made it stop working. I've checked my telnet and it reads "TCP 0.0.0.0:80 0.0.0.0:0 LISTENING" which seems to suggest that my computer is listening perfectly, but my router is blocking external connections for some reason.
Checking IIS logs confirms this as IIS doesn't receive ANY connection attempts when I try to connect using a public IP.
Again, I check my port forwarding and everything is set up correctly.
I check my ports with an online port scanner and it shows port 80 and 443 as closed still. I've even tried setting up a Dynamic DNS which still didn't work.
I have no idea what to check now and it seems like it just randomly stopped working for absolutely no reason what so ever.
My router appears to be blocking ports for some reason, even after explicitly forwarding them and I need some assistance where to go from here.
iis firewall router port-forwarding
asked Nov 19 at 17:27
Kats
11
Currently I'm having an issue that only somehow started to appear within the last day or so and nothing about my network setup changed that would cause these issues.
I'm running a development webserver on my home PC just to test some things out and I've had IIS set up correctly and haven't messed with any of the bindings.
I have port 80 forwarded on my router as normal and until a few days ago, I was able to access my webserver perfectly fine through the external IP, but when I start working on it today, it seems like it's blocking all connections externally now.
I've double checked and even deleted and redone my port forwarding. I've double checked and redone my IIS bindings and I even tried opening my windows firewall on port 80 to no avail.
I have no idea what could have happened that suddenly made it stop working. I've checked my telnet and it reads "TCP 0.0.0.0:80 0.0.0.0:0 LISTENING" which seems to suggest that my computer is listening perfectly, but my router is blocking external connections for some reason.
Checking IIS logs confirms this as IIS doesn't receive ANY connection attempts when I try to connect using a public IP.
Again, I check my port forwarding and everything is set up correctly.
I check my ports with an online port scanner and it shows port 80 and 443 as closed still. I've even tried setting up a Dynamic DNS which still didn't work.
I have no idea what to check now and it seems like it just randomly stopped working for absolutely no reason what so ever.
My router appears to be blocking ports for some reason, even after explicitly forwarding them and I need some assistance where to go from here.
iis firewall router port-forwarding
iis firewall router port-forwarding
asked Nov 19 at 17:27
Kats
11
asked Nov 19 at 17:27
Kats
11
asked Nov 19 at 17:27
Kats
11
asked Nov 19 at 17:27
Kats
11
asked Nov 19 at 17:27
Kats
11
11
migrated from serverfault.com Nov 19 at 17:30
This question came from our site for system and network administrators.
migrated from serverfault.com Nov 19 at 17:30
This question came from our site for system and network administrators.
Hi, please check with your ISP, a lot of ISP will block HTTP/HTTPS port to prevent business use on residential users.
– yagmoth555
Nov 19 at 17:30
This makes sense, but is confusing because why would it have just started a day or so ago and hasn't been consistent? Will changing the port help in any way?
– Kats
Nov 19 at 17:39
Yes you can try, it would rule out the ISP part
– yagmoth555
Nov 19 at 17:41
Running a server to the public Internet is a violation of your residential terms of service. Your ISP may have started running CGN. What address do you have on the WAN connection of your router; is it in Private (10.0.0.0/8,172.16.0.0/12, or192.168.0.0/16) or Shared (100.64.0.0/10) address space? If so, you would need to forward on the ISP NAPT router, which you cannot do.
– Ron Maupin
Nov 19 at 17:41
What do you mean on my WAN connection of my router? My local address is a 192.168.x.x address if that's what your asking.
– Kats
Nov 19 at 17:46
|
show 5 more comments
Hi, please check with your ISP, a lot of ISP will block HTTP/HTTPS port to prevent business use on residential users.
– yagmoth555
Nov 19 at 17:30
This makes sense, but is confusing because why would it have just started a day or so ago and hasn't been consistent? Will changing the port help in any way?
– Kats
Nov 19 at 17:39
Yes you can try, it would rule out the ISP part
– yagmoth555
Nov 19 at 17:41
Running a server to the public Internet is a violation of your residential terms of service. Your ISP may have started running CGN. What address do you have on the WAN connection of your router; is it in Private (10.0.0.0/8,172.16.0.0/12, or192.168.0.0/16) or Shared (100.64.0.0/10) address space? If so, you would need to forward on the ISP NAPT router, which you cannot do.
– Ron Maupin
Nov 19 at 17:41
What do you mean on my WAN connection of my router? My local address is a 192.168.x.x address if that's what your asking.
– Kats
Nov 19 at 17:46
Hi, please check with your ISP, a lot of ISP will block HTTP/HTTPS port to prevent business use on residential users.
– yagmoth555
Nov 19 at 17:30
Hi, please check with your ISP, a lot of ISP will block HTTP/HTTPS port to prevent business use on residential users.
– yagmoth555
Nov 19 at 17:30
This makes sense, but is confusing because why would it have just started a day or so ago and hasn't been consistent? Will changing the port help in any way?
– Kats
Nov 19 at 17:39
This makes sense, but is confusing because why would it have just started a day or so ago and hasn't been consistent? Will changing the port help in any way?
– Kats
Nov 19 at 17:39
Yes you can try, it would rule out the ISP part
– yagmoth555
Nov 19 at 17:41
Yes you can try, it would rule out the ISP part
– yagmoth555
Nov 19 at 17:41
Running a server to the public Internet is a violation of your residential terms of service. Your ISP may have started running CGN. What address do you have on the WAN connection of your router; is it in Private (
10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16) or Shared (100.64.0.0/10) address space? If so, you would need to forward on the ISP NAPT router, which you cannot do.– Ron Maupin
Nov 19 at 17:41
Running a server to the public Internet is a violation of your residential terms of service. Your ISP may have started running CGN. What address do you have on the WAN connection of your router; is it in Private (
10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16) or Shared (100.64.0.0/10) address space? If so, you would need to forward on the ISP NAPT router, which you cannot do.– Ron Maupin
Nov 19 at 17:41
What do you mean on my WAN connection of my router? My local address is a 192.168.x.x address if that's what your asking.
– Kats
Nov 19 at 17:46
What do you mean on my WAN connection of my router? My local address is a 192.168.x.x address if that's what your asking.
– Kats
Nov 19 at 17:46
|
show 5 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f1376746%2fport-80-closed-after-port-forward-and-firewall-settings%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
Hi, please check with your ISP, a lot of ISP will block HTTP/HTTPS port to prevent business use on residential users.
– yagmoth555
Nov 19 at 17:30
This makes sense, but is confusing because why would it have just started a day or so ago and hasn't been consistent? Will changing the port help in any way?
– Kats
Nov 19 at 17:39
Yes you can try, it would rule out the ISP part
– yagmoth555
Nov 19 at 17:41
Running a server to the public Internet is a violation of your residential terms of service. Your ISP may have started running CGN. What address do you have on the WAN connection of your router; is it in Private (
10.0.0.0/8,172.16.0.0/12, or192.168.0.0/16) or Shared (100.64.0.0/10) address space? If so, you would need to forward on the ISP NAPT router, which you cannot do.– Ron Maupin
Nov 19 at 17:41
What do you mean on my WAN connection of my router? My local address is a 192.168.x.x address if that's what your asking.
– Kats
Nov 19 at 17:46