Ask Your Question

Revision history [back]

Is it possible to detect what is blocking port 80

Ok, curl returns this on my local machine... "connect to 94.15.100.134 port 80 failed: Connection refused"

even telnet localhost 80 returns connect to address 127.0.0.1: Connection refused

and to the server with the http running on it directly robert$ telnet 192.168.0.15 80 Trying 192.168.0.15... telnet: connect to address 192.168.0.15: Connection refused telnet: Unable to connect to remote host

I've tried everything. I mean everything. at least tht I can think of. Port forwarding is on. and correct. However, even a check open port from outside returns Port Closed. The ISP swears black and blue that they aren't blocking the port...

is there any way of finding out what and where it's being blocked by through Wireshark?

I have it running of course and can see the no-ip service trying to do its thing - but to no avail, it seems.

40003 7509.869012 ec2-52-9-108-157.us-west-1.compute.amazonaws.com 192.168.0.15 HTTP/XML 557 HTTP/1.1 200 OK

40005 7509.870275 192.168.0.15 ec2-52-9-108-157.us-west-1.compute.amazonaws.com TCP 66 60220 → http(80) [FIN, ACK] Seq=249 Ack=656 Win=131072 Len=0 TSval=208303976 TSecr=1225515866

by the way. Complete newbie to Wireshark Robert

Is it possible to detect what is blocking port 80

Ok, curl returns this on my local machine... machine...

"connect to 94.15.100.134 port 80 failed: Connection refused"

refused"

even

telnet localhost 80 returns
connect to address 127.0.0.1: Connection refused

refused

and to the server with the http running on it directly directly

robert$ telnet 192.168.0.15 80
Trying 192.168.0.15...
telnet: connect to address 192.168.0.15: Connection refused
telnet: Unable to connect to remote host

host

I've tried everything. I mean everything. at least tht I can think of. Port forwarding is on. and correct. However, even a check open port from outside returns Port Closed. The ISP swears black and blue that they aren't blocking the port...

is there any way of finding out what and where it's being blocked by through Wireshark?

I have it running of course and can see the no-ip service trying to do its thing - but to no avail, it seems.

40003   7509.869012 ec2-52-9-108-157.us-west-1.compute.amazonaws.com    192.168.0.15    HTTP/XML    557 HTTP/1.1 200 OK 

40005 7509.870275 192.168.0.15 ec2-52-9-108-157.us-west-1.compute.amazonaws.com TCP 66 60220 → http(80) [FIN, ACK] Seq=249 Ack=656 Win=131072 Len=0 TSval=208303976 TSecr=1225515866

TSecr=1225515866

by the way. Complete newbie to Wireshark Robert