Hi
I have tried finding other seeing this problem but to no avail.
Maybe the combination is not so common, it took us several weeks to put the puzzle together.
We have a genuine new built Windows 2012 R2 domain with a variety of normal servers, domain controllers, Fileservers, Printserver, Federation server and RDS servers working in a farm.
To make the farm work as planned we created a dns name like ts.domain.local and letting the broker find out which server has a slot avaialable, it works good except in a few cases.
Some users reported they are failing in connecting with error "This Connection will Close now due to Protocol error"
Not every time, but enoug times to get frustrated, It took me several weeks until I noticed these users all had special characters in their SAMaccountName (aka Pre Win 2000 Logon name).
Since we using Office365 with federation we needed to put User Principle Name rather long. firstname.lastname@publicdomain.se
In Sweden its semi-common to have names with Å Ä Ö and Windows 2012 R2 was know to support this, and I was happy to finally after many years been able to allow users to keep their correct spelling, it felt fair to do so.
but it does not work in TS farm (RDS farm)
Let me give some details in case someone like to dig deeper in this.
IF having login names (We used Pre win 2000 login name) aka SAMaccountName with non A-Z characters.
(We used 3 first from given name and 3 first from family name)
RDP by dns-name Pointing to a RDS farm is giving intermittent error refering to protocol error.
Same servers will accept if using IP-address and never show this protocol error.
Same second changing the logon name the error is gone.
(Playing with settings in RDP-file could indicate different effects, but not under good control)
Best regards Kjell Liljegren
In case someone like to ask me more, write me at hot mail dot com with firstname dot lastname