yet another connection issue

[GJ51]

When you register the web address, the information is going out from your network to the Subsonic.org server. That's not a big deal. Trying to get INTO your network from outside is another matter alltogether that requires that the router and server be properly configured to recieve the outside request for data, and that it gets to your server on the designated port.

Although some users may have success using Plug and Pray, I've never had it work for me over the years, and just bit the bullet and learned to do the manual setup in the router. If your going to run a server and an expanding home network, it's a skill you're going to need anyway. There's no time like the present.

[jerryyyyy]

When you register the web address, the information is going out from your network to the Subsonic.org server. That's not a big deal. Trying to get INTO your network from outside is another matter alltogether that requires that the router and server be properly configured to recieve the outside request for data, and that it gets to your server on the designated port.

Although some users may have success using Plug and Pray, I've never had it work for me over the years, and just bit the bullet and learned to do the manual setup in the router. If your going to run a server and an expanding home network, it's a skill you're going to need anyway. There's no time like the present.

Yes, indeed. Well I am biting the bullet.

I tried to set up tonight but a bit like a Chimp typing War and Peace.

My WF router is a NetgearWNDR3700

I got my external IP from whatismyip.com: like 76.36.XXX.YY

The static router:

Destination IP: 76.36.XXX.YY
Mask 255.255.255.255
Gateway IP 192.168.0.250
Metric 8

Portforward settings:

Protocol TC/IP
Start Port 8080
End Port 8080
Static IP 192.168.0.250

I guess this is not correct as instructions assume you know what you are doing....

The test http://76.36.XXX.YY:8080 does not work...

Any help for a Chimp?

PS The router is 192.168.0.1 and the computer 192.168.0.3 that is running SubSonic....

[alphawave7]

When you register the web address, the information is going out from your network to the Subsonic.org server. That's not a big deal. Trying to get INTO your network from outside is another matter alltogether that requires that the router and server be properly configured to recieve the outside request for data, and that it gets to your server on the designated port.

Although some users may have success using Plug and Pray, I've never had it work for me over the years, and just bit the bullet and learned to do the manual setup in the router. If your going to run a server and an expanding home network, it's a skill you're going to need anyway. There's no time like the present.

Yes, indeed. Well I am biting the bullet.

I tried to set up tonight but a bit like a Chimp typing War and Peace.

My WF router is a NetgearWNDR3700

I got my external IP from whatismyip.com: like 76.36.XXX.YY

The static router:

Destination IP: 76.36.XXX.YY
Mask 255.255.255.255
Gateway IP 192.168.0.250
Metric 8

Portforward settings:

Protocol TC/IP
Start Port 8080
End Port 8080
Static IP 192.168.0.250

I guess this is not correct as instructions assume you know what you are doing....

The test http://76.36.XXX.YY:8080 does not work...

Any help for a Chimp?

PS The router is 192.168.0.1 and the computer 192.168.0.3 that is running SubSonic....

You don't need to do anything with the router's IP. You will set up a port forward for 8080, on the 192.168.0.3 address only. It appears you'll need to select 'Add custom service' and call it Subsonic, select TCP, start port 8080, end port 8080. Save, then reboot router. Test with canyouseeme.org.

[GJ51]

OK, I know it can be a bit confusing, in fact you've got me a bit confused, but I'm sure we can sort it out. From your post, I can't understand what you've set to 192.168.0.250. Usually the router is the gateway device on the network or it's a device provided by you ISP. The Gateway device also can, but doesn't have to be the DHCP server. In any event you also want to make sure that you don't have both devices doing DHCP or things get really messed up.

Assuming your Netgear router is doing the DHCP services for your network, it will typically be at the base address for the internal network. In your case you are stating that it is at 192.168.0.1. That should be fine. You can set up your server to sit at any valid open address as long as it's within the defined range that the router can use. In your setup, I'm assuming that the range is 192.168.0.1 to 192.168.0.255. You have listed that there is a Gateway device at 192.168.0.250. This may be true, but I've never encountered a network set up like this. I'm not saying that it can't be done that way, just that I've never seen it.

