I'm done. Help. Please. And, thank you.

[GJ51]

There shouldn't be any need for a Static route either. That's why I recommended a router reset to get rid of any settings you may have entered that weren't needed.

As stated above, if you provide the router make and model we can read the manual and provide specific instructions to forward port 4040.

You are closer to getting this to work than you think. Take a break if you need it, but don't give up.

[derk2468]

Yea, I'll hopefullyyyy be done with this whole process mid-end of week here. But what you just said is a MAJOR key that nowhere has listed and no one has ever told me and is probably why I seem like a fucking retard over here lol. My networking experience doesn't go past just simple installation, but I can obviously get into the settings and do all the minor stuff. But even I did not know that a static route wasn't the same as a static IP. And nowhere does it state that I don't need to touch that or anything with a static DNS? I know enough to just get in there and feel my way through the foreigness to the keywords on certain pages. I just only have to mess around with the port forward settings to set this whole static IP on my LAN and WAN up? Cause that would be exactly why I can't get it to work then lmfao. But I'll wait for responses and I guess thanks for putting up with me not getting the basics and all the advice, I just knew to look for a page that talked about anything to with 'static'. But I have been resetting back any settings I've changed when they haven't worked. I've only touched the DNS, the route and port forward pages. Router is all back to normal now. I'll wait for a response maybe lol with my only question being now if on the actual Subsonic site if I need to enable the auto portforward checkbox or not? I've read mixed responses. Hopefully we're done here guys, I knew I was close; just got sick of trial and erroring for hours with no results.

And FYI my router has no manual lol just a quick setup guide and CD with documentation that pretty sure has just minor warranty and troubleshooting info on it, looked at it once.
But I just bought it, brand new Linksys AC900 EA6200 Dual Band Smart Wi-Fi (Capacity Group C)

[alphawave7]

http://support.linksys.com/en-us/support/routers/EA6200

Contains both your manual (user guide) and the latest firmware download.
Manual: http://downloads.linksys.com/downloads/ ... 01684A.pdf
Firmware: http://downloads.linksys.com/downloads/ ... od.img.zip

Before beginning, I would check your current firmware and see if the one linked above is more recent. If so, consult the manual for upgrade procedures first. THEN, proceed with setting up router, dhcp reservation, and port forward.

First, DHCP Reservation (aka Static IP) on Page 30: "How to set up DHCP reservation"
Then follow instructions page 46: "How to set up port forwarding for a single port" with the following:
App Name=Subsonic
ExternalPort=4040
InternalPort=4040
TCP/UDP=Both
Default IP=whatever you set in DHCP Reservation (eg. 192.168.1.xxx)
CHECK THE ENABLED BOX.
Reboot.
Test with canyouseeme.org for 4040.

[GJ51]

Another tip for setting up the static ip for the server is to do so in the settings for the NIC. I usually go into the NIC settings and define the ip address that I want used and uncheck"Obtain ip automatically" That way if you have the address defined as reserved in the router and the same internal ip defined in the nic, your covered on both ends and should never have to worry about getting changed to a new internal ip on the server.

[alphawave7]

Another tip for setting up the static ip for the server is to do so in the settings for the NIC. I usually go into the NIC settings and define the ip address that I want used and uncheck"Obtain ip automatically" That way if you have the address defined as reserved in the router and the same internal ip defined in the nic, your covered on both ends and should never have to worry about getting changed to a new internal ip on the server.

Excellent advice..I go even further and manually assign IPs to every device nic possible (the mental lan map is actually quite easy) , use router 'reservations' for non-compliant hardware (rokus) and only use dhcp for guests, allocated in a range beyond my lan map. But that might be a tad DIY control-freakish for most.

[tnt533]

Another tip for setting up the static ip for the server is to do so in the settings for the NIC. I usually go into the NIC settings and define the ip address that I want used and uncheck"Obtain ip automatically" That way if you have the address defined as reserved in the router and the same internal ip defined in the nic, your covered on both ends and should never have to worry about getting changed to a new internal ip on the server.

Excellent advice..I go even further and manually assign IPs to every device nic possible (the mental lan map is actually quite easy) , use router 'reservations' for non-compliant hardware (rokus) and only use dhcp for guests, allocated in a range beyond my lan map. But that might be a tad DIY control-freakish for most.

Absolutely not control-freakish at all. If you actually use your internal network for anything further than connecting multiple machine to the internet then static addressing for all non-mobile systems IMHO is a must. It simply makes sense for administration purposes even on a smaller network. The last thing I want to have to do is scan my network or log in to my router to check DHCP tables just to reach out to my wife's system to throw an ebook on her desktop. Static addressing also forces one to gain a better understanding of how IP works in the first place and that is something anyone attempting to serve any kind of service outside of their home can benefit from.

