yet another connection issue

[jerryyyyy]

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.

Thanks, fixed that long ago. Still dead in the water.

[GJ51]

Did you uncheck the Autoconfigure?

Here are my revised guidelines for setup:

First read: http://monroeworld.com/android/subsonic/

Never use port 80 - ISP's often use it or block it. 8080,8081, work fine.

In Subsonic Settings/Network - UNCHECK " Automatically configure your router to allow incoming connections to Subsonic (using UPnP or NAT-PMP port forwarding)." make sure to hit the SAVE button, you may have to scroll down to see it depending on your screen size.

Manually assign a fixed intenal IP and static route to your server at the upper end of the address range of the router, out of the way of DHCP, e.g. 192.168.1.254

Set up your router manually. uPNP might work, but most often it doesn't. Learing how to do it will be a skill you'll love having as your network grows.

Check the Subsonic Control Panel to make sure it's using the right port you're going to use. I typically use 8080, 8081, etc.

Set up port forwarding in your router to direct traffic on the selected port to your server.

Learn your external IP address assigned by your ISP.

Test your setup by entering your external IP:port# to see if it connects. e.g.

http://24.88.76.61:4040/

If it works, you're good to go.

[alphawave7]

Agreed..only recent (2-3 year-old) routers have the UPnP capability..and I've seen some that claim to have it, but it simply doesn't work! Again, these things were supposed to be 'standards' compliant, but whatever!

[GJ51]

Even if it worked, it still pays dividends to know what it's doing and how to take control of it. I'm amazed at how many times, I'm thankful that I started computing with DOS 1.0 and had to learn the command line and batch file programming. As the home network grows and incorporates more and more devices. it really helps to know the ins and outs.

I bought my wife a Bose Wave with the Sound link adapter for Christmas. It took but a few minutes to have it streaming music from the server in the basement over Subsonic. When you understand how it wokrs, the possibilities are endless. My goal is to fully utilize Subsonic for all media distribution around the house and to all our remote devices/laptops when we're on the road. Only Subsonic makes this possible. For now it's the best solution available and it's unfortunate that some give up when trying to overcome the configuration hurddles, but then again some VCR's only show the correct time twice a day.

[jerryyyyy]

Did you uncheck the Autoconfigure?

Here are my revised guidelines for setup:

First read: http://monroeworld.com/android/subsonic/

Never use port 80 - ISP's often use it or block it. 8080,8081, work fine.

In Subsonic Settings/Network - UNCHECK " Automatically configure your router to allow incoming connections to Subsonic (using UPnP or NAT-PMP port forwarding)." make sure to hit the SAVE button, you may have to scroll down to see it depending on your screen size.

Manually assign a fixed intenal IP and static route to your server at the upper end of the address range of the router, out of the way of DHCP, e.g. 192.168.1.254

Set up your router manually. uPNP might work, but most often it doesn't. Learing how to do it will be a skill you'll love having as your network grows.

Check the Subsonic Control Panel to make sure it's using the right port you're going to use. I typically use 8080, 8081, etc.

Set up port forwarding in your router to direct traffic on the selected port to your server.

Learn your external IP address assigned by your ISP.

Test your setup by entering your external IP:port# to see if it connects. e.g.

http://24.88.76.61:4040/

If it works, you're good to go.

OK, you convinced me to reinstall with the 9 page instructions, but I am no better off.

I unchecked the plug and play.

I did not assign a fixed IP to the server as it should test correctly with its assigned IP as that should be good for weeks of testing.

