Page 1 of 1

LAN and WLAN issues

Posted: Tue Oct 06, 2009 10:06 am
by hudsonmanx
We have a TwonkyMedia server in a corporate environment, however our LAN and WLAN unfortunately are separate subnets.

I can ping the server from the WLAN however I dont seem to be able to get our PS3 or Xbox 360 to see it on the WLAN.

Any ideas how to solve this, I know this is not an ideal setup but just wondered if anyone found a solution.

Our SonicWALL TZ210 Wireless N router/firewall servers IP's by DHCP to the LAN and WLAN.


Re: LAN and WLAN issues

Posted: Tue Oct 06, 2009 8:10 pm
by PeeBee
Can you open up the subnet mask used on the LAN and WLAN?

For example, if your LAN is on 192.168.1.x and your WLAN is on 192.168.2.x and you have a subnet mask of then the 2 subnets will not be able to see each other. If you opened the mask up to then anything on 192.168.x.x would be able to see each other.


Re: LAN and WLAN issues

Posted: Thu Oct 08, 2009 1:40 pm
by Briain
You could 'pin' a DHCP address to the Twonky server (MAC address binding) to ensure it always gets the same IP address from the DHCP pool (all my stuff is set up like that; it's a great scheme to use), then maybe set up a static route for the (now effectively fixed) media server's IP address? Setting up static routes is not something I've personally experimented with, but my understanding is that it should be quite easy to do (though it depends on the options available with your router).


Re: LAN and WLAN issues

Posted: Fri Oct 23, 2009 11:13 am
by hudsonmanx
I tried changing subnets to and wasnt helpful as I have a site-to-site VPN to my office so it knocked that out.

For some reason with SonicWALL firewalls these kinds of devices dont work so well.

Re: LAN and WLAN issues

Posted: Wed Nov 11, 2009 4:28 pm
by cds

it is obviuos that changing the netmask is not working.
In the used setup the 192.168.1.x and 192.168.2.x are physically different networks with a router inbetween.
If a .1 client wants to talk to an .2 client it needs the router to forward the packets - and vice versa.
What would be needed here would be bridging the two networks, but this would mean changing the architecture here - and I'm pretty shure someone seperated the two networks by purpose.

Right now I'm struggeling with the same problem: I want to see my Twonkyserver at home through a VPN-Tunnel from outside.

The Problem is that a UPnP-Server uses multicast to make itselve visible to all the clients. Multicast-packets are not routed from one Network to an other, and I have not found a way to do so easily.

If I find a way I'll let you know .