Remote Desktop Connection - Windows Network Level Authentication

Hi
I'm trying to find a piece of Remote Desktop "Manager" software for Mac which supports Network Level Authentication (NLA). When NLA is enabled on a Windows Server I am unable to connect via CoRD or Royal TSX.
The reason I say "Manager" is because I have many, many windows servers I need to connect to and so I like to use software such as the above to save a list of all the servers for ease of access - this saves me having to type in the name of the server each time.
At the moment, for those servers with NLA enabled, I have to fire up Remote Desktop Connection for Mac and enter the name. I realise I could save this each time but then I would have LOADS of shortcuts.
Any ideas/proposals on pieces of software that can cater for this?
Thanks!

Hi!
Royal TSX actually supports NLA but you have to use the FreeRDP plugin instead of CoRD and enable the setting in the advanced settings of your RDP connection.
cheers,
felix

Similar Messages

AD "Log on to" restriction causes RDP connections with network level authentication to fail

I am running a Server 2008 R2 environment and have recently enabled network level authentication for RDP connections. Since the change, users who have their logons restricted to specific servers via AD, now get an error when logging on via RDP:
An Authentication error has occured
The Local security authority cannot be contacted
After investigating this error and reading technet I found that removing the "log on to" restriction within their user object solved the problem even tho they had rights to this server. Adding the users client PC name to the "Log on
to" list also solves this issue.
My question is, is there another way around this? We have an environment where some users may require an RDP connection from a client PC not on the same domain (over VPN) as the server. It will not be practical to add many different client PC names
to the log on to list and I don't understand why client PC's must be specified in the Log on to list and not just the actual server they are logging onto.
Any pointers appreciated

I have just come across this problem on one of my client’s domains; they have recently enforced a policy to “Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure)” and users with “Log on To” restrictions
on their account are no longer able to RDP using their second account.
After a lot of fiddling around I finally resolved the problem by adding the connecting computer name into “Log on To” list. Ultimately it appears that Network Level Authentication (NLA) requires authentication to take place on both the host initiating
the connection and the remote host.

Can I use Remote Desktop Connection (windows server 2008) even if no user is logged in?

I'm configuring a Server, running Windows Server 2008, to be accessed remotely. Suppose no user is logged in in the server (if it was just turned
on, for instance). Can I use the "Remote Desktop Connection" feature to log in remotely in this case? Or is it always necessary to have a user locally logged in, to remotely log in to one of the users available?

If its a fresh installation, RDM might not work at first.
1. You need to check firewall and allow Remote Desktop. To be specific, communication to port 3389 TCP
2. Right click My Computer --> Properties --> Remote tab
Enable Remote Desktop
Allow connections to this computer
Click users and grant the permissions for the users. By default, Administrators do have the permission. An also, the users who are members of the 'Remote Desktop Users' security group also have the permission

Remote Desktop Connection - cannot proceed because authentication is not enabled

Hello,
I try to connect via RDP from a Windows Server 2008 R2 to another 2008 R2 Server.
I always get the error message.
The connection cannot proceed because authentication is not enabled and the remote computer requires than authentication be enabled to connect.
On the target machine the Remote Settings are set to:
Allow connections from computers running any version of Remote Desktop.
Firewall is disabled on both servers.
Therefor I do not understand why I get an error message, that authentication is required.
The target box is a nearly fresh syspreped machine with all current Hotfixes installed.
I already found a lot of people having that problem by using XP (old RDP client), but no one seems to have this problem when connecting from 2008 R2 to 2008 R2.
Thank you very much in advance for every hint.
BR
Matthias

