Windows

11 Topics

LogMeIn Client Bug After Forced Password Resets
After the forced password resets last week, a couple people in our organization were getting the following message: Turns out to be something related (at least from what I can tell), to the "I trust this device. Keep me logged in." checkbox when first opening up the client. Had to go into options, delete all stored login credentials, then uncheck the box for trusting the device, for these users to be able to use the program again.
Solved
James18
2 years ago Place Central Discussions
3.9KViews
1like
19Comments
Hamachi Network in Gateway Mode is Giving Gateway an APIPA Address
As the title says, trying to run a Hamachi network setup in Gateway mode. The computer that I have designated as the gateway, however, is getting an APIPA address (169.254.x.x). In truth I'm not entirely sure how this system is intended to work, so I'm not sure if its the fault of my DHCP server on my router or if it's a fault on Hamachi's side. I have even manually set the IP range in the gateway settings on hamachi to match that of my home network's IP range (though higher so that there's no ip conflics, i.e. 192.168.0.200-255). Because of this none of the client computers on the network can access anything on the gateway's network. Anybody run into this issue before or know what's going wrong?
Solved
Official_Dalek
2 years ago Place Central Discussions
3.7KViews
0likes
4Comments
command prompt issue
we are using logmein central. throur the logmein client when you click on the home icon then go through computer management and clicking on command prompt you receive the following error: error title: script error error header: an error has occured in the script on this page. Line: 1136 Char: 59 Error: the operation attempted to access data outside the valid range code: 0 URL: https://console-xlyfethvvn.lmi-app22-02.logmein.com/htem/htem_all.js Do you want to continue running scripts on this page? yes or no. does not make any difference what option you select. however, if we go via the loginme website and selecting command prompt it works with no issues. Does anyone have any suggestion on how to fix this?
sergen
2 years ago Place Central Discussions
2.5KViews
0likes
7Comments
Central not detecting anti-virus software, real-time protection, or virus definition on Win 11 Pro
We have successfully used LogMeIn Antivirus for a year on many Windows 10 Pro computers; however, I just installed it on several new Windows 11 Pro computers. The program appears to install and the policies seem to apply correctly; however LMI Central is not getting updated information from the computers. The Windows 11 Pro computers show successful installation. Scans are running as scheduled and the firewall turned on (although I have since turned it off for testing). In Central, the anti-virus software column says "Unknown", the real-time protection column says "Disabled", and the virus definition column says "Out-of-date." I have changed the LMI AV policy to turn off the firewall and have also disabled the Windows firewall as requested by LMI support. I enabled logging in LMI Control Panel and uninstalled, rebooted, and reinstalled LMI AV and sent the debugging logs to LMI support. So far they keep saying it is a firewall issue but don't know what to suggest to fix it. The log says "Error (in recv): An existing connection was forcibly closed by the remote host" and "Error (in send): An established connection was aborted by are in your host machine." I feel it must be something unique to Windows 11 Pro. Does anyone have any idea what needs to be changed on these computers to get them to report properly to LMI Central?
Solved
remoteworker93
2 years ago Place Central Discussions
2KViews
0likes
6Comments
Logmein Client no longer installing along side Control Panel
All of a sudden, for some reason, Logmein control panel is installing, but the client is not. Normally they both install at the same time. I have to run a repair on the install and then it installs the control panel. I am not sure why this all of a sudden started. This is what I use to install the Windows Host LMI start-process C:\windows\system32\msiexec.exe -argumentlist "/I C:\temp\$lmilatest /qn /l*v C:\temp\lmiinst.log SETPOWERMANAGEMENT=0 LMIDESCRIPTION=`"$compname - $compmodel - `" COMPANYNAME=[companyname] ACCOUNTEMAIL=[accountemail] DEPLOYID=[deployid] SHOWCLIENT=0 SHOWCONTROLPANEL=0" -wait
Solved
Strobely
2 years ago Place Central Discussions
1.8KViews
0likes
7Comments
Error in SSL handshake connecting with client app - code :1417A0C1:lib(20):func(378):reason(193)
Hi board. We are getting the following screen and error while connecting from Central to a couple of clients behind the same router. Seems like some kind of ssl issue . I've just tried switching the DisableEx regword key to 1 with no luck Log Excerpt : (error marked in red) 2023-01-31 16:06:41.061 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00003D6C - Socket - 173.199.31.9:443 - SSL cipher TLS_AES_256_GCM_SHA384 (256 bits) TLSv1.3 selected. 2023-01-31 16:06:41.061 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00003D6C - Socket - 173.199.31.9:443 - SSL session: NEGOTIATED, timeout is 600 seconds 2023-01-31 16:06:41.061 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00003D6C - Socket - 173.199.31.9:443 - Assigned remote address: 24.232.78.69:57156 2023-01-31 16:06:41.139 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00003D6C - Socket - 24.232.78.69:57156/websvc - HandleSocket request(1): GET 2023-01-31 16:06:41.139 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00003D6C - Session - 24.232.78.69/OL69-78.fibertel.com.ar:SITE-878\Administrator - Serving HTTP/1.1 GET request for /img/itr_menu_button_s.jpg 2023-01-31 16:06:41.139 - Debug - LogMeIn - SITE-878\administrator - 12156 - 0x00003D6C - Session - 24.232.78.69/OL69-78.fibertel.com.ar:SITE-878\Administrator - Request for /img/itr_menu_button_s.jpg returned 200 OK (1092 bytes). 2023-01-31 16:06:41.139 - Debug - LogMeIn - SITE-878\administrator - 12156 - 0x00003D6C - Session - 24.232.78.69/OL69-78.fibertel.com.ar:SITE-878\Administrator - Response for /img/itr_menu_button_s.jpg sent uncompressed (1092 bytes, 198 header) . 2023-01-31 16:06:41.139 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00003D6C - SessionDataReport - An existing SessionDataReport found for session: 926423249. Type:3 Socket:00000000052D49C0 2023-01-31 16:06:41.139 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00003D6C - Socket - 24.232.78.69:57156/http - HandleSocket request finished(1): GET 2023-01-31 16:06:42.186 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00003D6C - Socket - 24.232.78.69:57156/http - HandleSocket request(2): GET 2023-01-31 16:06:42.186 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00003D6C - SessionDataReport - An existing SessionDataReport found for session: 926423249. Type:3 Socket:00000000052D49C0 2023-01-31 16:06:42.186 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00003D6C - Socket - 24.232.78.69:57156/http - HandleSocket request finished(2): GET 2023-01-31 16:06:42.639 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x000031AC - WebSvc - Opening data socket to web service gateway. 2023-01-31 16:06:42.639 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Main - Socket processing thread started. 2023-01-31 16:06:42.639 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Socket - Setup socket for connecting to control.lmi-app14-01.logmein.com on port 443... 2023-01-31 16:06:42.639 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Socket - Resolving address for control.lmi-app14-01.logmein.com... 2023-01-31 16:06:42.639 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Socket - Connecting to control.lmi-app14-01.logmein.com on port 443... 2023-01-31 16:06:42.717 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Socket - 173.199.31.9:443 - Connected (SSL: yes). 2023-01-31 16:06:42.717 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Socket - 173.199.31.9:443 - SSL handshake started. 2023-01-31 16:06:42.795 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Socket - 173.199.31.9:443 - Certificate chain verified, trust status: 0/100. 2023-01-31 16:06:42.795 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Socket - 173.199.31.9:443 - 2: CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3; S#=04:00:00:00:00:01:21:58:53:08:A2; trust 0/10c. 2023-01-31 16:06:42.795 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Socket - 173.199.31.9:443 - 1: CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE; S#=01:EE:5F:22:1D:FC:62:3B:D4:33:3A:85:57; trust 0/102. 2023-01-31 16:06:42.795 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Socket - 173.199.31.9:443 - 0: CN=*.lmi-app14-01.logmein.com, O="LOGMEIN, INC.", L=Boston, S=Massachusetts, C=US; S#=33:DB:C1:3C:15:C9:55:F9:B6:84:B4:DA; trust 0/102. 2023-01-31 16:06:42.795 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Socket - 173.199.31.9:443 - SSL handshake done. 2023-01-31 16:06:42.795 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Socket - 173.199.31.9:443 - SSL cipher TLS_AES_256_GCM_SHA384 (256 bits) TLSv1.3 selected. 2023-01-31 16:06:42.795 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Socket - 173.199.31.9:443 - SSL session: NEGOTIATED, timeout is 600 seconds 2023-01-31 16:06:42.795 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Socket - 173.199.31.9:443 - Assigned remote address: 24.232.78.69:57158 2023-01-31 16:06:42.873 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Socket - 24.232.78.69:57158/websvc - HandleSocket request(1): GET 2023-01-31 16:06:42.873 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Session - 24.232.78.69/OL69-78.fibertel.com.ar:SITE-878\Administrator - Serving HTTP/1.1 GET request for /remctrl.xml?50849 2023-01-31 16:06:42.873 - Debug - LogMeIn - SITE-878\administrator - 12156 - 0x0000439C - ActionRemCtrl - Current saved value of 'HostPrefdDefQuality' is -1 (-1 -> NOT SAVED) 2023-01-31 16:06:42.873 - Debug - LogMeIn - SITE-878\administrator - 12156 - 0x0000439C - ActionRemCtrl - Try to use HD quality as preferred default ... 2023-01-31 16:06:42.873 - Debug - LogMeIn - SITE-878\administrator - 12156 - 0x0000439C - ActionRemCtrl - Use RARC_QUALITY_JPEG color quality instead of HD streaming as preferred default. 2023-01-31 16:06:42.873 - Info - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Session - 24.232.78.69/OL69-78.fibertel.com.ar:SITE-878\Administrator - Request for /remctrl.xml?50849 returned 200 OK (6458 bytes). 2023-01-31 16:06:42.873 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Session - 24.232.78.69/OL69-78.fibertel.com.ar:SITE-878\Administrator - Response for /remctrl.xml?50849 sent uncompressed (6458 bytes, 461 header) . 2023-01-31 16:06:42.873 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - SessionDataReport - An existing SessionDataReport found for session: 926423249. Type:3 Socket:00000000052D68B0 2023-01-31 16:06:42.873 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Socket - 24.232.78.69:57158/http - HandleSocket request finished(1): GET 2023-01-31 16:06:42.873 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Socket - 24.232.78.69:57158/http - Disconnecting (served 1 http requests, 3891 bytes in, 7733 bytes out). 2023-01-31 16:06:43.123 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x0000439C - Socket - 24.232.78.69:57158/http - Closed (rcvd 3915 bytes, sent 7757 bytes). 2023-01-31 16:06:43.358 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00001864 - Socket - 24.232.78.69:57155/http - Error (in RecvInternal): Reached the end of the file. (38) 2023-01-31 16:06:43.358 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00001864 - Socket - 24.232.78.69:57155/http - Closed (rcvd 6926 bytes, sent 1173 bytes). 2023-01-31 16:06:43.358 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00001864 - Socket - 24.232.78.69:57155/http - Disconnecting (served 1 http requests, 6926 bytes in, 1173 bytes out). 2023-01-31 16:06:43.373 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00003D6C - Socket - 24.232.78.69:57156/http - Error (in RecvInternal): Reached the end of the file. (38) 2023-01-31 16:06:43.373 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00003D6C - Socket - 24.232.78.69:57156/http - Closed (rcvd 10257 bytes, sent 2507 bytes). 2023-01-31 16:06:43.373 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00003D6C - Socket - 24.232.78.69:57156/http - Disconnecting (served 2 http requests, 10257 bytes in, 2507 bytes out). 2023-01-31 16:06:44.201 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x000031AC - WebSvc - Opening raw ssl socket to web service gateway (id 23150309). 2023-01-31 16:06:44.201 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Main - Socket processing thread started. 2023-01-31 16:06:44.201 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Socket - Setup socket for connecting to control.lmi-app14-01.logmein.com on port 443... 2023-01-31 16:06:44.201 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Socket - Resolving address for control.lmi-app14-01.logmein.com... 2023-01-31 16:06:44.201 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Socket - Connecting to control.lmi-app14-01.logmein.com on port 443... 2023-01-31 16:06:44.279 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Socket - 173.199.31.9:443 - Connected (SSL: yes). 2023-01-31 16:06:44.279 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Socket - 173.199.31.9:443 - SSL handshake started. 2023-01-31 16:06:44.358 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Socket - 173.199.31.9:443 - Certificate chain verified, trust status: 0/100. 2023-01-31 16:06:44.358 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Socket - 173.199.31.9:443 - 2: CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3; S#=04:00:00:00:00:01:21:58:53:08:A2; trust 0/10c. 2023-01-31 16:06:44.358 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Socket - 173.199.31.9:443 - 1: CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE; S#=01:EE:5F:22:1D:FC:62:3B:D4:33:3A:85:57; trust 0/102. 2023-01-31 16:06:44.358 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Socket - 173.199.31.9:443 - 0: CN=*.lmi-app14-01.logmein.com, O="LOGMEIN, INC.", L=Boston, S=Massachusetts, C=US; S#=33:DB:C1:3C:15:C9:55:F9:B6:84:B4:DA; trust 0/102. 2023-01-31 16:06:44.358 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Socket - 173.199.31.9:443 - SSL handshake done. 2023-01-31 16:06:44.358 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Socket - 173.199.31.9:443 - SSL cipher TLS_AES_256_GCM_SHA384 (256 bits) TLSv1.3 selected. 2023-01-31 16:06:44.358 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Socket - 173.199.31.9:443 - SSL session: NEGOTIATED, timeout is 600 seconds 2023-01-31 16:06:44.358 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Socket - 173.199.31.9:443 - Assigned remote address: 24.232.78.69:57159 2023-01-31 16:06:44.436 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Socket - 24.232.78.69:57159/rawssl - SSL shut down - socket stays connected 2023-01-31 16:06:44.436 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Socket - 24.232.78.69:57159/rawssl - SSL handshake started. 2023-01-31 16:06:44.436 - Error - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Socket - 24.232.78.69:57159/rawssl - SSL error: handshake failure (in write). 2023-01-31 16:06:44.436 - Error - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Socket - 24.232.78.69:57159/rawssl - SSL error: error (in accept). 2023-01-31 16:06:44.436 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Socket - 24.232.78.69:57159/rawssl - Error (in SSL_do_handshake): error:1417A0C1:lib(20):func(378):reason(193) 2023-01-31 16:06:44.436 - Debug - LogMeIn - NT AUTHORITY\SYSTEM - 12156 - 0x00002318 - Socket - 24.232.78.69:57159/rawssl - Closed (rcvd 4121 bytes, sent 771 bytes). Any clues? Thanks a lot
GabrielGz
2 years ago Place Central Discussions
1.2KViews
0likes
0Comments
Mouse issues and Dual Cursors
over the last couple days, i have a few users complain that they have been having issues with their mouse cursor either not showing, disappearing or in some cases showing multiple mouse cursors. Has anyone else experienced similar issues and have a permanent fix for them? I think if i have the users check the box for Lock the keyboard and mouse on the logmein toolbar that seems to help.
jdemodl
2 years ago Place Central Discussions
1.2KViews
0likes
1Comment
Cancel subscription
Hello, We need to stop subscription. We outsourced our entire infrastructure to an external service provider. No one answer at the french number (seems everyone are VERY busy) . How can i contact them? Best
morespped
12 months ago Place Central Discussions
821Views
0likes
4Comments
Were is the documentation for LogMeIn Pro administration ?
Hi, Is there a way to update LogMeIn client on remote PC's using LogMeIn central ? Thanks in advance, François
Solved
fmeehan
2 years ago Place Central Discussions
624Views
0likes
1Comment
Is it possible to create a new plan with failed endpoints on a previous task?
I have a task to upgrade software for 400+ endpoints. The task failed on 100+ endpoints. I found myself creating a new plan and selected all endpoints, then deselected the successful 100+ endpoints. This is very tedious. Is it possible to run a new task on the failed endpoints? Preferably, running a new task for the failed endpoints (or offline endpoints) is ideal. Giving an option to rerun failed tasks found in History would be nice, too.
LMIJoe
2 years ago Place Central Discussions
528Views
1like
0Comments