Subsonic Forum

I just switched from a Linksys to a Buffalo router and after i got done setting up all my port forwarding rules, they all work except 4040 and thus Subsonic. I've tried tweaking FW rules outside of port forwarding, thinking it might be some other feature that subsonic needs enabled that isn't by default but nothing doing.

I can connect to my subsonic server intra-network through both the browser and the mobile app but nothing seems to work if i access my (external) dynamic DNS address. I've enabled 4040 on both TCP and UDP and no luck. I even tried forwarding a different port, 4041 to 4040 on the network side and still don't get anything back. Interesting to note, i get more of a timeout behavior hitting 4040 where as the 4041->4040 route gets an active refusal.

Not sure what else to try, i'm positive my port forwarding rules are setup properly (i can get through on many other ports/services to the same server). Is there anything else i should look into?

Several things: does the buff support DD-WRT? That would be a more suitable, stable firmware to run. Secondly, it may take reboots to check and see if your port pinholing is working, so reboot router after EVERY change. Lastly, use canyouseeme.org to test your ports after you reboot. Cheers!

So I just finished setting up a QNAP NAS and i'm having the exact same problem with remote access as with Subsonic, even though they are implicitly on different machines. Thus the router is the common point of travel.

It appears, it might be something to do with the way the request is translated through the firewall on the router. My understanding is that the host header information containing the dynamic DNS is coming through with the request and its not expected. I.E - that is to say, my request is coming over for mydynURL.dynURLservice.com:8081 to the web service but its expecting a request for 192.168.xxx.xxx:8081 and its being actively ignored (perhaps intentionally thinking it might be running on a webserver containing many URL signatures) Perhaps my old router always resolved the request to a local address, i don't know.

This is after only the briefest of research, so this might be total bunk, but it makes some sense to me. I'm going to do some tweaking of router settings tomorrow and see if that can fix it... OR i might just brick the thing trying to alter it too much and have to install DD-WRT which i assume is a working router setup for remote access

I'll report back here in the next few days, cheers.

So, update.

Haven't found anything confirming my theory on Buffalo or QNAP forums, or any settings to tweak. Most articles mention support for NAT, but it looks like i have that enabled. An interesting thing of note is i can hit both Subsonic and QNAP from my dynamic DNS address if i'm on the network.

Kinda scraping the bottom of the barrel, my router has power cycled many times since i enabled port forwarding for Subsonic so i don't think this is just an initialization problem. Any suggestions would be welcome.

Start fresh with a full reset of the router, restart form scratch. It simply must pass 4040 test on canyouseeme.org to be visible outside your lan.

Man, I'm having the same problem. Got an upgraded Uverse router, opened up all the same ports but can't see any of them outside my network. When I use the internal IP, all my devices can see it just fine. Can't figure out what's going on.

Hi, msujdog, I am having the same problem. Have you solved it? Could canyouseeme.org see your port 4040? Thank you!