Anyway. My setup is, two 2008 R2 machines, Remote Desktop Services role installed on both, Session Broker installed on one, both servers in the local “Session Broker Computers” group on the session broker. Licensing is installed, enabled, and assumed not to be a problem.
These machines are two physical HP Proliants, each with dual NIC’s. The NICs for the session broker are teamed to form one virtual interface, whose TCP/IP configuration is assumed to be correct. The second machine, the farm Member server, originally had the NICs teamed as well, and everything worked (From windows & mac clients, of course. Not from rdesktop).
In an effort to attempt accommodating the rdesktop users, the NIC team on the member server was broken, each interface was given its own IP, and the IP address for the second NIC was excluded from the IP set in the “RD Session Broker” tab of the Member Server Properties. This is where stuff gets funky.
We suddenly noticed that sessions attempting to redirect to the member server would fail, with the error message:
[This computer can’t connect to the remote computer.]
The remote computer broker.domain.edu that you are trying to connect to is redirecting you to the remote computer member.domain.edu. Remote Desktop Connection cannot verify that the two remote computers belong to the same farm. This can occur if there is another computer on your network with the same name as the computer you are trying to connect to.
(And of course the ubiquitous irony of) Contact your network administrator for assistance.
When I re-teamed the NICs, this issue appeared to go away for everybody except my co-worker, who, when attempting to auth into the farm using his su account (Member of local admins on both boxes), continued to receive the error.
However, a new, different problem also presented itself: When initially attempting authentication as domain\user, we receive a “Incorrect username or password”. The server then prompted for Fully.qualified.ad\user, upon which authentication worked.
This caused me to suspect NetBIOS, but everything seems to be just fine there; I can resolve single-name DFS entries, other windows hosts on the network, etc.
SO… any ideas? If I’ve forgotten some detail, let me know and I’ll provide it. This is highly annoying.