InterpretIT
Active Contributor
Joined 13 years ago
User Profile
User Widgets
Contributions
File Manager takes a long time to make a connection
Within the last 3 months, File Manager is taking a long time to connect before I can use the feature. In some cases, it takes 4-7 minutes. I find that I am clicking on File Manager as soon as a session connects, in case I need to use it. If I have had File Manager open in the same session, it does not decrease the time it initially took to start. I would guess the average time now is 90 seconds, where it used to be instantaneous. File Manager Client Connecting... control.app07-02.logmeinrescue.com (111.221.57.131), port: 443 Key exchange: Elliptic Curve Diffie-Hellman, 2048 bits Data encryption: ECDHE-RSA-AES256-GCM-SHA384, 256 bits Authenticating... Connect successful. P2P Negotiating UDP connection through MatchMaker... P2P MatchMaker: UDP socket invalid Handoff connection active (2093). File Manager Client Connecting... control.app07-01.logmeinrescue.com (111.221.57.130), port: 443 Key exchange: Elliptic Curve Diffie-Hellman, 2048 bits Data encryption: ECDHE-RSA-AES256-GCM-SHA384, 256 bits Authenticating... Connect successful. P2P Negotiating UDP connection through MatchMaker... P2P MatchMaker: UDP socket invalid P2P MatchMaker: Opening direct socket failed P2P Negotiating UDP connection through MatchMaker... P2P MatchMaker: UDP socket invalid Handoff connection active (17406).1.3KViews0likes1CommentMacOS: A keychain cannot be found to store....
Hi Lately, I've been having a lot of issues with LMI rescue unattended access and MacOS. I am receiving a window stating a "Keychain not Found" with the error: A keychain cannot be found to store "1:424688513186:ios:HexidecimalNumber_FIRAPP_DEFAULT" This occurs on Mac's that have previously had unattended access installed, on new installs and on clean installs of 10.12, 10.13, 10.14, 10.15 & 11.4. Resetting the keychain to default does not resolve the issue. Clicking on the cancel button results in another window being shown with the same error. Clicking on cancel again closes both the windows. I can log in as normal by either closing the error windows, or ignoring them.Solved53KViews0likes4Comments