Bridge connects wired devices to network but not internet

[overdrive31]

You changed end point filtering on the router? Does your ISP use DHCP or PPPoE? If your 2wire is bridged and using PPPoE, the PPPoE settings are required to be on the Dlink. You mentioned not seeing the music server netbios names in explorer, under http://192.168.0.1/Basic/Network.shtml you can enable Netbios announcement which may fix that. WPS settings exist on the 1522 as well, the Dlink users saying it effected functionality, didn't specify which to disable. What firmware versions are the router and bridge? If web access was never tried with just 2wire setup, the ISP could be blocking TCP 9000, can't you set a custom port, then use virtual server to accept the custom public port and point to 9000(or w/e port you setup) private port. You're sure gateway and DNS settings are correctly entered on the NAS? The reason I suggested DHCP reservation(static DHCP) is to be sure the problem devices got the proper settings they needed and that maybe for some reason port forwarding wouldn't function with client assigned static addressing. The WPS may need to be disabled on both the router and bridge for what Dlink users of these devices say disrupts internet and/or media sharing. I mentioned Enable Multicast Streams, it can have an effect on internet radio stations and the setting is found here http://192.168.0.1/Advanced/Network.shtml

 

[Mike Rubin]

You changed end point filtering on the router? Does your ISP use DHCP or PPPoE? If your 2wire is bridged and using PPPoE, the PPPoE settings are required to be on the Dlink. You mentioned not seeing the music server netbios names in explorer, under http://192.168.0.1/Basic/Network.shtml you can enable Netbios announcement which may fix that. WPS settings exist on the 1522 as well, the Dlink users saying it effected functionality, didn't specify which to disable. What firmware versions are the router and bridge? If web access was never tried with just 2wire setup, the ISP could be blocking TCP 9000, can't you set a custom port, then use virtual server to accept the custom public port and point to 9000(or w/e port you setup) private port. You're sure gateway and DNS settings are correctly entered on the NAS? The reason I suggested DHCP reservation(static DHCP) is to be sure the problem devices got the proper settings they needed and that maybe for some reason port forwarding wouldn't function with client assigned static addressing. The WPS may need to be disabled on both the router and bridge for what Dlink users of these devices say disrupts internet and/or media sharing. I mentioned Enable Multicast Streams, it can have an effect on internet radio stations and the setting is found here http://192.168.0.1/Advanced/Network.shtml

Overdrive: (1) I only changed the end point filtering for a few minutes last night while looking at the router's firewall screen. Changing it had no effect on my other issues, so I set it back to the defaults after a few minutes. (2) I am an early PacBell ADSL adopter, so I actually have a static IP address. (Yes, I know that everyone assumes that I am wrong about that, but, trust me, I can't use many routers' automated setup because I need to enter all the address, gateway, and DNS information manually.) (3) I don't think there's an issue with NetBIOS addressing; I see the netbios information for my devices all over my file managers and in my iPhone netscans. The failure of shares to display turns out to be an erratic problem solvable usually by refreshing the network scan or by using a different file manager. (4) I only turned off WPS on the router, but I can't find a way to disable it on the bridge. The bridge's web interface only has a very few settings available for adjustment and WPS does not seem to be one of them. (5) The router is a firmware update behind (2.02), and I've been reluctant to upgrade because the newer firmware is not getting rave reviews in the D-Link, forums. The bridge is at the current firmware level. (6) I don't know how to set a custom port but I'll figure that out tonight and let you know if it makes a difference. (7) I just double-checked the NAS' setup screen and the gateway is properly entered. For DNS, I am just pointing at the router, but I had the same results earlier when I pointed at the ISP's DNS preferences. (8) The behavior was the same when I reserved the music server's addresses rather than set them manually. I did not try that with the NAS, though, so I'll try that tonight. (9) I just enabled the multicast streams function, but can't stick around while the WLAN reboots and devices find their way back to it. I'll check this tonight, too.

Thanks so much for your suggestions. I have taken a great deal of your time and appreciate your generosity.

 

[overdrive31]

Just wanted to be sure the 2wire was bridged and not dual-nat.

Web access manual http://buffalonas.com/manual/en/ shows like three different setup instructions based on visual queues, if it looks like this click here..

