mitchm11741 wrote:Just wanted to thank you guys for tips that helped me with my similar sounding issue. Through your tips, I was able to find the utility to test whether or not my ports were externally accessible. They were not. Also, your tips indirectly lead me to a free Static IP setting app from the PortForward site. That app gave me an important clue. I first reset my server computer to dynamic address (instead of static) then tried to reset to Static and the app found an error. Somehow, all my addresses were locked up and unavailable. Obviously, something was haywire in my router in control of available addresses despite all the settings looking correct.
I reset my router to factory defaults (a popular LInksys WRT54G). Then I used the Static IP setup tool to reset my Subsonic Server computer's static IP (the app is a nice time saver). Right away, I found I had originally incorrectly set the static IP on my server to be within the range of the addresses set by the router. The new static IP was fine and now outside the range of DHCP set addresses. Finally, I went into the router to open the port for Subsonic to the new static IP for the computer running the Subsonic Server. Re-ran the Open Port Check Tool and, voila, now it looks like my server can be seen through the router. Tomorrow, I will test from outside my LAN to insure complete success but I am pretty confident now. Thanks again for the tips, guys.
Ha! Yeah...it's definitely a trial and error (with mostly error) troubleshoot until you get success, or give up!
It's also a great idea to return a non-compliant router to factory default condition before 'writing it off', or better still, like you can do with that WRT54G, install a superior firmware (DD-WRT, OpenWRT and their variants) that make customisations even easier and more reliable. Marking this as resolved, as OP's contact with ISP revealed his modem ALSO contained an SPI firewall, and once a hole was punched in it, his server lit up WAN-side. Happy day.
