Yes, all the clients access everything via a single name "RDS". In DNS, there are (3) A records for "RDS" , pointing to 10.1.3.7, 10.1.3.8, and 10.1.3.9, so it seems to be just sort of a round-robin approach to which server the client connects to. I didn't know a broker can redirect clients to specific servers if they were disconnected from that one.
I haven't dealt with MS NLB is forever. is that setup under the network card properties itself? That's where I'd be able to see if NLB is installed? Or is that a server-role? Jesse Rink Source One Technology, Inc. HP Partner 262 993 2231 ________________________________ From: [email protected] <[email protected]> on behalf of Charles F Sullivan <[email protected]> Sent: Thursday, October 1, 2015 11:08 AM To: [email protected] Subject: RE: [NTSysADM] Re: RDPing into the wrong IP address There needs to be way to balance the load. Isn’t there a common URL/DNS name that the clients point to? If so, the broker is needed to redirect clients to all 3 of your RDS servers. It also has some sort of affinity feature, so that if a client breaks the connection with one server, it will get the same server when it reconnects. If I remember correctly, network load balancing is optional, but is probably the most common way of setting up the broker, so you may have to investigate that. Look to see if NLB is enabled on the servers. Somewhere in the NLB configuration you should see the common name associated with it. I only have experience with this in a test lab and it’s been a while, so someone else may be able to better help you. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Jesse Rink Sent: Thursday, October 1, 2015 11:49 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] Re: RDPing into the wrong IP address I guess I'm not too familiar with RDS farms. I've managed a good number of terminal servers in my day, but haven't setup a RDS farm. Any quick info you can give me on how the farms operate, as opposed to not having them? What does the RDP connection broker actually do? Jesse Rink Source One Technology, Inc. HP Partner 262 993 2231 ________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Gabriel Moga <[email protected]<mailto:[email protected]>> Sent: Thursday, October 1, 2015 9:55 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: RDPing into the wrong IP address Most likely is the RDP connection broker. When I need to connect directly to one of my servers part of the RDS “farm” I use mstsc /admin. ;-) Regards, Gabriel Moga From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jesse Rink Sent: Thursday, October 01, 2015 8:46 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RDPing into the wrong IP address Having trouble understanding this one... I have a customer with (3) 2008 R2 servers all running RDS-terminal services. RDS1 - 10.1.3.7 RDS2 - 10.1.3.8 RDS3 - 10.1.3.9 Here's the weirdness. For example, * If I try to RDP into 10.1.3.7 (by IP address!! not by hostname), I actually get logged into 10.1.3.8 * If I try to RDP into 10.1.3.8 (by IP address!! not by hostname), I actually get logged into 10.1.3.9 * If I try to RDP into 10.1.3.9 (by IP address!! not by hostname), I actually get logged into 10.1.3.7 I am on the same local subnet as those servers, so I've ruled out something like the firewall or router having some weird redirect... Also pretty much ruled out some weird DNS issue because I'm attempting to access them via IP, not hostname. Another oddity is, when accessing \\CEO-RDS01\c$<file:///\\CEO-RDS01\c$> , I do get the proper server (so it's not redirected then.....), and same thing for the other two servers, accessing their UNC paths takes me to the correct servers. I thought perhaps some old/retired RD Gateway settings or something, but none of the 3 servers have RD Gateway services installed/running. Mainly it just seems to be when accessing the servers via IP address using RDP that I get connected to a server I shouldn't. The only way I can get onto the specific server is from the VMWare vSphere Client. Weird. Any ideas? JR