I don't wish to chime in on this particular issue because there are already enough peeps trying to help but one thing people need to understand is that the protocol that drives all this is steadfast and true. If you cant connect, sans a hardware or cabling issue, it is always config and bringing things down to their most basic low level form is the best place to start trying to trace issues. Is the cable working? Is it plugged in? Is there power to all devices? Can the hosting machine ping the loopback(127.0.0.1)? Ping another machine on the same subnet (local internal network)? Can it ping the default gateway (router)? Can it ping outside the network? In other words can you ping 8.8.8.8 for instance? Is the server software accessible from the server itself and then from another machine on the same subnet? If all that is yes but not from outside then it HAS to be port forwarding on the router.

[derk2468]

I just can't fucking type anymore or put anymore serious effort into this here. Basically just asking for all procedures and any advice to get the damn 4040 port open? Promise everything else is set up right. Thanks for finally telling me about the DCHP reservations advice, but reallyyyyy should be mentioned somewhere like from the fucking beginning honestly. But yea, canyouseeme won't work and it's the only roadblock left to having it work at 100%. Port only works on my localhost when my computer is on. Somehow this static IP I set up isn't being connected to my public/external IP? Why is it this hard to open something that is just a virtual doorway lol

[GJ51]

http://downloads.linksys.com/downloads/ ... 01684A.pdf

You want to use the instructions on page 43 of the manual in the link above.

"Single port forwarding is a feature that forwards inbound traffic from the Internet on a specific port to
a single device on your local network. An example of single port forwarding would be to forward inbound web requests, typically on port 80, to a web server."

Log into the admin page of the router and start with the instructions at #3.

You need to get to the screen in step 5 "The single Port Forwarding Screen"

The external port number is probably NOT required - Step 8 - or you might need to put in port 80. I'm guessing from experience that you don't need to put anything in, but remember, each router is unique and what I do on mine might not be what's required on yours. General concepts are the same but the interfaces are all different and some are really obtuse.

Internal port will be the port you're using for Subsonic (4040 is the default)

Protocol is TCP - it would probably work if you enable both but it isn't necessary and doesn't help anything.

The device IP is the INTERNAL address you've assigned to the host machine running Subsonic ( If you used my recommendation it would be 192.168.1.254, but whatever you used is fine as long as you're sending the traffic to your server.)

Select Enabled then Save

The most common mistake new users make is putting wrong information into the external port field. You DO NOT put 4040 in there.

Let us know if I got lucky

Here is what you posted earlier I will make my recommended changes in red:

Application Name:Subsonic
External Port:Leave blank - if first try with my settings doesn't work you may try 80
Internal Port:4040
Protocol: Both (TCP/UDP) obviously You only need TCP
Device IP# 10.88 (set permanently) then 2 open fields If you're still on 10.88.158.103 just complete the blank octets putting 158 in the first and 103 in the second

I'm a bit surprised that there are 2 octets to input given the subnet mask suggests you should only need to input the last octet, but again, router pages don't always make logical sense. It may have been set up this way as a limit on how much subnetting you can do on this particular router as opposed to a more logical approach of inputing known information and only leaving the last octet blank. Subnetting and network class are another topic that takes a bit of study to grasp. Just a quirky point of curiosity on my part here - nothing that should be of concern for getting you up and running.

Pv4 Address: 10.88.158.103
Subnet Mask: 255.255.255.0
Default Gateway: 10.88.158.176
Public IP (from canyouseeme): 72.88.52.108
Using Subsonic ports: 4040-4040 This is probably the problem as I mentioned above you most likely entered 4040 into the External port block. That would be WRONG, leave it blank or if that doesn't work try 80

This is a common mistake.Although the incoming request is asking to connect to port 4040 inside your network, the requesting device from outside your network is not using 4040 at that end to transmit the request to your router. That request is most likely being made on a randomly assigned port by a router at the origin of the request and can be just about anything.

This is just about what is happening when you have multiple devices inside your network all making requests for data from the web. Ever wonder how you can open multiple pages and get different information displayed in different windows. The router keeps track of what data is being requested by which device on which port and routes the response back to the device that made the request to the same port. The device keeps track of which process id made the request on that port and sends the data accordingly when the reply is received from the router.

This stuff is a never ending journey of discovery and Subsonic is a great way to learn these concepts. After 30 years of poking around this stuff, I'm still amazed at how much I'll never be able to get to learning. It's a very deep well indeed, but the learning part is always rewarding.

