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

Similar Messages

Remote Desktop Connection cannot verify the identity of the computer that you want to connect to.

I had a Windows 2008 server which was upgraded to 2012. Now RDC doesn't work and I get the following message:
Remote Desktop Connection cannot verify the identity of the computer that you want to connect to.
RDC works on the server because I can reach it via other windows machines, just not my Mac any more. I suspect it is a certificate issue but I can't find it in my key chain.
Any suggestions?

Hi,
You might want to follow the below Thread which best suits the current scenario
https://social.technet.microsoft.com/Forums/itmanagement/en-US/2bc873ed-6c11-4767-8ce3-4df8549aff20/remote-desktop-connection-cannot-verify-the-identity-of-the-computer-that-you-want-to-connect-to?forum=winservergen
Hope this helps !
Regards,
Sowmya

Windows 7 remote desktop connection cannot logoff the local user

Windows 7 remote desktop connection cannot logoff the local user
Remote Desktop connection:
(This experience is from Windows 7 remote to Windows Embedded Standard 7 computer)
I used Remote Desktop to try to log on to a Windows 7 (WES7E) computer and someone is already logged on locally (Console Session), I saw a message like this:
"Another user is currently logged on to this computer. If you continue, this user has to disconnect from this computer. Do you want to continue?"
I click on Yes.
Then I saw "Please wait for [username] to respond". No action from the logged-on local user, I waited for 30 seconds, then I was able to login the computer and at the same time was able to disconnect the logged-on local user.
Question:
1. "Another user is currently logged on to this computer..." message doesn't show me the actual logged-on user name. Is there any way to show the user name in this pop-up message?
2. After waiting for 30 seconds, I was able to login the computer and the logged-on local user is disconnected, however this local user is never been logged-off. I wanted to logoff the local user (with Console Session) when I made the connection remotely
to the computer from remote desktop (Just like Windows XP) Is there any group policy can change the behavior?
The policies I have looked at are:
Local Computer Policy | Computer Config | Admin Templates | Windows Components | Remote Desktop Services|Connections|Deny
logoff of an administrator logged in to the console session => disabled
Regards,
Mei Davis

Hi ,
These behavior is by design. There is no way to change that. Thank you for your understanding.
Best Regards.
Tracy Cai
TechNet Community Support

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

Remote Desktop Connection ok on work wireless but not from home

I've succesfully logged into the Win 2003 SBS (Terminal Services) from within the wireless connection at work using Mircrosoft's "Remote Desktop Connection". However when I try to do this from home I get the following error message "Either remote connections are not enabled, the computer is too busy to accept new connections, or network problems are preventing your connection. Try connecting again later or contact your administrator."
I've got the firewall on the mac on.
Now what I can't work out is why it works when at work and not from home. I have been searching for ages and can't work this out - annoying as I am sure it is very simple!
One thing I can think of is that the first time others connect via PCs they have to download the connection manager from the company web site which installs a security certificate. However this is an .exe file so cannae work on the Mac.
Do all I need to do is ask the IT administrator to email me the certificate and drop it into the keychain?
Thanks in advance.

"Now what I can't work out is why it works when at work and not from home."
Probably because, if your work is smart, they have a firewall in place, blocking external access to the ports needed for use with RDC.

Keep getting "Iphone cannot sync because syncing is not enabled" ??

So when I plug my iPhone into my PowerBook G4 to sync them together, I keep getting an error message that says "Syncing is disabled on this computer, do I want enable syncing ." When I chose yes, I get another error screen that says "Syncing is not available on this computer" and I get two choice buttons, override and ok. When I hit override, nothing happens. If I hit ok, the iPhone shows up on iTunes and I can back up my info but none of my music, contacts, iCal, or notes get synced.
Is there a preference screen I'm missing here or might my iPhone be corrupt and I need to restore? This problem just started happening recently.

stagebuilder wrote:
A note about something I just found is that the iSync icon in my tool bar cannot be chosen for some reason. It's solid black, not light gray like it was offline, so I can't seem to change it.
This article: http://support.apple.com/kb/TS1627 provides a few more tips that can resolve the issues where iSync will not launch or respond.
-Jason

