If installing Windows 7 or 8 this step is not necessary. I wont run through the installation of Windows here since you may be installing XP, Vista, 7 or 8. The name of the VM will be needed later when setting up the remote desktop software.
If everything is working correctly so far you will connect to the VM. If its not try connecting to the IP address instead. All other options should be set as shown for this to work. If you want to edit any of the settings just open the. All RDP files are just text files containing lots of settings in plain text. Next log into the VM and open regedit. Sometimes you need to support very old applications but keep the user within a modern and supported operating system.
Using Hyper-V and configuring remote desktop to only launch certain applications from a VM is a great way to keep things working until old applications are retired or updated. Skip to content Home. Search for:. Check the status of the RDP protocol on a remote computer Important Follow this section's instructions carefully.
To check and change the status of the RDP protocol on a remote computer, use a network registry connection: First, go to the Start menu, then select Run. In the text box that appears, enter regedt To check the group policy configuration on a local computer, open a Command Prompt window as an administrator, and enter the following command: After this command finishes, open gpresult. Set the policy to either Enabled or Not configured. In GPM, navigate to the organizational unit OU in which the blocking policy is applied to the affected computers and delete the policy from the OU.
On either computer, if one or both services are not running, start them. Check the status of the RDP listener For this procedure, use a PowerShell instance that has administrative permissions. To connect to a remote computer, run the following cmdlet: Enter qwinsta. Export the RDP listener configuration from a working computer. Sign in to a computer that has the same operating system version as the affected computer has, and access that computer's registry for example, by using Registry Editor.
For example, in Registry Editor, right-click the entry, select Export , and then enter a filename for the exported settings. Copy the exported. If you still can't connect, check the status of the RDP self-signed certificate. When you are prompted to select the certificate store to manage, select Computer account , and then select the affected computer. Note that if you just want to be able to remote control the desktop of the computer running on Windows XP Home Edition, it may be easier and wiser to use the free VNC as alternative instead.
Then download and install DevCon direct download link to devcon. Open a command prompt window Cmd , and the change directory into the i folder extracted by DevCon.
Then run the following command to reinstall rdpdr driver:. The other error message is-. The remote computer that you are trying to connect to requires network level authentication NLA , 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. No matter what remote desktop tool you are using, you will keep getting a similar error message until or unless you make the mandatory changes. In a nutshell, you need to disable the Network Level Authentication or loosen up the settings so that the remote computer can connect to the host machine without any error.
By default, your Windows machine allows connections only from computers that have Network Level Authentication. This inbuilt security function lets you block all the unwanted connections when you have a large local area network, and your computer is open for share.
You can change the network location from public to private and vice versa as per your requirement. However, the same settings can cause the issue as mentioned earlier. Therefore, you can try to disable this option and check if the problem remains or not. Following the following steps to allow connections without NLA. This is much more user-friendly, and you do not need any expert knowledge to get it done.
Even if you sideload Group Policy Editor, you might not get the similar option in that third-party app. Therefore, this method is applicable to Windows 10 Pro and Enterprise users only. Network Level Authentication can be blocked via Registry Editor as well. However, you need to do that on the remote computer.
This is quite easy when your host computer is connected to the remote computer via Local Area Network. In any case, if your Windows registry editor is disabled accidentally or by the syatem administartor, first enable the Windows registry editor.
To turn off or disable Network Level Authentication with the help of Windows PowerShell, you need the remote computer name. Otherwise, this is not possible to get started with this method. If you have collected that, go ahead and follow these steps.
0コメント