Hi Matthias,
First I would like to confirm if you have deployed RDS (Remote Desktop Services) and you got the error, if so, please check this option
TS Configuration, >> RDP-Tcp Properties >> change the Security Layer to "Negotiate"
Then Recycle the TS Gateway service.
Refer to:
Unable to connect to Server using the Remote Web Workplace (RWW) Small Business Server 2008
If this issue has nothing to do with RDS, and I suppose you used the cmd "mstsc" to remote access. This issue may also occur because of the version of mstsc, please make sure it has been upgraded to the new version.
In addition, Did you have another newer server available like Server 2012? So we can test and try to use Server 2012 to remote access Server 2008 R2, and check if the issue persists.
If there is anything else regarding this issue, please feel free to post back.
If you have any feedback on our support, please click here.
Best Regards,
Anna Wang
TechNet Community Support

Since upgrade to Windows 8, cannot save .rdp files under the Remote Desktop Connection application on the Desktop

Since I upgraded to Windows 8, I am no longer able to save individual Remote Desktop Connection files as .rdp files. I am talking about the traditional Remote Desktop Connection application on the Desktop that was in previous Windows versions, not the
Remote Desktop App from the Windows 8 store.
When I try to click on the Save button I get "An error occurred while saving to file"
When I try to click on the Save As button I get "Unable to open connection file" with the file address being where I tried to save it with the file name at the end.
Also when I upgraded to Windows 8, my .rdp files disappeared from my Documents folder.
I need to create different .rdp files for different programs that my employees get into on my server. Now I have to hand type all the info each time into the Programs tap on the Remote Desktop Connection window, because I can't save to an
.rdp file.
I like the Remote Desktop App from the Windows store but it won't let me designate specific programs to use using standard dos notation (ie c:\program files\ etc..). It just goes to my server desktop.
I want to promote Windows 8 to my employees but I need either .rdp files for the traditional Remote Desktop Connection or the ability to open specific programs using dos notation in the Windows Store Remote Desktop App.

I know this is an old post but others might still be having the problem. Here's what I did.
Create a new text file and open it in notepad. Copy the below into it and edit for your environment. (IP, screen size).
screen mode id:i:2
desktopwidth:i:1920
desktopheight:i:1080
session bpp:i:24
auto connect:i:0
full address:s:192.168.x.x
compression:i:0
keyboardhook:i:2
audiomode:i:2
redirectdrives:i:1
redirectprinters:i:1
redirectcomports:i:1
redirectsmartcards:i:1
displayconnectionbar:i:1
username:s:USERNAME
domain:s:DOMAIN
alternate shell:s:
shell working directory:s:
disable wallpaper:i:1
disable full window drag:i:1
disable menu anims:i:1
disable themes:i:1
bitmapcachepersistenable:i:1
use multimon:i:0
winposstr:s:0,3,0,0,800,600
audiocapturemode:i:1
videoplaybackmode:i:1
connection type:i:7
networkautodetect:i:1
bandwidthautodetect:i:1
enableworkspacereconnect:i:0
allow font smoothing:i:0
allow desktop com:0
disable cursor setting:i:0
redirectclipboard:i:1
redirectposdevices:i:0
drivestoredirect:s:*
autoreconnection enabled:i:1
authentication level:i:2
prompt for credentials:i:0
negotiate security layer:i:1
remoteapplicationmode:i:0
gatewayhostname:s:
gatewayusagemethod:i:4
gatewaycredentialssource:i:4
gatewayprofileusagemethod:i:0
promptcredentialonce:i:0
gatewaybrokeringtype:i:0
use redirection server name:i:0
rdgiskdcproxy:i:0
kdcproxyname:s:
You don't need to worry too much about what's in here. Save the text file as
filename.rdp then rightclick on the file and select edit. The familiar GUI rdp session editor will open. You can make changes in the GUI and
save or save as a different session.
Hope this helps.

Remote Desktop Network Level Authentication