Remote Desktop Connection (RDC) iMac to PC server with fixed IP

I have setup my first imac and as part of this process downloaded Remote Desktop Connection for macs so that I can log onto my server at work. Problem is when I attempt to connect to my remote pc the following message appears "Remote Desktop Connection cannot verify the identity of the computer that you want to connect to. Try connecting to the Windows-based computer, or contact our administrator"

So, what if those don't help? I've had "Always connect, even if authentication fails" selected for quite a while. It was working fine. Yesterday I installed Office 2011 (and immediately installed SP1), and now it broke my ability to connect to a Windows Server 2008 VM that definitely worked yesterday before the Office upgrade.
Anybody have a solution for this? It appears to be a bug in RDC 2.10. Thanks, Microsoft. Off to find a working RDP client for the Mac…

Remote Desktop Connection not working

I am able to remote desktop connect to my home computer from work; however, I can't remote desktop connect to my work comptuer and server. I believed it has something to do with my Linksys E3000 access point settings but I'm not sure where to look for and verify. I took my home laptop to work and able to do remote desktop connect to the server. I also took a laptop that's working fine with remote desktop connect to the server home and tried to remote desktop connect to the server at work and it's not working. Therefore, I've concluded that it has something to do with the access point and not the settings in the computer because it works fine when I took it out of my home network. I also VPNP in to my work place so that it has the same IP address as at work and still, remote desktop connection from home to work is not working. Any suggestion is much appreciated.

thebluemamba_24 wrote:
Connecting from home to your remote desktop server has nothing to do with your router. Certain ports are needed to be opened from the server’s end in order to host an application. Try to connect your computer to your modem or to another wireless network just to check if your work’s remote desktop will work. In case it will not work, then contact your IT guy.
If you read my previous post it said:
"I took my home laptop to work and able to do remote desktop connect to the server. I also took a laptop that's working fine with remote desktop connect to the server home and tried to remote desktop connect to the server at work and it's not working. Therefore, I've concluded that it has something to do with the access point and not the settings in the computer because it works fine when I took it out of my home network."
I think my above statement answers your question of "Try to connect your computer to your modem or to another wireless network just to check if your work’s remote desktop will work." However, your statement prompts me think of something else. What I have tried is bring my laptop to work and tried connect via RDC to the server and it works but it just not working when trying at home. What I have not done is instead of brining my laptop to work and try RDC there, perhaps I should I try it on a friend's or relative's network and see if I can do RDC to my server at work. If this does not work as well, then, could it be that at work there is something something outside RDC coming? But even if this is so, why can't VPN work?

VPN and Remote Desktop Connection

I have a standalone windows 2012 server that runs a domain with a few workstations. I have successfully configured a PPTP VPN and can connect using a Windows 7 computer at home. Once connected to the VPN, I can Remote Desktop to the server - but not any
other computers. The computer I'm trying to connect to runs Windows 7 and has remote desktop connections enabled.
Under the Access Details in the Remote Access Management the VPN connection is shown correctly first to the router (x.x.x.1) then the server (x.x.x.2) under Protocol 17 and Port 53. Then the server is shown again under Protocol 17 and Port 3389, which must
be the Remote Desktop connection. And then the workstation on the domain (x.x.x.20) also shows a connection with Protocol 17 and Port 3389. However, the remote desktop connection fails everytime. I'm not sure where the issue exists since it appears the server
is seeing and acknowledging the remote desktop connection. On my router I have PPTP passthrough enabled and port forward 3389 to the server.
I have attempted to use the workstations internal IP address as well as the computer name (workstation and workstation.domain.local) when connecting.
Thanks for your help.
I just noticed these three event errors on the destination remote machine. Not sure why it's trying to use L2TP?
Failed to apply IP Security on port VPN2-1 because of error: A certificate could not be found. Connections that use the L2TP protocol over IPSec require the installation of a machine certificate, also known as a computer certificate.. No calls
will be accepted to this port.
A certificate could not be found. Connections that use the L2TP protocol over IPsec require the installation of a machine certificate, also known as a computer certificate. No L2TP calls will be accepted.
The Secure Socket Tunneling Protocol service either could not read the SHA256 certificate hash from the registry or the data is invalid. To be valid, the SHA256 certificate hash must be of type REG_BINARY and 32 bytes in length. SSTP might not be able to
retrieve the value from the registry due to some other system failure. The detailed error message is provided below. SSTP connections will not be accepted on this server. Correct the problem and try again.