I may be making progress because I cannot connect on my LAN. If I type the local IP into the address bar (http://192.68.0.5:8080). It does not connect. It does connect on localhost while on the server.

Seems like I should be able to connect via another computer on my home network, and I cannot do this.

This does not involve the modem/router.

[GJ51]

Then your most likely not getting the internal ip address correct. In your post you have 192.68.0.5, it is probably 192.168.0.5. If you can pull up the site as localhost, there is no reason that you can't get to internally. You have to be very precise identifying the address. The only thing that could prevent connection would be an internal firewall setting on the host computer, but that should be set automatically by Subsonic, and I've never seen this be an issue, ... yet.

Another possibility is that some setting on your local host is blocking access. Are you able to get into this computer in any way from a different computer on the network? Have you manually changed any network settings, firewall settings, or any other programs that could be interfering with access to the host system. Bottom line, if you have SS running ok as local host, it is almost a given that it should be functional on the local network. We're all missing something very basic here that is probably the root of the problem.

[GJ51]

In Windows, can you generate a network map in the Network and Sharing utility?

Control Panel/ Network and Sharing - "See full map" - top right corner.

Does it show you are on a Home network?

[jerryyyyy]

In Windows, can you generate a network map in the Network and Sharing utility?

Control Panel/ Network and Sharing - "See full map" - top right corner.

Does it show you are on a Home network?

Thanks,

You were right on the IP error. I can see the server from its sister computer at 192.168.0.5:8080.

This is on a Windows 7 home network.

canyouseeme.org still fails on 8080.

[GJ51]

OK, if you can see it within your network, it's now only a matter of getting the port forwarding set up properly.

Access your router's setup and open Port Forwarding/Port Triggering under Advanced in the main menu. Select the Port Forwarding radio button as the Service type. Select add a custom service. Put Subsonic in the service name block. Select the TCP protocol. Enter the Subsonic port number in both the beginning and end port blocks, in your case 8080 in both. In the server IP address, enter the address of your server that is hosting SS, 192.168.0.5 then click Apply.

That shoud do it. Let me know if you need someone to test from outside the network.

I'm also a bit curious as to why your address is at 192.168.0.5 when the default base address for the router is 192.168.1.1 Normally, unless you changed the base address of the router, the network would use 192.168.1.2 - 192.168.1.254 as it's useable address range?????

So, I ask, why is your server at 192.168.0.5 instead of 192.168.1.5?? It can be done and there isn't anything wrong with doing it that way, I'm just curious as to why you changed from the default addressing scheme used by Netgear for this router. Can you also confirm the address of the router?

Also, I think we may have covered this before, but can you confirm that your ISP Gateway device is not acting as the DHCP server? Only one device should be making the DHCP assignments.

[jerryyyyy]

OK, if you can see it within your network, it's now only a matter of getting the port forwarding set up properly.

Access your router's setup and open Port Forwarding/Port Triggering under Advanced in the main menu. Select the Port Forwarding radio button as the Service type. Select add a custom service. Put Subsonic in the service name block. Select the TCP protocol. Enter the Subsonic port number in both the beginning and end port blocks, in your case 8080 in both. In the server IP address, enter the address of your server that is hosting SS, 192.168.0.5 then click Apply.

That shoud do it. Let me know if you need someone to test from outside the network.

I'm also a bit curious as to why your address is at 192.168.0.5 when the default base address for the router is 192.168.1.1 Normally, unless you changed the base address of the router, the network would use 192.168.1.2 - 192.168.1.254 as it's useable address range?????

So, I ask, why is your server at 192.168.0.5 instead of 192.168.1.5?? It can be done and there isn't anything wrong with doing it that way, I'm just curious as to why you changed from the default addressing scheme used by Netgear for this router. Can you also confirm the address of the router?

Also, I think we may have covered this before, but can you confirm that your ISP Gateway device is not acting as the DHCP server? Only one device should be making the DHCP assignments.

I think I am back to where I was a few days ago. There is a Westell 2200 modem/router for the DSL. I believe this is numbered 192.168.1.1 but the Netgear 3700 is 192.168.0.1. and the computers to follow.

I have the port forwarding done on the Netgear but it would appear that the Westell also restricts the ports, i.e. it is not acting as a bridge. Was suggested I reprogram the Westell but I have to reset it to get into its settings and this is not worth a reset for me as I have to go back to ATT and redo all the settings... and after doing all that SS may still not work.

it goes ATT -> Westell -> Netgear -> SS

I restarted this to uncheck the UPNP portforwarding, but that did not solve the problem.

[GJ51]

That's where your problem is. You have to gain control of the Westell in order to control your network. According to DSL reports, resetting the modem DOES NOT out it in bridge mode.

http://rexonavn.com/westell-2200-dsl-mo ... anual.html

http://www.dslreports.com/faq/6323

These links might help.

Does resetting the Motorola 2210 put it in bridged ethernet mode?

No, but it is a very popular myth that is propagated by poor help desk training and urban legend. When you reset the 2210 it does not automatically default to bridged ethernet mode (which is the preferred mode if you run it in conjunction with a third party router). When the 2210 is reset and detects another router or PPP client it will use a feature called "PPP Passthrough" and hopefully let the other PPP client initiate the connection. Unfortunately, this does not always work as designed and it may cause connection problems.

The proper way to configure the 2210 in conjunction with a another router is to manually set it up in bridged ethernet mode as shown here.

These set up procedures may take some time and effort, but unless you do them, or get a different ISP, you will never gain control of YOUR network.

[jerryyyyy]

That's where your problem is. You have to gain control of the Westell in order to control your network. According to DSL reports, resetting the modem DOES NOT out it in bridge mode.

http://rexonavn.com/westell-2200-dsl-mo ... anual.html

http://www.dslreports.com/faq/6323

These links might help.

Does resetting the Motorola 2210 put it in bridged ethernet mode?

No, but it is a very popular myth that is propagated by poor help desk training and urban legend. When you reset the 2210 it does not automatically default to bridged ethernet mode (which is the preferred mode if you run it in conjunction with a third party router). When the 2210 is reset and detects another router or PPP client it will use a feature called "PPP Passthrough" and hopefully let the other PPP client initiate the connection. Unfortunately, this does not always work as designed and it may cause connection problems.

The proper way to configure the 2210 in conjunction with a another router is to manually set it up in bridged ethernet mode as shown here.

These set up procedures may take some time and effort, but unless you do them, or get a different ISP, you will never gain control of YOUR network.

OK, now we are getting somewhere!

The #$%$#$% IP address for the Westell 2200 is 192.168.1.254.

This was on the links. I actually found some better links using Westell 2200 enable bridge as my search.

http://www.dslreports.com/faq/6096

In any case, I am trying not to fully reset the model, though I can now see all my setting and I guess I could restore them if needed (my wife would kill me if I screwed up the connection due to her work).

There is the option for an IPPassthrough. I see that this would enable the external IP address to be accessed from my Netgear router (The Netgear router is listed as an option).

I think this would get SS to my port 8080 on the server.

But, when trying the settings it says it will reset the model. I hope this is a soft and not a hard reset ? Ideas?

[GJ51]

Yes. I always have ideas - but I always want another user to understand that any decisions or actions that they decide to take on their system are their responsibility. My sole purpose is to give you information that will he;p you make an informed decision. You sit in front of the screen in your home at your terminal and see what you are doing. It's not the same as me interpereting what you are telling me. The bottom line - anything you decide to do on your network is soley your responsibility. If something goes wrong, don't come back and tell me that I led you down the garden path to catastrophe.

I'm not trying to discourage you from moving on and making progress, I'm just trying to emphasize that the decisions are yours.

That said, I know taking the plunge is a bit scary, but if you've throughly read the documentation and understand what you are doing, you should be able to make these changes successfully. To be cautious, you might select a time when any problems caused would be least disruptive. If others don't need connectivity over the weekend, perhaps a Friday night is a good time.

Ask youself what's the worst case scenario, and what would your recovery plan be? Most Gateway devices are easily rebooted to the ISP's default settings. Some even have configuration settings save provisions that allow you to save your current setting to a file that can be restored if you want to revert to the original configuration. You are taking your first steps that will enable you to take full control of your network. That's a good thing, but I'm not going to tell that nothing can go wrong - it can. But if you've carefully done your homework, and understand what you would need to do to recover, you will be well positioned for success. If you can configure the Westell to just allow pass through to the Netgear router and allow it to take all control of the network, that would be my first choice for configuration. I have the same router and wish I could do that on my network as it would make admin much easier. Because my FIOS router won't let me do that, my Netgear is only functioning as an access point for wireless on my network.

Good luck whatever you decide, and users here will always be happy to give you as much support as we can, but you are now THE network administrator.

[jerryyyyy]

Yes. I always have ideas - but I always want another user to understand that any decisions or actions that they decide to take on their system are their responsibility. My sole purpose is to give you information that will he;p you make an informed decision. You sit in front of the screen in your home at your terminal and see what you are doing. It's not the same as me interpereting what you are telling me. The bottom line - anything you decide to do on your network is soley your responsibility. If something goes wrong, don't come back and tell me that I led you down the garden path to catastrophe.

I'm not trying to discourage you from moving on and making progress, I'm just trying to emphasize that the decisions are yours.

That said, I know taking the plunge is a bit scary, but if you've throughly read the documentation and understand what you are doing, you should be able to make these changes successfully. To be cautious, you might select a time when any problems caused would be least disruptive. If others don't need connectivity over the weekend, perhaps a Friday night is a good time.

Ask youself what's the worst case scenario, and what would your recovery plan be? Most Gateway devices are easily rebooted to the ISP's default settings. Some even have configuration settings save provisions that allow you to save your current setting to a file that can be restored if you want to revert to the original configuration. You are taking your first steps that will enable you to take full control of your network. That's a good thing, but I'm not going to tell that nothing can go wrong - it can. But if you've carefully done your homework, and understand what you would need to do to recover, you will be well positioned for success. If you can configure the Westell to just allow pass through to the Netgear router and allow it to take all control of the network, that would be my first choice for configuration. I have the same router and wish I could do that on my network as it would make admin much easier. Because my FIOS router won't let me do that, my Netgear is only functioning as an access point for wireless on my network.

Good luck whatever you decide, and users here will always be happy to give you as much support as we can, but you are now THE network administrator.

Well, you should get one of these great Westell 2200 routers

As you can tell from my caution I am very careful after a few years of programming (If not broken, don't fix it) but I do push the envelop.

I think I will see if I can chat with ATT tech support and see how bad it would be if I screw it up. My recall was that it was 30 min to set it up again and if I have a screensave of all the current settings, it would be pretty easy.

I doubt that the ipforwarding would hard reset the modem. This is my preference as I would not have to change anything and SS would work.

I will be getting a new ISP in a couple months so at that time I will have to set this up again but can do it correctly from the start, so this is a good education.

>>>>> later

I did the reset and the IPPassthrough for the modem does not appear to have helped.

[jerryyyyy]

I had to change the port of the Netgear as it changed with the reboot of the router. But canyouseeme now sees 8080.

I'll make a static connection to that port in a bit.

Thanks for the encouragement.