A. Every time I've seen this, it's because IP virtualization is enabled on a per-session level. This causes some tools to get confused about how they should talk to the network. IP virtualization at a per-session level means each session gets its own IP address, rather than using the IP address of the Remote Desktop Session Host. Disabling IP virtualization solved the problem in each case.