On two of them it allows only to change the external(public) port which may be required to bypass any ISP block of TCP 9000 by setting a custom port. On one it allows setting both internal(private) and external(public) ports to custom. I think no matter what version of these, the external(public) port is all that needs changing and that the internal(private) port will always be 9000 unless changed by the one setup that features the option. However, port forwarding can't handle mismatch external/internal ports, so the virtual server(port mapping) setting which can map an external(public) port to an different internal(private) port is done easily and securely.

 

[Mike Rubin]

Thanks very much again. Since I last posted, I tested the multicast streaming and found it made no difference; I learned there's a recent firmware upgrade for the bridge, so will add that this weekend; and was unable to see the settings options that you picture on the bridge admin page. Just a moment ago, though, I saw on the D-Link forum that the bridge's firmware access works properly only when it's accessed by Internet Explorer, which explains why I could not see it with the two browsers I use, Safari and Firefox. I'll certainly try using Internet Explorer to disable WPS on the bridge this weekend. Finally, the Bufalonas pages you linked are the very pages I used to try to set up my NAS and, as you know, I've not gotten it to see the internet with my new router.

At this point, I am inclined not to focus so much on the bridge and, instead, focus on the router. With my old 2wire, I could use BitTorrent on the NAS and get internet radio, wirelessly, on the music servers. This weekend, I will take one of the routers from my hi-fi cabinet downstairs to my office and connect it to the router using Ethernet. Given that the NAS always has been connected to the router, if I can't get internet radio on music server, I'll conclude the issue is with the router and not the bridge, because I doubt that both the NAS and two musical servers all experienced their own failures around the same time that I, coincidentally, got a new router.

I appreciate very much all of your assistance and your generosity. I'll post here what I find out after connecting the music server directly to the router. I also am going to try both D-Link and Buffalo tech support again, as it seems from those manufacturers' forums that others have had similar troubles and in some cases have solved them. If, as I suspect, I have a router issue, I guess I'll take my inquiries to another sub-forum here.

 

[overdrive31]

Bittorrent may have worked with the 2wire, but recent firmware versions for the Linkstations have switched to using port 9090 rather than 8080. If you have updated the firmware on it since using it with the 2wire, I suggest reading firmware change logs before updating in the future. Wouldn't changing the external port for web access be a simple task as well as port mapping said external to the internal port 9000 using virtual server? There is another factor that may keep the music servers from receiving internet radio streams, but you said you used the ISP DNS and if so this would not be a factor, a feature called Advanced DNS Service in the router utilizing OpenDNS which could possibly filter some aspects of connectivity.

 

[Mike Rubin]

Overdrive:

(1) I haven't updated the NAS firmware at all, but I will try 9090 for Bittorrent, too. (BTW, I am not really a torrent user, but I followed a suggestion on the Buffalo forum to installt the Bittorrent PC client and see if IT would work and it does, indeed.)

Also, I don't know if I pointed out before that, when trying to configure the NAS for web access, I keep getting a "no UPNP gateway" error. That seems weird because I have UPNP enabled and working well from Foobar on my PC, the NAS itself, and both music servers, to two iPhone apps and both music servers.