If that is in fact, the way it is, I would assign my server to 192.168.0.249, just below the Gateway device. The reason I put my servers up high out of the way of the lower address range is because I have seen DHCP assign the same address to two different computers on the same network occasionally. It doesn't happen often, but if it does, you'll scratch your head for a while trying to figure out why things aren't working until you figure out what happened. Putting the server way up high avoids the whole issue and eliminates a problem that can happen as routers will assign DHCP addresses from the bottom up.

OK - So, if I know what I'm trying to accomplish with my network configuration, it's only a matter of getting the configuration details right with my equipment. I start at the server and go into control panel and bring up the configuration details for my NIC (network interface card). There will be a screen in there that allows you to specify wether the NIC uses a DHCP address automatically obtained from the server, or uses an address that you define. Here is where you want to assign an open address in the uppere end of the router's address range. In windows, I open control panel, go to the network and sharing center, then click on Change Adapter settings in the left column. Select the Local Area Connection, Properties, then highlight Internet Protocol version 4, and click Properties again. That reveal all the deep dark settings in Windows for the NIC. Assign the IP address e.g 192.168.0.249, Subnet mask leave at 255.255.255.0, enter your default gateway address, then use your router address and the gateway address for the DNS server addresses unless you know better ones. You can find out what your ISP DNS server addresses are by poking around in your Gateway device and use those, or any other good ones that can be found on the net. Reboot the server and it should now show up in your router at the new address. Now if you have SS set up to use 8080, then the internal address of SS will be 192.168.0.249:8080. If you test, and all that is working, now all you have to do is connect the dots on the router.

To go further I need to know what device is actually doing the DHCP, the netgear or you gateway device. If it's the Netgear, read chapter 5 of the manual at

ftp://downloads.netgear.com/files/WNDR3 ... CT2009.pdf

Pay speciall attention to the section on port forwarding and address reservation.

[jerryyyyy]

OK, I know it can be a bit confusing, in fact you've got me a bit confused, but I'm sure we can sort it out. From your post, I can't understand what you've set to 192.168.0.250. Usually the router is the gateway device on the network or it's a device provided by you ISP. The Gateway device also can, but doesn't have to be the DHCP server. In any event you also want to make sure that you don't have both devices doing DHCP or things get really messed up.

Assuming your Netgear router is doing the DHCP services for your network, it will typically be at the base address for the internal network. In your case you are stating that it is at 192.168.0.1. That should be fine. You can set up your server to sit at any valid open address as long as it's within the defined range that the router can use. In your setup, I'm assuming that the range is 192.168.0.1 to 192.168.0.255. You have listed that there is a Gateway device at 192.168.0.250. This may be true, but I've never encountered a network set up like this. I'm not saying that it can't be done that way, just that I've never seen it.

If that is in fact, the way it is, I would assign my server to 192.168.0.249, just below the Gateway device. The reason I put my servers up high out of the way of the lower address range is because I have seen DHCP assign the same address to two different computers on the same network occasionally. It doesn't happen often, but if it does, you'll scratch your head for a while trying to figure out why things aren't working until you figure out what happened. Putting the server way up high avoids the whole issue and eliminates a problem that can happen as routers will assign DHCP addresses from the bottom up.

OK - So, if I know what I'm trying to accomplish with my network configuration, it's only a matter of getting the configuration details right with my equipment. I start at the server and go into control panel and bring up the configuration details for my NIC (network interface card). There will be a screen in there that allows you to specify wether the NIC uses a DHCP address automatically obtained from the server, or uses an address that you define. Here is where you want to assign an open address in the uppere end of the router's address range. In windows, I open control panel, go to the network and sharing center, then click on Change Adapter settings in the left column. Select the Local Area Connection, Properties, then highlight Internet Protocol version 4, and click Properties again. That reveal all the deep dark settings in Windows for the NIC. Assign the IP address e.g 192.168.0.249, Subnet mask leave at 255.255.255.0, enter your default gateway address, then use your router address and the gateway address for the DNS server addresses unless you know better ones. You can find out what your ISP DNS server addresses are by poking around in your Gateway device and use those, or any other good ones that can be found on the net. Reboot the server and it should now show up in your router at the new address. Now if you have SS set up to use 8080, then the internal address of SS will be 192.168.0.249:8080. If you test, and all that is working, now all you have to do is connect the dots on the router.