Morning Trent,
I don't know if this is still an issue for you, did you get it solved?
If not, check on the server whether the user credentials that you're using to RDP to the workstation are actually authorised server-side. If that checks out, on the VPN connection you can specify a protocol to use. Specify the protocol that your VPN is configured
to use on the server.

After MS13-098 and SecurityAdvisory(2915720), Windows Server 2003 Remote Desktop(TermService) cannot start service

I have trouble with Windows Server 2003 R2 Standard. I installed the KB2893294(MS13-098) patch, and I changed the registry that is suggested actions of Security Advisory(2915720) http://technet.microsoft.com/en-us/security/advisory/2915720
Suggested Actions:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Wintrust\Config]
"EnableCertPaddingCheck"="1"
After rebooting the event viewer(system) says:
Event Type: Error
Event Source: TermService
Event Category: None
Event ID: 1014
User: N/A
Description:
Cannot load illegal module: C:\Windows\system32\rdpwsx.DLL
After I cannot use Remote Desktop Connection from other client.
So I check the all security patches and other hotfixies. I checked the KB2653956 and KB958476.
But TermService do not recover the error.
And then, I delete the "EnableCertPaddingCheck" registry and reboot systems.
TermService have no error. I can use Remote Desktop Connection from other client.
After KB2893294 installed, Remote Desktop Connection cannot use from other client that "EnableCertPaddingCheck" registry set to "1".
Other Windows Server 2008 systems do not effect the KB2893294 patch. But All Windows Server 2003 systems cannot use the Remote Desktop Connections after the KB2893294 patch.

Update on this issue:
The debug team has accepted the issue and has identified it as a regression. Right now they're targeting *June* as the release date for a fix. I'm attempting to educate them that customers don't just install patches the day (or even month) they're
released and that the fix needs to be moved up in priority to give a minimum of 60 days to install the patch before the time-bomb explodes.
In the meantime, a workaround has been provided that will turn off the new functionality. Note that I have not yet had a chance to test this. It entails creating a new DWORD registry entry--UseLegacyPE--and setting it to 1.
HKLM\Software\Microsoft\Windows NT\CurrentVersion\ImageHlp\UseLegacyPE
I will update this thread when I have further information.

Remote Desktop Connection Stopped Working when Disconnecting

Hi I have a fresh clean install of Windows 8.1. Whenever I RDP into another Windows 8 machine... upong disconnecting I get the error: "Remote Desktop Connection Stopped Working"
I have tried not mapping to remote printers, or drives (smart cards etc.) and it still persists. When I remote to Windows Server or Win 7, it does not happen.
Anyone have any ideas?
Thank you
mi

