I am running Pooled VDI for Windows 7 Enterprise on a collection of Windows 2012 servers.
Two virtualization hosts, on two different networks, connect via VPN. I will call them HostA and HostB.
HostA is running Windows 2012 Core. On it are two VMs. One is serving the client's line-of-business app. The other VM is designated as the VDI broker. This computer also hosts about 30 VDI sessions.
HostB is located on another network about 200 miles away. It receives a replication of the first VM of the HostA (that's working great) and has 10 VDI sessions assigned to it.
When a user logs in that has his session (assigned) on HostA, the session starts fine.
When a user logs in that has his session on HostB, all of the startup processes seem to work, as the broker starts the VM (if it was off or saved) and then attempts to connect, only to be met with "loading the virtual machine" and a failed connection after about 5 minutes of waiting.
I thought it might be a firewall issue on HostB, so I configured the firewall to be off in domain mode for testing. No change.
The clients connecting to HostB's VDI sessions are on HostB's local LAN. If I switch their VDI assignment to HostA, it works fine.
NetworkA and NetworkB are connected together over a site-to-site VPN. They have different subnets (x.x.1.x and x.x.2.x) but I can contact any host on NetworkA from NetworkB and vice-versa consistently, so it is not a routing or firewall permissions issue, that I can tell.
Has anyone seen this? Is there something else that I need to do to get HostB to be able to accept connections or maybe accept the handoff?
I didn't see anything amazingly relevant in the logs, but I might not be looking in the right place.
Help?