Unsolved
This post is more than 5 years old
5 Posts
0
5904
August 3rd, 2015 03:00
Wyse PocketCloud Auto Discovery Windows is not readable.
Wyse PocketCloud Auto Discovery Windows is not readable.
I install Wyse PocketCloud to my Galaxy tab and Wyse PocketCloud Windows Companion (Version 2.1.5) to my windows 7 Ultimate (64 bits) with Norton Internet Security. I already config the fireware (norton Fireware) to allow Wyse PocketCloud widows with full access. I am able to login to my Gmail account via Auto Discovery Setting in both PC and my Galaxy tab. I use "Diagnostic" in the PocketCloud WIndows Companion, it show no issue. However, after I select my PC name in my computer list to connect to the PC from my Galaxy tab, it said that "Could not connect to server". I read in the forum. There is something to do with the Wyse Pocket Clud Auto Discovery setting. I do follow as below.
1. right click to the PocketCloud Windows Companion.
2. Click on Auto Discovery Settings
3. The Wyse PocketCloud Auto Discovery Windows pop up.
However, the windows pop up side is too small. I cannot read all the content in side. I cannot change the windows side or make it full screen. Please help me on this, so I cannot try to solve the "Could not connect to server" issue.
Thank you for your help.
thepui
5 Posts
0
August 6th, 2015 00:00
Sorry! I can fixed the PocketCloud Auto Discovery Windows to small by change the font side in the control panel display. Now, I try to follow the instuction in another Thread as below.
"Could you please check Windows Companion Settings.
Right click on Windows Companion icon > Auto Discovery Settings > Options
Check VNC Port. It should be 5900. Then run test. Click TEST button.
Try to connect again via 3G"
My question is how can I check VNC port. It try 5900, and 5800. It show "VNC is not listening on this port. Do you still want to save it?" I click yes.
After Click TEST button. It show "VNC to port 5900(5800) failed."
thepui
5 Posts
0
August 13th, 2015 03:00
I already got it work after install UltraVNC. However, I found another issue. I will write another Thread if I cannot find the solution.