Recently, I began getting failed connections from a Windows 7 Enterprise client to another Windows 7 Enterprise host where the host is requiring NLA. This has been a problem on and off for YEARS and I have found no link that can tell me to configure something
that I haven't already configured. Neither system underwent any configurations changes that I know of with the exception of Windows security updates/patches. In fact, some people in my company have the same issue while other do not. I can find no rhyme or
reason to it. Heres where I'm at:
"The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support."
But I do. when i click the upper left hand corner of my RDP client window and select "About", I see this:
"Remote Desktop Connection
Shell Version 6.1.7601
Control Version 6.1.7601
Network Level Authentication Supported.
Remote Desktop Protocol 7.1 supported."
And the above info is exactly what it says on the host.
Here's the SecurityProvider registry settings on the client:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders]
"SecurityProviders"="credssp.dll"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SaslProfiles]
"GSSAPI"="Kerberos"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL]
"EventLogging"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\CipherSuites]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Hashes]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\KeyExchangeAlgorithms]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Client]
"DisabledByDefault"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\WDigest]
"Debuglevel"=dword:00000000
"Negotiate"=dword:00000000
"UTF8HTTP"=dword:00000001
"UTF8SASL"=dword:00000001
"DigestEncryptionAlgorithms"="3des,rc4"
Every link I have looked at tells me to look at those things. Anyone got something new? :)
Also if someone knows how to log the RDP failures that would be cool too. Presently I have turned on Audit Other Security Events in GPO but it doesn't tell me if someone attempted to authenticate with a less then desirable security protocol.
As a fix, for now, I have reduced the security requirements on the host to not require NLA. <-- This is the only consistent fix I have ever seen that works.
By the way, just about every link I see also starts talking about setting up RD session host service. I am not running Windows Server 2008. This a Windows 7 to Windows 7 problem

Hi,
On both Windows 7, Please go to System Properties,
Remote tab and make sure that Allow connections only from computers running Remote Desktop with Network Level Authentication
is unchecked.
If problem persists, please check if there was any Windows updates need to install, if so, try to install updates for test.
Roger Lu
TechNet Community Support

Configure Network Level Authentication for Remote Desktop client

We publish Remote Desktop in our Windows 2008 R2 terminal server.
However, in Windows 2008R2 , the remote desktop client will a lillte bit slow
I found out that if I modify the setting in default.rdp
authentication level:i:0
enablecredsspsupport:i:0
it will increase the speed a lot
however, how can I set all user use remote desktop will disable those feature as well?
Thanks

Hi Kenneth,
I suggest you to see similar thread "disable
Network Level Authentication Terminal Server 2008"
If above thread does not helps, seek help from RDS/TS experts in here.
Or wait until any of our moderator move this post to respective forum.
Thank you for understanding.
Regards, Ravikumar P

Remote Desktop Connection With Custom Certificate on Windows 8.1 fails

I'm trying to establish a secured remote desktop connection without success.
The setting
There are some local pcs with windows 8.1 Pro and windows 7 Pro, no server-edition. I've created a self signed ca-certificate with openssl for Windows. I used this to sign custom certs for the local windows-pcs, which are installed at mmc -> certificate
snap-in for local computer -> My Certificates -> Certificates. The networkdriver has the right to read the key. The sha1-fingerprint of the custom signed certs are registered at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
-> SSLCertificateSHA1Hash = sha-1 hash of the custom local cert. Additionally the revocation-list is restrained to the local list by setting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Credssp -> UseCachedCRLOnlyAndIgnoreRevocationUnknownErrors
= 1.
The results
The connection form win 8.1 to win 7 works. The connection info confirms that it is a veryfied connection. The connection to windows 8.1 fails after entering the credentials with error: No connection possible. Network Level Authentication is set, but other
level don't work as well. The log (Event Views -> Applications and Services Logs -> Microsoft -> Windows -> TerminalServices-RemoteConnectionManager -> Admin) says "Remote Desktop Services has taken too long to load the user configuration
from server" and "The Local Security Authority Cannot Be Contacted" (error 0x80090304)
Aditional information
The connection via linux (remmina) works for win 7 and win 8.1, but I have no information about the encryption. It is the same with the Microsoft Remote Desktop Tool for Android.
Maybe it is accociatet with a different cert handling by Windows 8.1 but I couldn't find further information or a solution in the internet.
Best regards
abditus

