Calling Card "Checking for Updates - Unable to Connect" error on Vista

Hi there:

On occasion whenever I install my Calling Card on Vista and start it for the first time, I get the following error:

"Checking for Updates...." Then "Unable to connect". The internet connection is working fine, so I am unsure why this happening - anyone else run into this?

Thanks.

[8F] The NyQuil Kid

Find more posts tagged with

Accepted answers

SCSService

@Straifer wrote:
Can we get this issue escalated? I am having this same exact problem on both Windows Vista and 7.

The issue already has been... I worked with someone and we narrowed the problem to being some combination of a DNS mismatch and/or an SSL issue. They said they're working on it and would post a reply to this thread when it has been fixed.

Meanwhile, you can avoid it with the following batch file:

start iexplore "https://secure.logmeinrescue.com"

msiexec /qn /i "LogMeIn_Rescue_Calling_Card.msi" RUN=0

...that will open an IE window to the https site, which resolves the SSL mismatch and then it silently installs the calling card without running it afterwards.

That's what we're using currently to deploy the calling card. Closing the IE window is a bit annoying, but workable.

Hope this helps.

All comments

Straifer

Can we get this issue escalated? I am having this same exact problem on both Windows Vista and 7.

SCSService

An update -

If you go to https://secure.logmeinrescue.com in internet explorer on a machine where this is happening then simply close the browser after the page opens the calling card will then work. It's got something to do with SSL certificates.

This is a solution that can at least be pseudo-scripted for deployment, though it's obviously not ideal.

SCSService

Just an update... I had this happen on a Windows 7 installation as well in a virtual machine. I made a snapshot before installing. I installed and had this problem, then rolled back, disabled UAC, the windows firewall and windows defender then rebooted then tried it again - still the same problem.

I can't fathom why this would happen with some copies and not others now. I can only assume it might have something to do with different sets of Windows updates. I submitted a support ticket.

SCSService

I can offer some feedback on this issue. Thus far we've only noticed this occurring on Vista machines. In all cases they were brand new Windows installations as well (directly from a generic OEM disc - no third party system-restore stuff to complicate things).

Both times thus far I've seen this we had UAC still enabled in the computer. After disabling UAC and rebooting the calling card still fails. Uninstalling and reinstalling at that point doesn't help.

I can only assume that the problem has to do with Vista in general or installing with UAC enabled in Vista...maybe some mismatch due to the installation prompting for elevated rights, and thus running in a different user account than the logged-in one?

If someone from logmein could take a look at this it would be appreciated.

Thanks!

The NyQuil Kid

I found a workaround that might be helpful:

a) In addition to my calling card, I have a website where clients can visit and have me remote in - I noticed that if the calling card fails to connect, I have them visit my site, fill out the fields and click my connect button - this installs the necessary Active X control. Once they are connected, I have them close out of that session and try the calling card again - voila, the calling card works.

[8F] The NyQuil Kid

snakes

wow, fast help we are getting in here..

snakes

same here - some machines works perfect, others don´t.

Support please.