> Troubleshoot RDP Connection Problems
> Generally, RDP settings should have been correctly set during DVM Template creation; as such, a user should not experience any problems in logging on to a DVM using RDP. The most common reasons for not being able to RDP to a DVM are as follows:

> • | RDP not enabled

> Enable RDP protocol on the virtual machine as outlined in (RDP Connections Only) Enable Remote Desktop and Set Remote Desktop Users.

> • | AD groups doesn’t have permissions

> Select an AD user group that has permissions to connect to this DVM using RDP. Verify that the Group Policy does not disallow RDP. Make sure that the user has a UPN (User@Company.com) in Active Directory.

> • | Firewall prevents communication

> Ensure that there is no Windows firewall rules that prevent the Pano device from communicating with the Pano DAS running on every DVM. Go to Configure DVM Firewall. Some organizations have a policy to enable the Windows firewall and many do not have this policy. You can troubleshooting, by temporarily disabling the firewall.

> • | RDP not listening on the correct port

> Ensure that RDP runs on default port 3389.

> • | Incomplete UPN

> Check to verify that the user has a complete UPN (User@Company.com) defined within Active Directory or your alternate user authentication service. For more information, go to No Privileges or No UPN Format.

> • | Data encryption error

> If you try to connect to a DVM using RDP, you might receive a data encryption error. This problem is caused by a known issue (KB323497) in Windows XP. To fix this problem, do the following:

> 1. | Launch Registry Editor.

> 2. | Locate and click the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService\Parameters registry subkey.

> 3. | Under this registry subkey, delete the following values:

> • | Certificate

> • | X509 Certificate

> • | X509 Certificate ID

> 4. | Quit Registry Editor, and then restart the virtual machine.

Did you find what you're looking for?
v2.5.1