(2) I tried using Virtual Server on the D-Link but had no more success with it than with port forwarding. Maybe I am just doing those things incorrectly, so I will try calling D-Link tech support AGAIN tonight and hope they can help me fill in the configuration blanks properly. (I have had the worst luck ever, truthfully, with that support; I either don't get connected to anyone at all and only get a "call back later" message OR, after 30 minutes on hold, I do get connected, can barely hear a thing over the static-y connection, and the call fails entirely.)

(3) When I set up the new router, I was given the option, but chose not, to enable the (recommended) Advanced DNS Service because I was concerned about its effects. I kept the ISP DNS settings if for no other reason than they were the known devils. (I was working consciously to duplicate all of the 2wire settings since, range and n-support and re-boot issues aside, it did everything I asked of it.)

I am reaching the point, I think, where I realistically have to decide whether the inability to use the Buffalo Webphone NAS access application, bittorrent on the NAS, and internet radio on the servers are worth the time and effort that you and I and other folks who've offered suggestions have put into this cleanup effort. The new router, range extender, and bridge have solved the very problems that I wanted them to solve, and apparently this is the collateral damage. As always, I appreciate your help.

 

[overdrive31]

If you read the Buffalo NAS web access manual, it explains that if UPnP doesn't happen to work, even though it works for other devices, to disable UPnP on the NAS and fall back to port forwarding. I explained that since trying to forward port TCP 9000 and it not working, it had to be dual-nat(why I asked about the 2wire bridge status) or ISP filtering of ports, you are going to have to pick a custom port to enter on the NAS web access setup. Once you have the custom external port setup, you must put this port # in virtual server in the public spot, the NAS still uses port 9000 internally and isn't subject to filtering so you will put it in the private spot. done! This is the third time I have explained this and you continue to dismiss it. If you try one custom port and it doesn't work, keep trying different ones or call your ISP to ask what ports they happen to filter. Virtual Server allows port mapping, which is what I am trying to explain, by pointing one external port to any port you choose internally or vice-versa.

 

[Mike Rubin]

Honestly, I am not dismissing it. I am grateful for your help. I have tried to do what you've suggested, but I think I must have been doing it incorrectly, which is why I thought I ought to have D-Link walk me through the entries in the web interface as I made them. I will try it again, I assure you. I just did not want to take up so much of your time when I was not having success. Thanks again for responding.

 

[overdrive31]

If you follow my instructions you shouldn't have a problem. One more time step by step very slowly.

1.(a) Using the Buffalo NAS web access manual to find the instructions for your model, locate the setup page.
1.(b) Enter your chosen buffalonas.com name
1.(c) Disable UPnP
1.(d) Enter your chosen custom port in the emtpy dialog box labeled External Port and write this port # down for later, hit Apply.

2.(a) Log into the router and create an Virtual Server entry labeled WebAccess in the Name dialog box.
2.(b) In the dialog box labeled Public enter the port # you saved in step 1.(d)
2.(c) In the dialog box labeled Protocol choose TCP.
2.(d) In the dialog box labeled IP Address enter the IP you have given the NAS.
2.(e) In the dialog box labeled Private enter 9000
2.(f) Ignore all other dialog boxes in the entry
2.(g) In the check mark box to the left of this virtual server entry, give it a check mark
2.(h) Hit Save Settings.

3. Open your browser to http://buffalonas.com/ and enter the name of your NAS you chose in step 1.(b).

4. Hit Connect

5. What are the results? If still doesn't work, either call your ISP to ask what ports they might filter or go to step 6.

6. Repeat steps starting with 1.(d) changing to a different custom external port, skip steps 2.(a) and 2.(c) through 2.(g).

 

[Mike Rubin]

Thanks for setting this out in such detail. I do think it's what I was doing when I tried manual port-setting on the NAS and port-forwarding on the router before, but I will follow your instructions explicitly and we'll see how I do.

 

[Mike Rubin]

Overdrive, I cannot thank you enough. I think the problem before was that identified external ports that weren't numbered high enough to be available for use. When I chose a number at the high end of the range, I was able to get web access, finally. I had some log-on issues that I resolved with Buffalo tech support, but I was able to get this to work. I appreciate both your patience with me and the breadth of your knowledge. I owe you big time.

 

[overdrive31]

Glad you got that working finally, and I have a couple options for solving the other issue with the bridge.

Traditionally, a bridge doesn't require an IP address of it's own on the sub-network. These days, using consumer brand bridges, they do get assigned IP addresses on your network for simplicity. This difference could be the cause of internet communication troubles for some devices that utilize such a bridge. The bridge uses 192.168.0.50 as it's default IP, which also happens to exist in the same subnet as your D-Link DIR-825's 192.168.0.1 address, that being the case it is not traditionally how a bridge would function. Lets say you set the bridge to use 169.254.1.1 static IP with subnet mask of 255.255.0.0 to support, for configuration setup, any wired DHCP clients connected to the bridge, not connected to a router, getting an APIPA address in the range of 169.254.0.0 -169.254.255.255. Then configure wireless to connect the bridge and router. It now would be operating like a traditional bridge, and chances are your problems may go away.

Sometimes firmware developers will fix things that they deemed not important enough to list on the change log/release notes. Try updating to version 2.05, you can always go back to 2.03. Another thing you might try is DD-WRT for the DIR-825 B.

Something I have learned about using a bridge with the DIR-825, is the bridge needs an IP within the DHCP reservation list for most things to function(specially hosted services needing port forward), so static addressing is out. Another thing is QoS really messes with RTP/RTCP traffic, had to turn it off for some things to function.