Never give up.

[derk2468]

Fucking really though? If I could I on my phone right now I'd bring it up as proof, but swearrrr to God all the guides and even the Subsonic official instructions say to to put 4040 for BOTH ports. I'll take the blame for getting a static IP route confused with what I needed under the DHCP reservations. Really though, individual router protocols aside, I just think all the listed guides and help out there are meant to make people look like retards -_- lol. Thank you for the extremely long post and for everyone's help on clearly such stupid small issues here, but such small things really should be updated in future setup instructions, cause it's not just cause I'm a moron or that it varies by router too much, it's that every little detail in this process counts. Holy shit does it lol

[derk2468]

Sooo...I fixed the external port to forward to 80, because it wouldn't let me leave it blank. Tried only TCP, only UDP and both. Andddd under the Subsonic network settings every other time I save it says I'm successfully forwarding port 4040. Figure that one out geniuses lol

[alphawave7]

What does can you see me.org say for 4040?

Sent from my Nexus 5 using Tapatalk

[GJ51]

Sooo...I fixed the external port to forward to 80, because it wouldn't let me leave it blank. Tried only TCP, only UDP and both. Andddd under the Subsonic network settings every other time I save it says I'm successfully forwarding port 4040. Figure that one out geniuses lol

I can't explain why the router doesn't work as described in the manual. We have encountered routers that need to be rebooted before the new settings take effect. Linksys was the number 1 name in residential routers originally, but they seem to have rested on a few laurels since the early days. After being bought by Cisco I've felt that the old reputation for being bullet proof just wasn't being upheld in newer stuff and I'm pretty much in the Netgear camp for now.

There are thousands of users here with all manner of equipment that have gotten this working. I've personally done this on my network and working here with other users thousands of times. Without being physically onsite with your gear it's not as easy to figure out anything more specific than the router is not forwarding the port properly. Is it user input error, a faulty router, or something else? The bottom line is that if you can't see the port as open from canyouseeme.org you're not going to be able to connect from outside your network. We've given you all the information we have with the exception of one possible exception you might be able to try.

The one application that seems to be able to set up its own port fwd rule properly without any problems is Skype. If you have Skype or any other applications that forward ports on the router, you should be able to look at the rules, test those ports at Canyouseeme and verify that port fwding actually works on the router, If that's the case you should be able to compare the rules that are working with what you have set up for Subsonic to see if you can spot an error.

If none of that bears fruit it may be time to solve the problem with a large hammer and go buy a new router.

EDIT: By the way - you did not fix the external port to forward to 80. You defined the request for port 4040 being received at the router on port 80 to be sent to the correct internal ip address where your Subsonic host machine is waiting to answer the request. I know this may sound a bit picky, but it's the details like this that create confusion and errors. Those of us who started back in the old days with MS-DOS, or anyone who does programming realizes how even the difference between a period and a semicolon can make all the difference in the world between something that works and failure. Details are important when dealing with these topics. It's not horseshoes or hand grenades at this level. No points for close.

[derk2468]

Idk about picky, just confusing lol. You're saying I only in theory I'm forwarding to the port 80? And there's something I have to do to actually confirm/activate the port forward? Regardless having my slightly more technical computer oriented step father to have his hand at it sometime soon. He's older and grew through the old school like you guys so I'm sure he can figure something iut. It's whatever at this point, thanks everyone for all the advice all the same though. Always gotta be some sort of a catch with a service and technology this insanely useful and beneficial for so cheap with unlimited storage lol

[alphawave7]

Idk about picky, just confusing lol. You're saying I only in theory I'm forwarding to the port 80? And there's something I have to do to actually confirm/activate the port forward? Regardless having my slightly more technical computer oriented step father to have his hand at it sometime soon. He's older and grew through the old school like you guys so I'm sure he can figure something iut. It's whatever at this point, thanks everyone for all the advice all the same though. Always gotta be some sort of a catch with a service and technology this insanely useful and beneficial for so cheap with unlimited storage lol

The catch: anything worth having is worth working for, and the journey is often more important than the destination.

You don't want to run a server on port 80. Use default port 4040, and open the port according to your router manual's directions. Test with canyouseeme.org for 4040.

[mgoldey]

I didn't see any mention of this, and it bedeviled me too, once:

Open the Subsonic icon in your system tray and check the "settings" tab. Is "Enable https on port ___" checked? If so, either uncheck it, or open that port in your router as well as 4040. If it's checked, then traffic coming in on port 4040 gets redirected to port 4443 or whatever https port is listed there. If that https port is blocked, then you'll see "Network connection error" or whatever that message is, no matter how 4040 is set.