My research to this point revealed that configuring for NLA does not work for RDP connections in the 'HTML5 VPN Portal', however, I see the same error in the 'HTML5 VPN Portal' log when I attempt to use TLS instead of NLA:
2015:01:08-11:43:31 cable screenmgr[2816]: Client 4: authenticated: user='skowa'
2015:01:08-11:43:31 cable screenmgr[2816]: Client 4: start screen requested: REF_CliConFirst
2015:01:08-11:43:31 cable screenmgr[2816]: Client 4: 400: Bad Request: argument format error
2015:01:08-11:43:33 cable screenmgr[2816]: Client 4: disconnected: Broken pipe
TLS works fine when "Automatic login" is disabled:
2015:01:08-12:02:17 cable screenmgr[2816]: Client 6: authenticated: user='skowa'
2015:01:08-12:02:17 cable screenmgr[2816]: Client 6: start screen requested: REF_CliConFirst
2015:01:08-12:02:19 cable screenmgr[2816]: Client 6: connector started
2015:01:08-12:02:19 cable screenmgr[2816]: id="2201" username="skowa" event="Connection started" sub="vpn" variant="clv" sys="SecureNet" severity="info" srcip="97.72.234.4" service="HTML5 VPN" type="VNCRDesktop" sessionid="6" sessionname="Obscenity"
Maybe RDP with NLA not working is a symptom of a problem with the automatic login?
Forgive me if this is already a known issue, it didn't turn up in my searches.
Thanks much,
This thread was automatically locked due to age.