FYI, same issue here, Windows 8.1 on ThinkPad W520 (upgraded from Windows 8).
Even without Fingerprint Manager, and having uninstalled ThinkVantage Password Manager as well, still crashes. I also tried the:
Dism /Online /Cleanup-Image /RestoreHealth
but no luck, my mstsc.exe is still crashing when the remote session window is closed.
Any ideas? Happy to upload/provide more details, here's the Report.wer contents from
C:\Users\myusername\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_mstsc.exe_fe9be6b453d387663f457b9f305ac5e3ae6f5fc2_00000000_2fb47393\Report.wer
Version=1
EventType=CLR20r3
EventTime=130332895175356766
ReportType=2
Consent=1
UploadTime=130332895176424161
ReportIdentifier=1d23a02d-7507-11e3-81f8-f0def1f95c65
Response.BucketId=c93f173301a697688e31de36235ffda6
Response.BucketTable=5
Response.LegacyBucketId=-439202015
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=mstsc.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=6.3.9600.16384
Sig[2].Name=Problem Signature 03
Sig[2].Value=5215e2b5
Sig[3].Name=Problem Signature 04
Sig[3].Value=WHSOLConnector
Sig[4].Name=Problem Signature 05
Sig[4].Value=2.5.7.7
Sig[5].Name=Problem Signature 06
Sig[5].Value=4beac4d4
Sig[6].Name=Problem Signature 07
Sig[6].Value=70
Sig[7].Name=Problem Signature 08
Sig[7].Value=71
Sig[8].Name=Problem Signature 09
Sig[8].Value=System.NullReferenceException
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\WINDOWS\system32\mstsc.exe
UI[3]=Remote Desktop Connection has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\WINDOWS\system32\mstsc.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\system32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\system32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\system32\ADVAPI32.dll
LoadedModule[5]=C:\WINDOWS\system32\GDI32.dll
LoadedModule[6]=C:\WINDOWS\system32\USER32.dll
LoadedModule[7]=C:\WINDOWS\system32\msvcrt.dll
LoadedModule[8]=C:\WINDOWS\system32\ole32.dll
LoadedModule[9]=C:\WINDOWS\system32\OLEAUT32.dll
LoadedModule[10]=C:\WINDOWS\system32\SHELL32.dll
LoadedModule[11]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.16384_none_62475f7becb72503\COMCTL32.dll
LoadedModule[12]=C:\WINDOWS\system32\COMDLG32.dll
LoadedModule[13]=C:\WINDOWS\system32\SHLWAPI.dll
LoadedModule[14]=C:\WINDOWS\system32\CRYPT32.dll
LoadedModule[15]=C:\WINDOWS\system32\WINHTTP.dll
LoadedModule[16]=C:\WINDOWS\system32\credui.dll
LoadedModule[17]=C:\WINDOWS\system32\Secur32.dll
LoadedModule[18]=C:\WINDOWS\system32\CRYPTUI.dll
LoadedModule[19]=C:\WINDOWS\system32\CFGMGR32.dll
LoadedModule[20]=C:\WINDOWS\system32\WS2_32.dll
LoadedModule[21]=C:\WINDOWS\system32\NETAPI32.dll
LoadedModule[22]=C:\WINDOWS\system32\RPCRT4.dll
LoadedModule[23]=C:\WINDOWS\system32\WINMM.dll
LoadedModule[24]=C:\WINDOWS\system32\IPHLPAPI.DLL
LoadedModule[25]=C:\WINDOWS\SYSTEM32\sechost.dll
LoadedModule[26]=C:\WINDOWS\SYSTEM32\combase.dll
LoadedModule[27]=C:\WINDOWS\system32\MSASN1.dll
LoadedModule[28]=C:\WINDOWS\system32\NSI.dll
LoadedModule[29]=C:\WINDOWS\system32\netutils.dll
LoadedModule[30]=C:\WINDOWS\system32\srvcli.dll
LoadedModule[31]=C:\WINDOWS\system32\wkscli.dll
LoadedModule[32]=C:\WINDOWS\system32\WINMMBASE.dll
LoadedModule[33]=C:\WINDOWS\system32\WINNSI.DLL
LoadedModule[34]=C:\WINDOWS\system32\SHCORE.DLL
LoadedModule[35]=C:\WINDOWS\system32\DEVOBJ.dll
LoadedModule[36]=C:\WINDOWS\system32\SSPICLI.DLL
LoadedModule[37]=C:\WINDOWS\system32\IMM32.DLL
LoadedModule[38]=C:\WINDOWS\system32\MSCTF.dll
LoadedModule[39]=C:\Windows\system32\nvinitx.dll
LoadedModule[40]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll
LoadedModule[41]=C:\WINDOWS\system32\CRYPTBASE.dll
LoadedModule[42]=C:\WINDOWS\system32\bcryptPrimitives.dll
LoadedModule[43]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[44]=C:\WINDOWS\system32\credssp.dll
LoadedModule[45]=C:\WINDOWS\system32\NTASN1.dll
LoadedModule[46]=C:\WINDOWS\SYSTEM32\clbcatq.dll
LoadedModule[47]=C:\WINDOWS\system32\PROPSYS.dll
LoadedModule[48]=C:\WINDOWS\system32\dwmapi.dll
LoadedModule[49]=C:\WINDOWS\system32\mstscax.dll
LoadedModule[50]=C:\WINDOWS\system32\PSAPI.DLL
LoadedModule[51]=C:\WINDOWS\system32\d2d1.dll
LoadedModule[52]=C:\WINDOWS\system32\d3d11.dll
LoadedModule[53]=C:\WINDOWS\system32\MSACM32.dll
LoadedModule[54]=C:\WINDOWS\system32\VERSION.dll
LoadedModule[55]=C:\WINDOWS\system32\SETUPAPI.dll
LoadedModule[56]=C:\WINDOWS\system32\DWrite.dll
LoadedModule[57]=C:\WINDOWS\system32\bcrypt.dll
LoadedModule[58]=C:\WINDOWS\system32\ncrypt.dll
LoadedModule[59]=C:\WINDOWS\system32\pdh.dll
LoadedModule[60]=C:\WINDOWS\system32\dxgi.dll
LoadedModule[61]=C:\WINDOWS\system32\explorerframe.dll
LoadedModule[62]=C:\WINDOWS\system32\DUser.dll
LoadedModule[63]=C:\WINDOWS\system32\DUI70.dll
LoadedModule[64]=C:\WINDOWS\system32\WINTRUST.dll
LoadedModule[65]=C:\Windows\system32\WHSOLConnector.dll
LoadedModule[66]=C:\WINDOWS\system32\mscoree.dll
LoadedModule[67]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[68]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll
LoadedModule[69]=C:\WINDOWS\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_88dcdb0b2fb19957\MSVCR80.dll
LoadedModule[70]=C:\WINDOWS\system32\profapi.dll
LoadedModule[71]=C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\mscorlib\97d2eb053ee241db571311577790ae43\mscorlib.ni.dll
LoadedModule[72]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorjit.dll
LoadedModule[73]=C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\System\8b12c5fec7e8912da325ee73b380e652\System.ni.dll
LoadedModule[74]=C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\System.Drawing\3eac16e6688dfec78565e3e71a26266f\System.Drawing.ni.dll
LoadedModule[75]=C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\System.Windows.Forms\d78d7a76a56319e4bc1cbffa3a90a0e1\System.Windows.Forms.ni.dll
LoadedModule[76]=C:\WINDOWS\System32\Essentials\VCListener.dll
LoadedModule[77]=C:\WINDOWS\system32\MF.dll
LoadedModule[78]=C:\WINDOWS\system32\MFCORE.DLL
LoadedModule[79]=C:\WINDOWS\system32\ksuser.dll
LoadedModule[80]=C:\WINDOWS\system32\MFPlat.dll
LoadedModule[81]=C:\WINDOWS\system32\RTWorkQ.DLL
LoadedModule[82]=C:\WINDOWS\system32\AVRT.dll
LoadedModule[83]=C:\Windows\System32\MSAudDecMFT.dll
LoadedModule[84]=C:\WINDOWS\System32\MMDevApi.dll
LoadedModule[85]=C:\WINDOWS\System32\perfos.dll
LoadedModule[86]=C:\Windows\System32\msxml6.dll
LoadedModule[87]=C:\WINDOWS\system32\NLAapi.dll
LoadedModule[88]=C:\Windows\System32\rasadhlp.dll
LoadedModule[89]=C:\WINDOWS\system32\WTSAPI32.dll
LoadedModule[90]=C:\WINDOWS\system32\WINSTA.dll
LoadedModule[91]=C:\WINDOWS\system32\mswsock.dll
LoadedModule[92]=C:\WINDOWS\system32\DNSAPI.dll
LoadedModule[93]=C:\Program Files\Bonjour\mdnsNSP.dll
LoadedModule[94]=C:\WINDOWS\System32\fwpuclnt.dll
LoadedModule[95]=C:\WINDOWS\system32\DPAPI.DLL
LoadedModule[96]=C:\WINDOWS\system32\CRYPTSP.dll
LoadedModule[97]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[98]=C:\WINDOWS\system32\schannel.DLL
LoadedModule[99]=C:\WINDOWS\system32\tspkg.DLL
LoadedModule[100]=C:\WINDOWS\system32\ncryptsslp.dll
LoadedModule[101]=C:\WINDOWS\SYSTEM32\gpapi.dll
LoadedModule[102]=C:\WINDOWS\system32\wdmaud.drv
LoadedModule[103]=C:\WINDOWS\system32\AUDIOSES.DLL
LoadedModule[104]=C:\WINDOWS\SYSTEM32\powrprof.dll
LoadedModule[105]=C:\WINDOWS\system32\msacm32.drv
LoadedModule[106]=C:\WINDOWS\system32\midimap.dll
LoadedModule[107]=C:\Windows\System32\msmpeg2vdec.dll
LoadedModule[108]=C:\WINDOWS\System32\msvproc.dll
LoadedModule[109]=C:\WINDOWS\system32\LINKINFO.dll
LoadedModule[110]=C:\WINDOWS\system32\ntshrui.dll
LoadedModule[111]=C:\WINDOWS\system32\cscapi.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=Remote Desktop Connection
AppPath=C:\Windows\System32\mstsc.exe
ReportDescription=Stopped working
ApplicationIdentity=00000000000000000000000000000000

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

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 Connection Authentication Error from Windows 8.1 Pro to Windows 7 Pro

