Subsonic Forum

I've been using Subsonic to stream across the Internet for a few months, and I love it!

My ISP is Roadrunner. Until about a month ago, I had Internet, phone and cable bundled, but changed to DirecTV and Vonage, keeping RR for Internet only.

In attempting to get the DirecTV system up and running on the network, I had to upgrade my router, so I chose a Netgear WNDR3400 dual band router. Since the upgrade, I can't connect to my Subsonic server from outside my network via browser or iPhone with iSub...

I've tried reinstalling Subsonic, setting a static IP according to instructions at portforward.com (though I never did that before under the old router), changed the port number in info.plist to a couple of different numbers to no avail... Also tried automatic port forwarding via UPnP and manual port forwarding and still no dice.

So, within my network I can hit localhost and my Subsonic-provided doman name (Subsonic network settings show port forwarding successful and Subsonic domain registered but not connected), but I'm getting nothing when I try to connect from outside or via iPhone on 3G.

As for port changes, I've tried the default 4040, 4140 and most recently 3820... An open port check via canyouseeme.org confirms these ports are not open.

I'm worried now about two things: Port blocking by RR, or the DirecTV system playing havoc in there somewhere...

Anyone have any suggestions? I want my Subsonic back!

The router is the key..until we can open the chosen port, it simply won't work. Is the router responsible for your lan/wlan addressing (dhcp)? Can the router see your computer hosting Subsonic? have you repbooted the router AFTER assigning a pinhole (eg. 4040)? And if so, have you ever seen a successful pinhole using this router? Is the router's firmware up to date?

alphawave7 wrote:Is the router responsible for your lan/wlan addressing (dhcp)? Can the router see your computer hosting Subsonic? have you repbooted the router AFTER assigning a pinhole (eg. 4040)? And if so, have you ever seen a successful pinhole using this router? Is the router's firmware up to date?

Yes, the router is configured as the DHCP server (192.168.1.2 ~ .254). The host computer is assigned 195.168.1.3, and I can run Subsonic locally on the host machine via http://localhost:3200 as well as the Subsonic-provided URL.

After reading your reply, I changed the port number again to 3200 and rebooted the router, with the same results.

This is a new router, and this attempt with Subsonic is the first server assignment I've tried, so no, I haven't been successful hitting an (assumed) open port from outside. The router firmware is up to date.

I'm open to suggestions!

The subsonic url reverts back/resolves to localhost, so that isn't an indicator the port is open. I've verified your public IP and port are NOT open, so we need to troubleshoot your router. Is it's firmware up to date?

Yes, I'm aware that the Subsonic URL resolves to localhost... I have checked port functionality externally via http://www.canyouseeme.org/ and basically none of the port numbers I've attempted have been open.

Anyhoo, yes, the firmware is up to date.

Try a full reset of the router (factory defaults), then ONLY open a single port on your SS host machine. Reboot the router after setting the SS host port, then retest with canyouseeme.org.

Also, I was curious if SS->Settings->Network showed check boxes in both 'automatically configure' and 'Access server' and what they say in the results area?

Many low end routers have a DMZ function which usually only allows ONE host to be added to allow port forwarding. If that is the case you will need to add your PC IP to that setup before it will ever work.

First off, Merry Christmas and thanks so much for your help!

Okay, so I reset the router to factory settings, manually opened port 3200 to my computer running Subsonic (192.168.1.3) in router settings, and then rebooted the router...

• Canyouseeme.org reports Error: I could not see your service on 66.68.100.119 on port (3200) Reason: Connection timed out

• SS automatic configuration deselected, reports pf status as Port forwarding disabled

• With SS custom domain selected, reports: Status: sluggo.subsonic.org is registered, but could not connect to it. (ConnectTimeoutException)


I then deleted the port forward exception I made previously and turned UPnP on in the router and rebooted it. Then I selected automatic UPnP port forwarding in SS and saved...

• Router portmap table recognizes port 3200 as active (TCP) with IP 192.168.1.3

• Canyouseeme.org reports Error: I could not see your service on 66.68.100.119 on port (3200) Reason: Connection timed out

• SS automatic configuration selected, reports pf status as Successfully forwarding port 3200.

• With SS custom domain selected, reports: Status: sluggo.subsonic.org is registered, but could not connect to it. (ConnectTimeoutException)


Also tried both of these options with Default DMZ Server set to 192.168.1.3 per Exrace's instructions, to no avail.

I should note that I have not set up a static IP—I never did this using old router, as I was using a custom domain thru DynDNS. After trying the two connection options above, I entered my DynDNS info in the router's Dynamic DNS section and hit 'show status,' which reported back a successful update... But I can't connect through it.

At this point, I am about ready to return this router and try another, but I REALLY don't want to do that unless I absolutely have to.

Okay, you guys are gonna laff at me... Go ahead...

Remember in my original post, I said I had switched to Vonage for phone service? Well... The Vonage adapter is IN FRONT of my router... And I had NO IDEA that it acted as a router on its own. So, yeah, I searched around and found the login for the Vonage adapter—er, um, ROUTER—and setup port forwarding and DMZ server there, and VOILA! Everything seems to be good now.

Thanks again for trying to help! I appreciate your efforts!

Glad it finally got sorted! Enjoy!

Sluggo wrote:Okay, you guys are gonna laff at me... Go ahead...

Remember in my original post, I said I had switched to Vonage for phone service? Well... The Vonage adapter is IN FRONT of my router... And I had NO IDEA that it acted as a router on its own. So, yeah, I searched around and found the login for the Vonage adapter—er, um, ROUTER—and setup port forwarding and DMZ server there, and VOILA! Everything seems to be good now.

Thanks again for trying to help! I appreciate your efforts!

I used Vonage for many years, until I realized that Ooma would pay for itself after 8 Vonage bills. "I'm now on Ooma, and this is my last Vonage bill!" Went from $25/mo to $3.47/mo.

Anyway, I'm really just commenting because others may like to know that with high speed internet, there is no need to put a VOIP device in front of the router. Just plug it into one of the ports on your router or switch and it will work fine. Attached behind the router it will not interfere with the rest of the network.