Setting Up The Router - Static IP Address

[markfielding]

I have read that "most problems are due to improper setup on the router. Setting a fixed internal ip address for the server and proper port forwarding rules on the router are essential for long term stability"... I'm pretty sure that this is where I am coming unstuck.

I have set up and configured the server on my Mac OS X v.10.6.8.

But I cannot find the resources to help me set up my router, which is a Cisco Linksys WRT160Nv. I don't profess to be completely savvy when it comes to networks - far from it. But I can usually follow instructions and believe I need assistance in assigning a static IP address to my Mac. Any guidance would be greatly appreciated.

Best regards,
MNF

[BKKKPewsey]

Try http://portforward.com/english/routers/port_forwarding/Linksys/WRT610N/Subsonic.htm
That should give you all the info you need

[markfielding]

Dear BKKKPewsey,

Thank you for responding. I've attached 2 screen shots of the settings I currently have on my Cisco Linksys WRT160Nv router, showing the Basic Settings and the Single Port Forwarding settings in the Applications & Gaming tab. I have been unable to assign a static IP address to my iMac (at least, not one that works), so I have reverted to assigning the same IP address manually that had just been assigned automatically (in this case 192.168.1.105), but also to no avail. Also attached is a screen shot of my network System Preferences. Are you able to identify where I am going wrong from this information?

Thanks and brgds
MNF

[BKKKPewsey]

To set up a static IP for your server you need to hit the DHCP Reservation button
Then you can assign an IP address against a MAC address.
Just enter your servers mac address and what ever IP you want eg 192.168.1.105
Your server will will then always get that IP from router eg static IP -voila!!

[bushman4]

Also, does it work on your INTERNAL network? ie, can a different computer on the same network navigate to http://192.168.1.105 and get redirected to https://192.168.1.105:4040 and see the subsonic interface?

If that does not work then there is either a port conflict (you have something else running on your subsonic server on either port 80 or 4040) on your subsonic server or a firewall on your subsonic server that is blocking the traffic to those ports.

If it works on an internal client but not externally then it is a router issue.

Logical troubleshooting steps would be:

1. Try it at the server itself using "localhost" or "127.0.0.1" as an address. If that works then
2. Try it at the server itself using the server's real IP address. If that works then
3. Try it on a WIRED internal client using the server's IP address. If that works then
4. Try it on a WIRED internal client using the server's hostname. If that works then
5. (optional) Try it on a WIRELESS internal client using the server's IP address. If that works then
6. (optional) Try it on a WIRELESS internal client using the server's hostname. If that works then
7. Try in on an EXTERNAL client using the router's external IP address. If that works then
8. Try in on an EXTERNAL client using your custom subsonic hostname.

Follow in order, and if it does not work, tell us where it failed and the details of that step.

HTH,

Glenn

[schitonk]

Couple things...make sure DNS also points to your router/gateway and that you're allowing connections through the firewall in OS X. And make sure nothing else on your network is using that IP.