@IT_Drone 

1. no change in the Windows "public/private" setting for the network
2. no change in the addressing scheme, the size of the subnet
3. all devices being on the same, main, network
4. all devices connected to the Deco, not to a switch or a modem or another router

  @yves_b 

yves_b wrote

  @IT_Drone 

 

1. no change in the Windows "public/private" setting for the network
2. no change in the addressing scheme, the size of the subnet
3. all devices being on the same, main, network
4. all devices connected to the Deco, not to a switch or a modem or another router

1. There were no changes in the Windows "public/private" settings for the network - all clients reside on the "private" network, and I don't have any Guest network enabled on my new Deco network.

2. As far as I know, nothing has changed regarding the addressing scheme or size of the subnet - IPs are still all dynamically assigned to clients that join the LAN by the Deco BE63 router; no static routes (same as when I had the Netgear router). The only thing I'm aware of that HAS changed is the IP of the default gateway - the old Netgear router was 192.168.1.1, while the new Deco BE63 uses 192.168.68.1 as its default gateway.

3. Yes, all clients are on the same "main" network. I have not enabled the a separate "IoT" network on my Deco BE63, so all clients connect to the "main" network. Not sure if this matters, but I have the 2-pack Deco BE63, and the "main" unit is on the 1st floor of my home, and the 2nd BE63 unit is on the 2nd floor of my home. So some wireless clients will join the net via the 1st floor unit, while others join via the 2nd floor unit.

4. Correct, all devices connect to the Deco, there are no other additional switches, modems or routers in my network.

  @IT_Drone No change in subnet mask?

yves_b wrote

  @IT_Drone No change in subnet mask?

  @yves_b 

Looks like there was a change to the subnet mask... Running ipconfig on all of my windows clients says the current subnet mask is set at 255.255.252.0, and my records from the old Netgear router setup indicated it was 255.255.255.0. FWIW, the Deco app didn't ask me to specify a subnet mask when I installed & setup my Deco's.

  @IT_Drone 

You can specify the LAN subnet mask of the Deco via the app: More, Advanced, LAN IP.  You will perhaps have to change as well the DHCP range if you change the mask.

I do not expect that the different subnet mask is the source of your issue, but it is a difference.  The default mask of some Deco allows more than 255 IP addresses.  That makes sense when you start having 100+ devices.

yves_b wrote

  @IT_Drone 

You can specify the LAN subnet mask of the Deco via the app: More, Advanced, LAN IP.  You will perhaps have to change as well the DHCP range if you change the mask.

 

I do not expect that the different subnet mask is the source of your issue, but it is a difference.  The default mask of some Deco allows more than 255 IP addresses.  That makes sense when you start having 100+ devices.

  @yves_b 

Thanks, but it appears I managed to solve my problem - apparently needed to do some Windows 10/11 kung fu on each of my clients to restore the "cast to device" functionality, which is now working. Here's the solution that worked for me, in case anyone else runs into this...

For each Windows 10/11 client, do the following:

1. Go into Settings => Bluetooth and Devices, and find the devices you are unable to stream/cast to. Go ahead and select the "Remove Device" for those device(s)

2. Reboot Windows.

3. When Windows is back up, go to Settings => Bluetooth and Devices, and hit "Add Device". For the Windows 11 clients, the options are Bluetooth, Wireless Displays or Docks, and Everything Else - select the appropriate category for your device, and Windows will search for it on the network - make sure the device is powered on & connected to the net first. Then select the device. Reboot Windows. The menus are a little different in Wndows 10, but the sequence is the same, so follow the same basic procedure for those

4. When WIndows boots up, the "cast to device" functionality should be fully restored.