I keep trying to connect to my server running Windows 7 Pro from my laptop running Windows 8.1 Pro, but I get the following message after providing
my credentials:
"An authentication error has occurred (Code: 0x8007001f)"
I can't find any reference to this error code being associated with using remote desktop.

Hello,
Are you connecting to a server as part of a domain ? if so confirm you are using adequate credentials for remote desktop for example: username: domain\administrator
if not you can try connecting to the localhost using:
username: .\administrator - for example
also you can try running your remote connection in admin mode:
Win + R - bring up run then type:
mstsc /admin
hope that helps.
Cheers,
Harry

Server 2012 R2 Remote Desktop Connection Broker

I have installed RDS on a server named PLUTO on which Windows 2012 R2 datacenter is in. There is a domain controller (domain name: AGROSY) running on a Linux server. We have used Samba 3.6.6 to control the file sharing system.
When I attempt to install RDS in Server Manager, it states as following: could not retrieve the deployment information from RD connection broker server pluto.AGROSY.
Then, I searched a lot of solutions, e.g. and tried as following:
Enter-PSSession -ComputerName pluto --> which works;
but Enter-PSSession -ComputerName pluto.AGROSY --> which gives the error message as: Enter-PSSession : Connecting to remote server pluto.AGROSY failed with the following error message : WinRM cannot process the request. The following
error with errorcode 0x80090311 occurred while using Kerberos authentication: There are currently no logon servers available to service the logon request.
If I ping the pluto.AGROSY, it works as well.
I have no idea how it can be solved, please help me out. Thanks a lot!

Hi,
Thanks for your comment. Sorry for late reply.
Initially please enable the PowerShell remoting in your case.
Enable-PSRemoting
http://technet.microsoft.com/en-us/library/hh849694.aspx
For FQDN name, please see that RDCB is properly configured and also certificate which you have used for RDS environment must be trusted with its private key and must match the FQDN name of the server. Did you seen the certificate has been properly used and
configured. You can go through following article for certificate and also for configuring RDCB role.
Configuring RDS 2012 Certificates and SSO
Configuring HA for the Remote Desktop Connection Broker in a 2012 RDS Farm
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Remote Desktop Connection - cannot proceed because authentication is not enabled

Similar Messages

Maybe you are looking for