{"id":229,"date":"2018-12-31T15:20:31","date_gmt":"2018-12-31T15:20:31","guid":{"rendered":"https:\/\/unsrewiki.1sys1.com\/?p=229"},"modified":"2018-12-31T15:20:31","modified_gmt":"2018-12-31T15:20:31","slug":"the-remote-computer-requires-network-level-authentication","status":"publish","type":"post","link":"https:\/\/server-help.org\/index.php\/2018\/12\/31\/the-remote-computer-requires-network-level-authentication\/","title":{"rendered":"The remote computer requires Network Level Authentication"},"content":{"rendered":"\n
\"\"<\/figure><\/div>\n\n\n\n

The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support.<\/p><\/blockquote>\n\n\n\n

Or this can also happen: <\/p>\n\n\n\n

The remote computer that you are trying to connect to requires Network Level Authentication but your Windows domain controller cannot 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.<\/p><\/blockquote>\n\n\n\n

1] Change Remote Desktop setting<\/strong><\/p>\n\n\n\n

Going via the Remote Desktop Settings route is the simpler solution. \nIt will work for you and you might not feel the need to enable NLA back \non. So, if you are ready for this solution, here is how you go about it.\n Follow the steps carefully.<\/p>\n\n\n\n

1] Go to \u2018Run\u2019 and type \u2018sysdm.cpl<\/strong>\u2019 and hit the \u2018Enter\u2019 button.<\/p>\n\n\n\n

2] You are now in the System Properties<\/strong> window. You need to go to the Remote<\/strong> tab.<\/p>\n\n\n\n

3] Find the \u201cAllow connections only from computers running Remote Desktop with Network Level\u00a0Authentication\u00a0(recommende<\/em>d)\u201d and uncheck this option.<\/p>\n\n\n\n

\"\"<\/figure><\/div>\n\n\n\n

4] Click \u2018Apply\u2019 and then click \u2018OK\u2019 or hit the \u2018Enter\u2019 button to disable Network Level Authentication<\/em>. <\/p>\n\n\n\n

This fix should work because you just undid the only thing that was causing the problem. But just in case it did not work, or you do not want to pursue this route, there is another option which is also simple to follow. <\/p>\n\n\n\n

2] Edit Registry<\/strong> (method is more elaborate and needs more attention) <\/p>\n\n\n\n

Note: Please backup your data before making changes to the registry of the system.<\/p><\/blockquote>\n\n\n\n

Follow the steps very carefully and you will be good to go. You have \nalready created your System Restore point so there\u2019s nothing to worry \nabout anymore. So here we go.<\/p>\n\n\n\n

1] Go to \u2018Run\u2019 and type \u2018regedit\u2019<\/strong> and click \u2018OK\u2019 or hit \u2018Enter\u2019. This opens the Registry Editor.<\/em><\/p>\n\n\n\n

2] Look at the left panel in the Registry Editor window and find the registry key called:<\/p>\n\n\n\n

HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Lsa<\/code><\/pre>\n\n\n\n
3] Select Lsa<\/strong> and then locate Security Packages<\/strong> in the right panel. Double-click on it. <\/p>\n\n\n\n
\"\"<\/figure><\/div>\n\n\n\n
4] Find the Edit Multi-String<\/em> option and type \u2018tspkg\u2019 <\/strong>in the Value data box. This will be the only value.<\/p>\n\n\n\n
5] Thereafter, locate the following registry key in the navigation \npane: \nHKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\SecurityProviders<\/p>\n\n\n\n
6] Double-click SecurityProviders in the right-pane to open its properties.<\/p>\n\n\n\n
7] Type credssp.dll in the Value data box and let it be the only value.<\/p>\n\n\n\n
8] Click \u2018OK\u2019 and close the Registry Editor<\/em>.<\/p>\n","protected":false},"excerpt":{"rendered":"
The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support. Or this can also happen: The remote computer that you are trying to connect to requires Network Level Authentication but your Windows domain controller cannot be contacted to perform NLA. If you are…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"_links":{"self":[{"href":"https:\/\/server-help.org\/index.php\/wp-json\/wp\/v2\/posts\/229"}],"collection":[{"href":"https:\/\/server-help.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/server-help.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/server-help.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/server-help.org\/index.php\/wp-json\/wp\/v2\/comments?post=229"}],"version-history":[{"count":1,"href":"https:\/\/server-help.org\/index.php\/wp-json\/wp\/v2\/posts\/229\/revisions"}],"predecessor-version":[{"id":233,"href":"https:\/\/server-help.org\/index.php\/wp-json\/wp\/v2\/posts\/229\/revisions\/233"}],"wp:attachment":[{"href":"https:\/\/server-help.org\/index.php\/wp-json\/wp\/v2\/media?parent=229"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/server-help.org\/index.php\/wp-json\/wp\/v2\/categories?post=229"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/server-help.org\/index.php\/wp-json\/wp\/v2\/tags?post=229"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}