To go further I need to know what device is actually doing the DHCP, the netgear or you gateway device. If it's the Netgear, read chapter 5 of the manual at

ftp://downloads.netgear.com/files/WNDR3 ... CT2009.pdf

Pay speciall attention to the section on port forwarding and address reservation.

Thanks.

Let me try to clarify. I am in California and my ISP is ATT/DSL. I have a DSL modem that connects to the Netgear router.

The Netgear router is indeed at 192.168.0.1.

I tried to set up the static route for the subsonic server 8080 port at 192.168.0.250.

The computer on the local network with the subsonic server is at 192.168.0.3.

The Netgear settings say I get the IPs dynamically from the ISP as well as the DNS.

I think I have all the pieces, but I cannot fit them into the right boxes on the options in the Netgear Control Panels (I have read and reread Chapter 5)... I really do not get the relationship between the static routing and the port forwarding. Seems like I should just be able to do this with manual port forwarding settings.

This must be an obvious dumb error on my part.

[GJ51]

You don't need to set up a static route for Subsonic and assign it an internal IP address. Terminology with routers can be confusing as they don't all use the terms the same way. The term server can get ambiguious as well as it can refer to both a software program and/or the physical hardware that hosts the software. An internal network IP address such as 192.168.0.250 is typically assigned to the hardware, that is the computer that hosts the program. Setting up the entry in the router lets the router know which computer to send traffic to by linking the internal IP address to the MAC address on the NIC in the server. THERE is NO need to assign Subsonic an internal IP address as it is just a process running on a computer that already has an internal IP address.

What Subsonic needs to get it's data traffic is a unique port number, which listens on that computer for its data. When a request for Subsonic comes into your network on that port through your router, the router uses the port forwarding rule for that port to look up and pass the data to the proper MAC address, thus getting the request to the proper internal IP address, that is, the computer that hosts SS. When the computer gets the request, the Subsonic service sees that it is traffic on the port that it listens to and the link is then made to Subsonic.

When I suggest using a high address for the "server" I'm reffering to the physical computer that hosts Subsonic, not Subsonic itself.

I do apologize. After almost 30 years of doing this stuff, it's all too easy to lose sight of how complicated and confusing it can get to someone that is just getting into it. I think you have all the pieces here, but if you still run into a wall, let me know and we can set up a skype call or some other way to help you get straightened out. For a Netgear router they use "Address Reservation" rather than "Static Route" as a way to assign the internal IP to a computer.

Let me know if you need more help. Once you get it set up, it'll seem easy and you'll be happy you got a good foundation for troubleshooting network issues.

[alphawave7]

"I tried to set up the static route for the subsonic server 8080 port at 192.168.0.250.

The computer on the local network with the subsonic server is at 192.168.0.3."

All you need to do is set up a 'Custom Service' in port forwarding, call it Subsonic, open port 8080, TCP for both start and stop, associate it with 193.168.0.3 if allowed to do so. Reboot router, and test with canyouseeme.org using 8080.

[jerryyyyy]

"I tried to set up the static route for the subsonic server 8080 port at 192.168.0.250.

The computer on the local network with the subsonic server is at 192.168.0.3."

All you need to do is set up a 'Custom Service' in port forwarding, call it Subsonic, open port 8080, TCP for both start and stop, associate it with 193.168.0.3 if allowed to do so. Reboot router, and test with canyouseeme.org using 8080.

I did all this and rebooted and it did not work.

