Chromebook network access to devices on a different internal subnet
Looking for information regarding Chromebook networking capabilities specific to working among multiple subnets. For example a LAN that has multiple physical or VLAN subnets, can the Chromebook communicate with devices on a different subnet. Let's say the Chromebook is on VLAN 1 which uses 192.168.1.0/24, so the Chromebook receives an IP address of 192.168.1.10. This VLAN is connected to a Layer 3 Switch that also has VLAN 2 attached using 192.168.2.0/24 and configured to allow traffic in both directions of VLAN 1 to VLAN 2 and VLAN 2 to VLAN 1. Let's say I have a Windows system on VLAN 2 at 192.168.2.20. Both the Chromebook and Windows system have the appropriate/respective Default Gateway pointing to the Layer 3 Switch. Could these two devices communicate?
The Chromebook has the capability to talk to devices on any attached network as long as it has a path to the device and the device has a path to it.
If it can connect to the vast number of systems on the Internet...
If it can connect to the vast number of systems on the Internet...
ASKER
Yes, as I described in detail the subnets on the two VLANs connecting to the same Layer 3 switch have full access to each other. I can communicate with Windows devices on each subnet/VLAN, but not a Chromebook to Windows device. The Windows device on the same subnet/VLAN as the Chromebook allows for communication between that Windows device on the same subnet/VLAN and the Chromebook.
That sounds a little strange. For the sake of clarity, could you give specifics on what exactly you're trying to do? I think that'll make more sense with trying to help resolve.
This is a general networking question and not a hardware question. Replace Chromebook with "a Device"
Physically there is no restriction to connect from any address to any other address. There does have to be a path from one lan segment to another lan segment AND the traffic cops have to allow the traffic to pass in both directions.
You will have to ask your network designer if it is possible as they set the paths and the inter-lan rules
Physically there is no restriction to connect from any address to any other address. There does have to be a path from one lan segment to another lan segment AND the traffic cops have to allow the traffic to pass in both directions.
You will have to ask your network designer if it is possible as they set the paths and the inter-lan rules
This behavior could be caused by settings in the Windows Firewall on the target system.
What applications or protocols are the Chromebook trying to use to talk to the Windows devices?
What applications or protocols are the Chromebook trying to use to talk to the Windows devices?
ASKER
Apologies, the end user just clarified the situation with very pertinent information. He is attempting to use Chromecast from a laptop on one subnet to a TV on another subnet that has the Chromecast dongle.
it still comes down to networking. If the routes are setup correctly which is probably not doable with soho hardware.
i.e.
Internet (x.x.x.x) - Router 1 - 192.168.0/24 - lan port 1 - router 2 - 192.168.1/24 - laptop (192.168.1.100)
- lan port 2 - router 3 - 192.168.2/24 - TV (192.168.2.50)
to go from the laptop to the tv
laptop -> router 2 -> router 1 -> router 3 ->chromecast
router 1 would have to know to send traffic to 192.168.1/24 to port 2, and 192.168.2/24 to port 3. Normally It would send it out its gateway to the internet.
i.e.
Internet (x.x.x.x) - Router 1 - 192.168.0/24 - lan port 1 - router 2 - 192.168.1/24 - laptop (192.168.1.100)
- lan port 2 - router 3 - 192.168.2/24 - TV (192.168.2.50)
to go from the laptop to the tv
laptop -> router 2 -> router 1 -> router 3 ->chromecast
router 1 would have to know to send traffic to 192.168.1/24 to port 2, and 192.168.2/24 to port 3. Normally It would send it out its gateway to the internet.
So fundamentally, there is no issue with communication across subnets. However, Chromecast is one of those things that wasnt really designed with working across subnets in mind. Doesn't make it impossible though. Just comes down to do you want to do the work to make that work.
I recommend you read this guide from Cisco which should help: https://www.cisco.com/c/en
I recommend you read this guide from Cisco which should help: https://www.cisco.com/c/en
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Short answer to your question would be yes. The key thing was that traffic between the VLANs is allowed.