I solved the problem!
The default openssl certificate signature algorithm is md5RSA but it doesn't work with windows 8.1.
It is at least sha1RSA needed.
By adding "default_md = sha1" to the openssl.cnf you create certs with sha1RSA and it works fine.
Beste Gegards
abditus

Remote desktop connection in windows 7 pro

I have a problem accessing remote desktop connection using windows 7 64 bit.
My remote desktop connection shell version 6.3.9600 shows the Network Level Authentication is not supported.
My other computer also win 7 pro 64 bit has a different shell version 6.2.9200 that supports Network Level Authentication.
How do I go backwards to shell 6.2.9200?
I have been trying use remote desktop using the more robust security and could not figure out why I could not log.
I have screen shots of the two shells and my system screens

Hi,
Configure Network Level Authentication
Click Start, click Run, type regedit, and then press ENTER.
In the navigation pane, locate and then click the following registrysubkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
In the details pane, right-click Security Packages, and then click Modify.
In the Value data box, type tspkg. Leave any data that is specific to other SSPs, and then click OK.
In the navigation pane, locate and then click the following registrysubkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders
In the details pane, right-click SecurityProviders, and then click Modify.
In the Value data box, type credssp.dll. Leave any data that is specific to other SSPs, and then click OK.
Exit Registry Editor.
Restart the computer.
Hope this helps!
Andy Altmann
TechNet Community Support

Remote Desktop Connection between Windows Mobile 6.5 and server 2012

Hi all,
We have problem with remote desktop connection. The server that I want to connect is 2012 R2.
We have no trouble with server 2008. I searched from internet, there are solutions on server side(I am not sure if these suggestions solve the problem), but our customers don’t want to solve this problem
on server side because it is diffucult and risky.
Is there a solution on handheld terminal side to do?
Operating system: WM 6.5 classic(Professional o.s. has no effect, same error continues)
Any help will be appreciated from your side.
With Best Regards.

Hi,
What is the precise error message you are seeing? What are the exact symptoms?
I don't remember what version of RDP/featureset is supported by Windows Mobile 6.5. Perhaps the client does not support Network Level Authentication, which is required by default on Server 2012 R2. You can enable non-NLA connections by
unchecking Allow connections only from computers with Network Level Authentication in Server Manager -- RDS -- Collections -- Properties of collection -- Security tab.
Lack of NLA may not be the cause of the issue you are experiencing, however, if it is the only way to solve it would be to change the server setting or to potentially install a new client on the device that supports NLA.
-TP

Remote Desktop Connection to Windows 8 PC from other computers crashing