I discovered that my DSL model I expect probably has another firewall. It is a Westell 2200 and looking at the manual, it seems to have enough settings to create one.

http://www.lava.net/support/Westell_220 ... tion_Guide

I tried to login at 192.68.1.1 as it says in the manual and could not. On the instructions it says to reset to login- that is all I need is a reset modem and calling ATT.

Suggestions to login without resetting?

[alphawave7]

"I tried to set up the static route for the subsonic server 8080 port at 192.168.0.250.

The computer on the local network with the subsonic server is at 192.168.0.3."

All you need to do is set up a 'Custom Service' in port forwarding, call it Subsonic, open port 8080, TCP for both start and stop, associate it with 193.168.0.3 if allowed to do so. Reboot router, and test with canyouseeme.org using 8080.

I did all this and rebooted and it did not work.

I discovered that my DSL model I expect probably has another firewall. It is a Westell 2200 and looking at the manual, it seems to have enough settings to create one.

http://www.lava.net/support/Westell_220 ... tion_Guide

I tried to login at 192.68.1.1 as it says in the manual and could not. On the instructions it says to reset to login- that is all I need is a reset modem and calling ATT.

Suggestions to login without resetting?

Lemme read the manual right quick...you have this modem, and a separate router or just the modem? What model router is it, if so?

edit: nevermind..I found your Netgear router mentione above! /sigh

[alphawave7]

Westell is proving to be a bear, even to find a pdf manual. I did find this on dslreports: http://www.dslreports.com/faq/6323
It says 192.168.1.254 for that particular firmware version...give that addy a try. http://www.dslreports.com/faq/7074

edit: the key here I see mentioned repeatedly is you want the Westell to be in 'Bridge Mode' only, which should have all of it's services (incl. firewall) disabled. I think a full reset, followed by the standard VC1 config, and then Bridged, is the way to go.

edit2: Lookie: Netgear/Westell setup: http://www.dslreports.com/faq/7815

[jerryyyyy]

Westell is proving to be a bear, even to find a pdf manual. I did find this on dslreports: http://www.dslreports.com/faq/6323
It says 192.168.1.254 for that particular firmware version...give that addy a try. http://www.dslreports.com/faq/7074

edit: the key here I see mentioned repeatedly is you want the Westell to be in 'Bridge Mode' only, which should have all of it's services (incl. firewall) disabled. I think a full reset, followed by the standard VC1 config, and then Bridged, is the way to go.

edit2: Lookie: Netgear/Westell setup: http://www.dslreports.com/faq/7815

I appreciate the effort and it was a learning process but the 192.68.1.254 does not get me in and I do not want to reconfigure the modem/router.

Think it is time to cut my losses with this before I screw the system up.

Thanks again.

[GJ51]

Sorry to hear you weren't able to crack it. Some ISP's throw up a lot of roadblocks because they don't want to deal with the increased bandwidth streaming consumes. Subsonic is still a good media server for your local network. You can also call your ISP and see if they are willing to help you, but admittedly, that's a long shot.

[alphawave7]

I suspect your Westell is already in bridged mode, and the firewall is inactive, and it's the Netgear still blocking access. Just holler if you want to revisit it!

[jerryyyyy]

I suspect your Westell is already in bridged mode, and the firewall is inactive, and it's the Netgear still blocking access. Just holler if you want to revisit it!

I am a glutton for punishment, but I just do not know where to take it from here. I am in Silicon Valley/Stanford and got that Modem/Router down at Fry's electronics as the "best" I could get after having lost 2 prior ones from ATT. Unfortunately, does not look like I can get into the modem without resetting it. The Netgear seems to be set-up correctly.

In the next 6 months my home will get high-speed fiber and will have a new modem. At that point I can customize the system to do all...

[alphawave7]

I just noticed this setting from way above:

"Portforward settings:

Protocol TC/IP
Start Port 8080
End Port 8080
Static IP 192.168.0.250 "


I think the last octet should be 192.168.0.3, which is the server machine.