I've tried Your patch on Your custom terminals.config. It replaced enableCredSSPSupport with enableNLAAuthentication. But the new config file didn't work with either Your custom terminals nor with the stable 1.9a. When replaced the default terminals.config
with the patched one - terminals would complain that it couldn't migrate my connections and would launch the initial config window. After the initial configuration (master pasw etc.) the terminals.config file would loose any record regarding enableNLAAuthentication
and I couldn't connect to servers requiring NLA.
Meanwhile Your custom terminlas app has 8 records enableCredSSPSupport="false" in it's terminals.config. I've changed them to "true" and now I can connect to our Win 2008 server that would previously give me an error that the server requires NLA (also -
this message only appears on Your custom terminals, the standard 1.9a does not show a message at all - very inconvenient, I wouldn't even know NLA was the culprit of my failed attempts to connect if not for Your custom build). But I've tried to connect to
our clients server (also win 2008) but got the same message stating that NLA is required. So it seems just changing enableCredSSPSupport to "true" does not solve everything - at least in my case (obviously something is configured stricter at our client site
since I can connect to our server that I reckon has near default configuration - it's only a test system).
Maybe You have a config file that is patched and would fit the standard 1.9a version (with enableNLAAuthentication)?
When you say 'the stable 1.9a', do you mean the original version (May 11 2010) as per the downloads page. This doesn't support NLA but the one from http://terminals.codeplex.com/workitem/26306 does. (Should maybe point out that
that 26306 still needs admin rights)
If you were using the May 2010 version, it wouldn't understand the config file ( if it refers to either enableCredSSPSupport or enableNLAAuthentication) and would bring up the message about not being able to migrate your connections etc.
> Meanwhile Your custom terminlas app has 8 records enableCredSSPSupport="false" in it's terminals.config.
I erred on the side of caution and hence did not enable this setting by default. So you need to enable it on the Extended settings tab on the RDP tab of each connection that you need it. If you do a search and replace for enableCredSSPSupport="false" in
the terminals.config and change it to true, that will work, but only if the that line already exists. This might explain why some connections work and others don't. So you would be better using the UI to check/set the option.
> also - this message only appears on Your custom terminals, the standard 1.9a does not show a message at all - very inconvenient
Yeap, that was another change I made. That fix will be in the next offical release (but it is not in the 26306 version)
> Maybe You have a config file that is patched and would fit the standard 1.9a version (with enableNLAAuthentication)?
The config file is a list of your connections, which obviously I don't have. All I can say is that the only change I made to the file format was to add the enableCredSSPSupport setting. If you want to go back to the original 1.9a
you can remove all occurances of enableCredSSPSupport="false" or enableCredSSPSupport="true" and the config file will open correctly. (This would also open using the workitem/26306 version, but obviously all connections would be set to not enable
CredSSP/NLA). All my patch did was replace enableCredSSPSupport with enableNLAAuthentication so that the config could be opened with workitem/26306 version (and future versions of terminals) without having to go through all your connections
and re-enable this setting.