You state "Client B cannot access Client B's hosted PBX via the Fiber vendor's Internet connection", so I assume they can use that for general internet browsing?
If so, as Client B has a hosted PBX I assume they are using IP Handsets. Setup the IP handsets on a separate VLAN and the DHCP for that VLAN can set the Default gateway as the Internet connection for Client B (pretty sure the Ubiquiti Edge Router can do that). Client B PCs will still have the Client A connection as their default g/w so all their normal browsing will go via that.
If they actually mean Client B can't use Client A internet at all then:
You are possibly looking at 3 VLANs, one for each clients PCs, phones etc and one for the server. The 2 VLANs for each client have has the DHCP set the g/w to each respective internet connection. You might need a layer 3 switch to handle the 3 VLANs and the routing between them (I have used Cisco for similar and also a Draytek Vigor 286x will do it as I use them for something similar, but you might have to set some static routes).
One last option (came to mind, haven't thought through too much!), is it looks like you are using Windows 2016 Std with the Essential role. How about setting that up as a HyperV, if not already, and then 1 VM each for each company and use the VLAN for each VM to isolate the data. Setup a FreeNAS VM and put the shared data there for them to access. This would make it easier to separate them if required in the future (if one compnay sold off (going through this with a client at the moment).
Anyway 3 suggestions to think about...
Rob
answered 08/05/2020 14:11