Unsolved
This post is more than 5 years old
2 Posts
0
31590
August 2nd, 2015 01:00
Problem Logging-in to PC Companion for Auto Discovery
Problem Logging-in to PC Companion for Auto Discovery
I just purchased PocketCloud (version:1.1.208) and I’m having trouble setting it up to access my home computer.
Phone: Verizon Motorola Droid X
Android Version: 2.2.1
PC: Windows Vista Home Premium 64-bit
Connection method: Auto Discovery
When I try to log-in to the PocketCloud Companion on my PC a window pops up saying:
“The PocketCloud Service is currently not running. Please start the services by following these steps…etc, etc”
When I follow those steps by going to Control Panel > Administrative Tools > Services > Wyse PocketCloud it shows it as started.
I’ve tried stopping and restarting it and I get the same message even though it appears to be “started”.
Also, when I test the RDP and VNC connectivity it fails to both ports.
I’ve tried going to Windows Firewall Settings and making sure that the following exceptions are checked: PocketCloud Service, Routing and Remote Access, TightVNC Server, TightVNC Server
I’ve also gone to Control Panel > System > Remote Settings and made sure that “Allow Remote Assistance” is checked.
Can you tell me what else I can do to get this up and running?
lmorse
7 Posts
0
August 13th, 2015 00:00
I think I am having similar issues: I am running PocketCloud on an iPhone 3gs. I have PocketCloud companion installed on a Windows 7, 32 bit Home laptop. I can connect to my PC when both iPhone and PC are connected to the same Wireless Network, however if the iPhone is not connected to the wireless network, PocketCloud crashes when I try to log in to my PC.
I have played with Ports, adding them to Firewall exceptions, I have allowed remote access. I have checked for updates and am using the latest version of PocketCloud companion.
I am unable to find the options in PocketCloud for VNC and "allow loopback connections" - is this supposed to be in a tab in PocketCloud companion? I do not get any additional tabs. I have allowed loopback connections in TightVNC.
VNC Test is succesful with port 5900, however RDP fails on port 3389.
Looking forward to finding a solution.
openminds
1 Message
0
August 13th, 2015 00:00
I am having the same problem. Windows 7 64bit.
I am able to log in with the Google Account credentials, but when I go to test RDP/VNC connectivity, I continuously get a "VNC to port 5900 failed". I added the ports in Windows Firewall, I have disabled Windows Firewall. I tried changing the port number from null to 27895 as mentioned above as well as many other test numbers, still fail. I tried a few different ports with same result. However, if I use 3389 as VNC, it passes, though I doubt this would work. Any more ideas?
websuperman
5 Posts
0
August 13th, 2015 00:00
I am getting the exact same error. Running Windows 7 64 Bit. If I run diagnostic everything passes. However, if I run the autodiscovery I get the error when trying to log in with my google account. I have confirmed that the service is running and the diagnostic from the program shows that the proper ports are working. The test in autodiscovery fails, however. This is the exact error message received when trying to log in using google account:
---------------------------
Wyse PocketCloud Companion
---------------------------
The PocketCloud Service is currently not running. Please start the service by following the steps below:
1. Open the Control Panel
2. Open the “Administrative Tools”
3. Open “Services”
4. Locate the “Wyse PocketCloud” service.
5. Right click and press start.
---------------------------
OK
---------------------------