6
3
I have RavenDB running on localhost:8080
. I would like to make it externally accessible, just as a test (ignore security concerns for now).
To do so, I configured my router to forward external port 8080
to internal port 8080
of 192.168.0.101
(which is the internal IP address of my machine, as determined by the IPv4 entry of ipconfig /all
).
According to an external port checker, port 8080 is open (external IP is masked):
However, when I go to ExternalIp:8080
, I'm unable to connect. In contrast, InternalIp:8080
works fine.
Given that the port appears to be open, but I can't connect externally, are there any tools or ways of diagnosing where the blockage is happening?
Additional Possibly Relevant Info
- I have Windows Firewall, but turning it off makes no difference.
- Router is Archer C5, modem is Motorola SB6121.
- My ISP only blocks a couple ports, and 8080 is not one of them.
- My external IP is dynamic, but changes very infrequently, and I made sure to use the right one :)
1if the port shows as "open" to a external port scan, then you have your three 'P's: a running process, listening on an known port, with a pathway to access it. That means that your port forwarding and service listener configurations are correct, and that a firewall is not blocking the path. So that leaves internal service configuration as the likely vector. Review your service configuration to see if it controls valid IPs, etc. Also, its a long shot, but confirm that your port forwarding rules are pointing to the correct server, not another server at 8080. last, what client are you testing? – Frank Thomas – 2015-10-15T16:12:15.430