RDP missing from Pocketcloud
I have installed the Pocketcloud companion software on a new Windows 7 Pro PC which is running on our corporate network.
In the PocketCloud companion software it says RDP is listening on port 3389, and VNC is listening on port 5900.
However on my Android device only the VNC connection has been automatically discovered. Why hasn't the RDP been automatically discovered?
I've installed Pocketcloud companion software on other WinXP PCs in the same network and both VNC and RDP are successfully discovered. Its just this new Windows 7 machine which is giving me trouble.
Any help appreciated.
Lana, Thank you for the suggestion. I tried this and the problem has not been fixed.
1. On the Android device I logged out of PocketCloud and shutdown the device.
2. On the Windows Companion on the PC I selected Sign Out.
3. I waited 60 seconds
4. On the Windows Companion on the PC I selected Sign In.
5. I waited 60 seconds
6. I repeated step 2/3/4/5 three times.
7. I started the android device and ran PocketCloud. I logged into Auto Discovery on PocketCloud. Again it only found the VNC connection to the PC. No RDP connection.
Thank you for trying.
Please give us next info:
-PocketCloud Version number (is it latest Paid 1.2.265 or Free version?)
-WindowsCompanion Version number (is it latest 2.3.7?)
We are trying to create the exact environment to reproduce this issue. But it looks like it is related to this specific Win7Pro PC.
Thanks to Lana for her terrific help this problem has been solved.
If anyone else has the same issue this might help. Usual disclaimer when working with Windows registry; if you don't know how to work with registry, don't! You can break your computer.
In the registry location:
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contr ol\Terminal Server" .
The key "fDenyTSConnections" should be set to 0 (zero). The Companion setup wizard should detect if this value is not zero and correct it, but this did not happen on my PC.
On my PC it was set to 1. I changed the value to 0 and restarted the PocketCloud service (or reboot) and it fixed the problem.