Manual RDP Problems

Hi irongiant.

1) Try to see if your computer's and your phone's date/time is correct. This might be causing certificates to expire. 

If that does not work 

2) Try to go settings and accept all certificates.


I am assuming you have NLA enabled on that machine. 

Let me know how if goes.

I also have this issue with connecting to my Windows Home Server. It used to work just fine and ever since the update i get the cannot connect error message.

We'll try to find the rootcause for your problems, can you try the following?
1) In PocketCloud on your Android Phone can you try going to the Settings page and Enable the Accept All Certificates option?
2) Create a new RDP connection from scratch

Are you using Auto Discovery? We'll keep looking at this internally as well.

Wyse PocketCloud Team

 Originally Posted by daniel 

We'll try to find the rootcause for your problems, can you try the following?
1) In PocketCloud on your Android Phone can you try going to the Settings page and Enable the Accept All Certificates option?
2) Create a new RDP connection from scratch

Are you using Auto Discovery? We'll keep looking at this internally as well.

Accept all Certificates is enabled... New RDP connection... Have tried auto discovery... Still cannot connect. Having done a little research last night, it seems as though Windows Home Server 2003, does not support NLA. Microsoft's Knowledge Base states that RDP 6 is required for NLA, Home Server 2003, doesn't include RDP 6, nor does any of it's updates. Uninstalling Pocket Cloud Pro, and reinstalling Pocket Cloud Free, allows free to work, but with the one computer connection limitation. Is there anyway that previous (non NLA) versions of Pro can be re-released? Perhaps an option to enable/disable NLA... Thank you

Thanks for the details, this is very helpful information! We'll add a toggle switch to enable/disable NLA in the next maintanance release.

Wyse PocketCloud Team

We are prioritizing a maintenance release to address this. Sorry for the inconvenience.
BTW, this can resolved in some instances by enabling "Accept All Certificates" in the Settings page.

Wyse PocketCloud Team

 Originally Posted by daniel 

Thanx Daniel... I'll continue with the free version until the fix. Unless you can provide me a link to the previous version of Pro. I've also been meaning to update to Server 2008, maybe this is the excuse I need to get it done.

I think I'm having the same issue. Just upgraded to Pro, but cannot connect to any 2003 servers, which is mostly what I got it for. Can connect to Windows 7 ok. 2003 and 2008 just get a grey screen 

I have a major problem with this same issue. I am the IT manager for a computer service center. Our office uses a home server exclusively, which is server 2003. This new update has broken the connection to our office. Our office is completely down for on-site invoicing. All of our on-site technicians use android phones, and all of them use PocketCloud for invoicing! Please tell me that you can release an emergency update or an APK I can manually install on the technicians' phones.

Same issue here getting to Windows Home Server v1 and Server 2003 systems...! Argh!! Just wasted 2 hours of my life trying to figure out what was wrong. We just installed a new router and I assumed it was related to that rather than the client that had worked fine for so long without issue...

Accepting all certs has no effect, as a matter of fact, I finally realized the issue was with the client after clearing all saved certs. Upon connection I was prompted to accept the cert so I knew traffic was getting to the client...

HTC Incredible w Froyo

this can resolved in some instances by enabling "Accept All Certificates" in the Settings page.

this worked for me on my Galaxy S running android 2.2

Thanks.

Hi,

New release is coming soon with NLA switch ON/OFF option, which should solve connection issues on Paid version.

Regards

I'm having the same issue. It took me more than 15 minutes to find out and could not return $15.00 app. Called WYSE support and they told me I had to use this forum to find answer. 

Will I be able to use on windows server 2003 and Win 7?

I am having what I think is a similar problem. We use server 2000. Until recently on our network the manual connection worked fine. I have a Droid X, I have made sure that the settings accept all certificates. I continue to get the "Could not connect to server" message. I am using the pro version of pocket cloud. My initial question was whether this has to do with something entirely different--say like different security settings on our network--but this is not it because my home network doesn't have those settings and I cannot connect. In both cases, if I use the Windows companion (both are windows 7 pro) I am able to connect. That presents a problem for me as well, because when I had been using the manual connection, there was no distortion of the 16x9 screen layout of the host computer that I was RDP-ing into; not so with the Windows companion. Programs that require various windows from within themselves, are "scrunched" into the portrait size of the Droid X, even when in landscape mode. 

This is frustrating, and makes me want to use the manual, but that doesn't work. It suddenly makes this not very usable for me.