Hi all.
Was hoping someone would be able to help me with an issue I'm having.
I'm trying to get a LAN remote desktop connection established to my Windows 8 laptop. It's an HP ENVY 17t-2100 CTO 3D Edition Notebook PC. Note that I'm running Windows 8 Pro only - not 8.1 as HP haven't released 8.1 graphics drivers for this laptop and probably
never will. The computer has a single user profile that has full administrator rights.
I have followed numerous web tutorials on how to turn on Remote Desktop. I've gone into Advanced System Settings > System Properties > Remote > checked "Allow Remote connections to this computer". All seems ok to me.
The problem comes when I try to establish a connection. When the connection is made, it almost instantaneously crashes the session on the computer or device trying to connect. The RDP client on my Windows 7 laptop, Mac OSX or Mac running Windows 8.1 Pro just
crashes, while the RDP iPhone or iPad app simply flickers for a few seconds then goes back to the main screen. Meanwhile, the HP ENVY loads the lock screen and displays a message saying XXX device is connected remotely and it won't let me log back in to kill
the connection or do anything. I have to restart the computer from then to be able to use it again.
I'm convinced there's not a problem with my local network as the HP ENVY can RDP into the Windows 7 laptop or Mac running Windows 8.1 without any problems. All computers are connected via Ethernet to a Linksys/Cisco wireless ADSL modem router which supports
Gigabit. The iPhone and iPad of course connect to the wifi network from the Cisco/Linksys modem router
I've also had a brief look at the RDP local connection logs. From what I can make out, they confirm that a user has successfully logged in, but they don't provide a crash log or a log of the user ever disconnecting, probably because I have to restart the computer
to continue using it. Dead end there, it seems.
The HP ENVY is connected to 3 external HP LED monitors. I've disconnected them and tried all devices with no luck. I've also played round with the RDP client settings to not mount drives or printers and the HP ENVY has no printers connected anyway, though I've
done all I can to remove any printer drivers as I've read elsewhere that they are what could cause the problem, but I've had no luck.
If anyone can suggest anything more that I can try, I would be unbelievably grateful! I'm more than happy to provide screenshots or videos of what happens when I try connecting. I'm not sure what you experts would find immediately helpful so just ask away if
you think I can provide anything.
Thanks in advance!
rugbyreff

