StriatedFoot Posted May 31, 2007 Report Share Posted May 31, 2007 When I'm inside the network and type http://<utorrentmachineIP>:8080/gui , it works fine. The <utorrentmachineIP> is a local 192.168.X.X IP address.I've used my router (FreeBSD machine running natd and ipfw) to forward port 8080 to <utorrentmachineIP> by adding the redirect line in natd.conf.Outside the network, I type http://<externalIP>:8080/gui, and it times out. I know my external IP is correct because I run other servers on it from the FreeBSD box. I also know that the port is open at the external location where I've tested it from.I don't believe it's a firewall issue because I've set it to "allow" everything for testing purposes.Any ideas? Link to comment Share on other sites More sharing options...
Ultima Posted June 1, 2007 Report Share Posted June 1, 2007 Does the router allow loopback connections? Link to comment Share on other sites More sharing options...
StriatedFoot Posted June 1, 2007 Author Report Share Posted June 1, 2007 Yes. I can type the external IP address from inside the network and it will still resolve to the router. But the problem of reaching the utorrent computer persists from both inside and outside the network when I try to do it using the external IP address. It's as if port forwarding is not enabled, even though I know it is. Link to comment Share on other sites More sharing options...
Ultima Posted June 1, 2007 Report Share Posted June 1, 2007 Mm... Could it be that your ISP is blocking port 8080? Many ISPs do so to prevent personal website hosting... and stuff... Link to comment Share on other sites More sharing options...
StriatedFoot Posted June 1, 2007 Author Report Share Posted June 1, 2007 I guess that's possible. But my ISP is typically really good about leaving ports open. I have a web, ftp, telnet, https server that all work on their respective ports. I also use VoIP with no problems, and of course utorrent works on the high number port it was set to.How do I find out if my ISP blocks 8080? Link to comment Share on other sites More sharing options...
Lord Alderaan Posted June 1, 2007 Report Share Posted June 1, 2007 By changing the alternative webui port. If you aren't using the alternative webui port and you are connectible then there is something freaky going on. Link to comment Share on other sites More sharing options...
StriatedFoot Posted June 2, 2007 Author Report Share Posted June 2, 2007 I made sure that 8080 is open. It is.Can anyone think of an easy way to tell if port forwarding is working? Link to comment Share on other sites More sharing options...
schnurlos Posted June 2, 2007 Report Share Posted June 2, 2007 in uTorrent: CTRL+G, point 2) Test if port is forwarded properly Link to comment Share on other sites More sharing options...
Ultima Posted June 2, 2007 Report Share Posted June 2, 2007 Just to be sure, can you try connecting your computer directly to the modem (bypassing the router)? Link to comment Share on other sites More sharing options...
StriatedFoot Posted June 2, 2007 Author Report Share Posted June 2, 2007 Strange. It says that neither port is forwarded properly. That is, the webUI port AND the port you use for data -- however, I can download and upload just fine. I dunno, maybe NAT is allowing me to bypass port forwarding for this app? Link to comment Share on other sites More sharing options...
Ultima Posted June 2, 2007 Report Share Posted June 2, 2007 Doubtful. If the port isn't forwarded, then it isn't forwarded. A "bypass" would register as an open port with the port checker. Have you tried connecting your computer directly to the modem like I suggested? Link to comment Share on other sites More sharing options...
StriatedFoot Posted June 2, 2007 Author Report Share Posted June 2, 2007 I believe that NAT requires that the person within the network initiates the transfer, which may be what is allowing utorrent to work. Anyway, why else would utorrent be working but the port coming back as closed?[Haven't tried the computer directly up the modem yet -- gotta wait for tonight, because it requires that I basically shut down my entire network and go to a remote location to test it.] Link to comment Share on other sites More sharing options...
Lord Alderaan Posted June 4, 2007 Report Share Posted June 4, 2007 Use a different port. Forward that one. Test again. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.