Soulkeeper is right, your wired and wireless networks are still on different IP segments. Changing the subnet to 255.255.0.0 for both networks would fix it, but so would putting both wired and wireless clients on the same network. Since you don't have administrative access, looks like it is a Tech Support issue. Bummer. Alternately, you could install an additional router "behind" the ISP router that would allow you to completely control your internal network, but that gets a bit complicated.
What ISP does not give you access to configure your network as you see fit?
Results 11 to 13 of 13
-
2011-04-01, 20:59 #11It all started with a Squeezebox Duet...
-
2011-04-02, 01:11 #12
One way to check if the Controller and Player (and NAS) are on the same subnet is to find their IP addresses, and then PING them. If they respond, use the command "arp -a" (This is the Windows format) to see if the IP addresses turn up in your ARP list.
If they do, then you are all on the one subnet. If they don't, then you're not.
-
2011-04-05, 23:01 #13Junior Member
- Join Date
- Mar 2011
- Location
- Denmark
- Posts
- 13
Things working properly now
Dear Natex, Soulkeeper and Swiftie
Thanks for all your advices and help. Things are working properly now. NAS installed with Squeezebox Server wired to the router in one end of the house and the Squeezebox receiver and controller in the livingroom at the other end by WIFI; actually playing both internet radio stations and music from my Squeezebox Server.
The ISP tech support bridged the two subnets (wired and wireless clients) in the router configuration et voila: Music all over.

Reply With Quote

