Apologies for the "noise". I solved it. The Firewall settings in the VM had the default 3389 Inbound Rule enabled. As soon as I disabled it, bingo. Locked out on 3389.
/Gordon From: [email protected] [mailto:[email protected]] On Behalf Of Gordon Pegue Sent: Thursday, February 11, 2016 12:06 PM To: [email protected] Subject: [NTSysADM] Hyper-V 2008 R2 VM Listener Port I've changed the Listener Port on a Hyper-V virtual server (W2K8 R2) to a custom value supported in our enterprise. What is dang curious is that the Hyper-V Manager > VM > Connect happily connects to the VM and opens a remote desktop session. Also, my pinned Remote Desktop Connection also happily connects to the VM. I assume that the Hyper-V Manager Connect tool is using the default 3389. I KNOW that my pinned RDP file is using 3389... The VM lives on the host server where I'm doing my testing but I get the same result when I test from a different physical box.... What am I missing to make my custom Listener Port number properly block RDP access to the VM if the 3389 default is used in the RDP client? /Gordon