The first thing that I would try is to uncheck all of the boxes for local resources on computer running the RDP client. It is possible that a device, such as a printer or other redirected device, is causing the crash. You can also look under Event Viewer
in the event logs of both systems and see if anything unusual appears when you attempt the remote connection.
Brandon
Windows Outreach Team- IT Pro
The Springboard Series on TechNet
Hi Brandon
Many thanks for your suggestions. There's nothing in the logs that I could find, like I said in the original post. I've also tried connecting with bare minimum settings on all devices (FYI the iPad and iPhone version don't support the use of printers) and
this still hasn't helped.
If you have any other ideas I'd be very glad to hear them!
rrugbyreff
"If it's worth doing, it's worth overdoing" -- MythBusters

Can 1 instance of Windows 8.1 ENTERPRISE host multiple Remote Desktop connections?

I am shopping for the components for building a machine with fair, high-performance hardware. I have Windows 8.1 Professional. I wanted to know if either Windows 8.1 Professional or Windows 8.1 Enterprise can support multiple remote connections
from users outside the local network. For example, my brother is based in San Diego, CA and has an underpowered laptop. Is there any way to make a remote connection over that much distance, from San Diego to Northern Virginia, from a RDP client running Windows
8.1 Professional to a RDP "server" Windows 8.1 Professional/Enterprise machine, and run a modern, single- or multiplayer- game over smoothly that connection? At the very least, is it possible to run common
apps (e.g. Microsoft Office 2013 IE 11, Adobe Acrobat XI) smoothly on a Windows 8.1 Pro RDP client connected to a Windows 8.1 RDP "server" located 2250+ miles away?
Would upgrading my installation from Professional to Enterprise improve the responsiveness and display quality for my remote users?
I know Windows Server R2 2012 has features specific for handling remote connections, but I am trying to keep a Windows 8.1 user experience. Still, if anyone can show some evidence that Windows Server 2012 R2 Remote Desktop Services (RDS) improves display
and responsiveness over long-distances for remote (RDS) connections, then I will shop for Windows Server 2012 R2 Standard instead. The huge drawback of Windows Server 2012 R2 Standard CALs is the enormous cost to enable 3-5
remote connections for family, non-commercial use.
Has anyone attempted to host long-distance remote access, non-commercially, for 3-5 connections? Has it worked well? What, in general, is required?
T. Webster

Hi,
It depends on the quality of the network connection to run the software smoothly throuth RDP. And I don't think the quality would be better if you upgrade to Windows 8.1 Enterprise.
Windows 8.1 allow only one session of RDP, the Remote Desktop Server in Windows other than the Windows Server edition has a limitation to allow only one concurrent user per session by default, i.e. if someone remotely connects to the computer over RDP then
whoever was logged in at that moment will be automatically logged off, even if that user is physically present at the computer. This is by design.
Regarding more information about RDP, please take a look at the following articles:
Remote Desktop app help
Remote Desktop Connection: frequently asked questions
Best regards
Michael Shao
TechNet Community Support

Remote Desktop Connection - Authentication error

Hello,
I wish to connect to my work PC from my laptop. The remote desktop connection was working fine till yesterday, but today i receive the following error when i try to connect -
"An authentication error has occurred. The Local Security Authority cannot be contacted. Remote Computer: <name>."
I have Win 7 ultimate installed on my 32 bit system, and have tried solutions proposed in the other threads. I do not require a NLA check for connection, i have always used the remote desktop with this option unchecked. Could anyone help me with this please?
Is this a error on my Laptop, or do i need to contact the network administrators for this?

Hi!
It could be as easy as you need to change your password on your domain accout.
Are both computers connected to the same domian or is your work computer connected to a domain and your laptop connected to a workgroup?
If your password has expired, this error can occur, so I would start to check that since it stoped working over night.
Best regards
Andreas Molin

Remote Desktop Connection won't work from Leopard to Windows XP

Hi, folks:
I'm unable to connect to my work XP computer via my home iMac (Leopard 10.5.7) using Microsoft's Remote Desktop Connection for Mac. The XP settings are correct, I'm connected on my work network VPN, and I don't believe I have any router firewalls causing the problem --- the reason I know this is because I also have an MacBook running Tiger (10.4.11) and it has been connecting to my work PC without any problems. So, this must be a Leopard firewall setting?
As far as that goes, on my iMac I've got Screen Sharing, Remote Login and Internet Sharing turned on. Again, work network VPN is on.
I'm getting this error from Remote Desktop Connection:
"The Mac cannot connect to the Windows-based computer
This problem can occur if:
- The Windows-based computer is not set up to accept remote connections
- The Windows-based computer is not turned on
- The Mac, or the Windows-based computer is experiencing network problems
Try connecting to the Windows-based computer again, or contact your administrator"
Anyone know of a fix? I'd greatly appreciate it!
Thanks.

What Firewall setting do you have on your Mac? Try setting it to allow all connections. At least as an experiment.
Do you have any Proxies set in System Preferences -> Network -> Advanced -> Proxies? If yes, then is it possible that "Bypass" list is not covering the XP system.

Remote desktop connection from windows computer to TC

hi all,
what I have: I have a TC 2TB, bought it three months ago.
what I did: I have set it up at home. Using as base station for all my devices, iphone 4, ipad 2, macbook air and also other laptop. My TC is connected to ADSL modem with an ethernet cable (as expected). with port forwarding option of ADSL modem (in NAT Properties), I managed to forward any connection to TC. I have a static IP by the way.
what I can do: from work or anywhere else other than my home network, I can connect to my static IP (via "Connect to Server" option in any mac device), it pops up a user name and password window, I login with my TC user name and decive password. In an instant my TC disk is mounted on my desktop, and I can reach all my files in it as if it is an external hard disk.
what I cannot do: from a windows computer outside my network, I cannot connect to TC. I try to do this through "Remote Desktop Connection". Is this possible? If so how? Is this a problem related to network connection or TC settings?
aakibar

You cannot remote desktop into a TC..
In fact you cannot remote access a TC from windows.. sorry.. but SMB protocol is blocked on the internet.. there are work arounds but no security.. don't do it.
The only other protocol the TC offers is AFP.. there is no AFP file access software available for windows. You need to use a Mac.
The best alternative is vpn.. replace your current adsl modem router with a vpn one.. eg draytek.. then you can access your home network. Since I presume when you say you have static ip you mean public IP then vpn is easy (well once setup it is).. reliable and secure.

Remote Desktop Connection - Windows Network Level Authentication

Similar Messages

Maybe you are looking for