How to configure ORBI in router mode for vnc connections

The Orbi will not block internal communication between devices on the LAN.  (If the devices are physically wired to the router, those data packets never leave the Ethernet module on the router, so the "router" itself never sees them at all.)  WiFi connections would pass through the router, but still will not be blocked.

I, also, use TightVNC to view headless Raspberry Pi's on my LAN.

I suspect that the change from the 192.168.1 IP subnet to 10.0.0 is the problem. Perhaps

• The VNC server is locked in somehow to 192.168.1 and is rejecting connections from 10.0.0, or
• The VNC Client setup is still pointing at the 192.168.1 subnet. (I often use "names" to label VNC connections and thus am not paying a lot of attention to the underlying IP address.
• The Windows Firewall on the VNC server side is not set up to allow connections from 10.0.0

A VNC connection from outside the 10.0.0 LAN would require Port Forwarding to get through the router, but since the point is to isolate VNC traffic from the rest of the network, that does not seem to be an issue here.

If you are comfortable with Wireshark, it might be useful to monitor the progress of a VNC connection (from either end.)  The default port for TigerVNC is 5900. That would show the connection request going out and then......