I think it has something to do with the RD Connection Broker and server farm stuff.... I'm not an expect at RDS server farms, but there does seem to be a setting for IP redirection so I think that's where it's coming from. Just need to better understand how this works.
JR ________________________________ From: [email protected] <[email protected]> on behalf of Miller Bonnie L. <[email protected]> Sent: Thursday, October 1, 2015 8:01 AM To: [email protected] Subject: [NTSysADM] RE: RDPing into the wrong IP address Incorrectly configured NLB? Do you see anything on the advanced tab for a second IP address? How about if you run: Get-netipinterface | fl (2012+) Or Netsh int ipv4 show config -Bonnie From: [email protected] [mailto:[email protected]] On Behalf Of Jesse Rink Sent: Thursday, October 1, 2015 5:46 AM To: [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
