none
Remote Desktop Connection - Issue RRS feed

  • Question

  • Hi Team,

    When a user trying to access the server via remote they are getting the below error. Could someone please advise what action should we take to remediate this? Thanks.

    An authentication error has occurred.

    The Local Security Authority cannot be contacted.

    Remote computer : computer name

    This could be due to an expired password.

    Please update your password if it has expired.

    For assistance, contact your administrated or technical Support.

    Wednesday, August 7, 2019 7:38 PM

All replies

  • 1. Check the connectivity for RDS server from users' PC

    2. If the connection is OK, Check the user permission whether the user is allowed to access RDS or not

    3. Check the RDS server whether it's allowed to login via remotely or not

    4. Further you can check RDS server event log for resolve this..

    for further support, Need more details...

    Wednesday, August 7, 2019 9:15 PM
  • Hi Udara,
    Thanks For replying.

    There is no specific RDS server, we'd windows 2008 DC server which we migrated on windows 2016 now the users are not able to take the RDP of web/app server. They are getting the above message along with below one.

    The Remote computer that your are trying to connect to required Network Level Authentication (NLA), but your Windows Domain Controller can not be contacted to perform NLA. If you are an administrator on the remote computer, you can disable NLA by using the options on the Remote tab of the System Properties dialog box.

    So, can you please guide how can user take RDP with enabling NLA settings.  thanks

    Wednesday, August 7, 2019 11:23 PM
  • HI
    1 can you enter gpresut /h rdp.html on session host server and look which policy is set in below location:
    admnistrative templates\windows components\remote desktop services\remote desktop session host\security
    the rdp.html file is in c:\users\username\
      1.1 if you set security layer to negociate on session host server and reboot the probelmatical server ,will the problem persist ?
    2 Do you use MFA or smard card in your environment ?
    3 do you mean there is only w2016 DC in your environment ?
      can you enter winver in command prompt on problematical server and look the os version and os version number ?[for example windows 10  enterprise 1809 (os build 17763.316)]
    4 Have you still been using RDP self sign certificate in your environment? When you migrate windows 2008 DC to w2016 DC ,did you change RDP self sign certificate ?
    5 from your decription ,after migrating from w2008 DC to w2016 DC ,you can not remote access web server or app server?
    6 "There is no specific RDS server"
       did you mean you not install any RDS role(RDSH,RDCB,RDWEB,RDgateway,RDLS) in your environment ?
    7 can you logon the problematical server local console ?
    8 if you create a new domain user account ,can you remote access problematical server by using this new account when NLA is enable?

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.



    Thursday, August 8, 2019 6:18 AM
    Moderator
  • HI
    Is there any progress on your question?

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, August 15, 2019 3:31 AM
    Moderator