Authorization problem with LogMeIn - SSL configuration?
Hello people.
I first thought it might be a problem with Firefox, but after installing Opera, I had exactly the same problem (thanks to those who helped there!). A friend of mine had asked me to help him out with a problem, and gave me access through LogMeIn. I had entered previously, while I still had Slackware 12.x installed (32 bit), but now, with SW64, and FF3.5.x, I can't get in. I mean, I can _log_ in, but clicking on 'Remote control', the system advances past 'Connected' and then disconnects (there seems to be a timeout). I configged the logging in LMI for including debug information, and got this: 2009-11-09 01:22:40.218 - Debug - LogMeIn - Socket - 216.52.233.217:443 - SSL cipher AES256-SHA (256 bits) TLSv1/SSLv3 selected. 2009-11-09 01:22:40.218 - Debug - LogMeIn - Socket - 216.52.233.217:443 - SSL session: REUSED, timeout is 600 seconds 2009-11-09 01:22:40.218 - Debug - LogMeIn - Socket - 216.52.233.217:443 - Assigned remote address: 201.253.152.112:46619 2009-11-09 01:22:40.218 - Debug - LogMeIn - Socket - 216.52.233.217:443 - Connected (SSL: yes). 2009-11-09 01:22:40.218 - Debug - LogMeIn - Socket - 216.52.233.217:443 - SSL handshake started. 2009-11-09 01:22:40.453 - Debug - LogMeIn - Socket - 201.253.152.112:46619/rawssl - SSL shut down - socket stays connected 2009-11-09 01:22:40.453 - Debug - LogMeIn - Socket - 201.253.152.112:46619/rawssl - SSL handshake started. 2009-11-09 01:22:40.453 - Debug - LogMeIn - Socket - 201.253.152.112:46619/rawssl - Error (in recv): Se ha forzado la interrupción de una conexión existente por el host remoto. (10054) 2009-11-09 01:22:40.453 - Debug - LogMeIn - Socket - 201.253.152.112:46619/rawssl - Closed (rcvd 176 bytes, sent 345 bytes). 2009-11-09 01:22:40.453 - Error - LogMeIn - Socket - 201.253.152.112:46619/rawssl - SSL error: SSLv2/v3 read client hello A (in accept). 2009-11-09 01:22:40.468 - Debug - LogMeIn - Socket - 216.52.233.217:443 - SSL handshake done. 2009-11-09 01:22:40.468 - Debug - LogMeIn - Socket - 216.52.233.217:443 - SSL cipher AES256-SHA (256 bits) TLSv1/SSLv3 selected. 2009-11-09 01:22:40.468 - Debug - LogMeIn - Socket - 216.52.233.217:443 - SSL session: REUSED, timeout is 600 seconds 2009-11-09 01:22:40.468 - Debug - LogMeIn - Socket - 216.52.233.217:443 - Assigned remote address: 201.253.152.112:58874 The line before the 'Error' line, translated to English, says as much as 'The existing connection was dropped (interrupted) by the host". The user forums at LMI aren't very helpful - the problem is discussed but no solution. There is one line marked as 'Error', I've tried to google this message, read a lot of mails commenting it, but most of the issues were Ubuntu-related. I couldn't find any difference in configuration of OpenSSL, /etc/ssl/xxx, etc, as compared to before changing to SW64. They just all look identical. I can't find any .pem file on the disk, but then there wasn't one before, either. I'd appreciate suggestions... John |
Do you have the system set up with reverse DNS....a TXT http://en.wikipedia.org/wiki/Reverse_DNS_lookup?
Reverse DNS lookup |
Quote:
John |
... Anyway, I just tried
dig -x xxx.xxx.xxx.xxx ptr (xxx... is my IP) from another machine, and it resolves correctly to the domain name assigned dynamically. John |
Quote:
from = http://community.logmein.com/logmein...message.id=541 ;; Quote:
|
Quote:
Thanks for the info. I'm quite convinced this is not my problem - I'm not using any plugin to access LMI - never have. The thread speaks about using the plugin if java fails - but I have a running Java installation. As far as I understand things, I don't need a plugin. John |
Welllll.... Maybe not - I had missed the last part of the thread, where it says the 64bit java plugin is incompatible with LMI. Is this really true? I thought Java was the flagship of compatibility?
I have very little incentive (LMI is not enough) to install 32-bit Java again, and invite problems with ndiswrapper etc. Thanks again, John |
All times are GMT -5. The time now is 09:57 PM. |