On the LFDomain web site - developer of LF Connection Keeper - it indicates that the application automatically logs you out when you shut it down, and some users have problems when starting Windows again - mainly because Windows is often slower to connect to the Internet than LFCK is trying to logon, thus disallowing access to the Internet. Also, some users report getting 503 errors and the developer blames that on the ISP logon server not being accessible at the time. This sounds like the users wherever this is developed must logon to their ISP's servers in order to get Internet access, and logoff when they finish. I'm in the USA and I have a broadband connection that is never logged out from the Web.
Can this default behavior by LFCK be reconfigured? I'd really hate to lose my connection due to LFCK trying to do something it can't and then spend the next couple days troubleshooting it! (LFCK apparently sets up as a service and takes over a few Windows DLLs, including mfc42.dll). Also, it looks like LFCK requires users to use it as a proxy to access the Internet. If this is the case, I don't think this would work for me.