The GoTo Community is currently experiencing some technical issues affecting new posts and comments. We are actively working with our service provider and apologize for the frustration.
Forum Discussion
Khaos_Storm
4 years agoActive Contributor
Cannot Connect to Host -1st attempt drops -2nd attempt says already connected
I am having an issue with LogMeIn, that seems to be hitting more and more of my machines.
I have 87 computers at 5 sites.
All 87 have been working through LogMeIn, and then last week we had one computer go into this new funky mode, and failed to work. I swapped out that PC, and the PC I swapped it with then had the same problem.
I have a 3rd machine at another site, that also just started doing it.
(The other 84 machines are still working just fine, including all the machines at the same sites as the non-working ones)
The problem is this:
When the first attempt to connect is made, it hangs after authenticating, and the drops. The error message says the connection was lost.
The second attempt to connect hangs in the same place, but then comes back saying that the host is already in a session (with the last IP/user that attempted to connect the first time)
I have attempted to use the reboot options to restart the logmein service, but that doesn't seem to work.
I can use that same menu to push a reboot, and that will work successfully. (I can also push the reboot through Windows from Active Directory, or with Powershell). When the machine reboots, the first attempt to connect is cleared, and attempting to connect after the reboot puts you back at receiving the "Lost connection" error, and back in line to receive "already connected" if you try again from there.
Booting the computer into SafeMode with Networking and LogMeIn, does seem to make it work. But then it is in safemode, and not very usable.
Any ideas on how to troubleshoot this, before I start seeing it on even more machines?
JLSantos I managed to figure out the issue myself. After uninstalling Citrix Workspace and rebooting, Logmein magically worked again. Even the inability to stop/restart the service was fixed.
I found it from looking into graphics drivers as the only thing different about this PC was that it had an old dedicated graphics card. I noticed in device manager that Citrix had it's own entry under display adapters listed as "citrix indirect display adapter". I remember Logmein used to use it's own mirror driver that showed up in Device Manager so I took a wild guess that it was interfering with whatever Logmein does to tap into graphics drivers. Perhaps it's seeing that device as a display out and tries to get a feed from it only to fail since it isn't a real display device. This isn't a solution because I still need Citrix Workspace but this should point Logmein in the right direction. Going to reinstall Citrix Workspace and see if I can replicate it.
Update: Reinstalling Citrix workspace didn't bring back the issue. But it also didn't install the "citrix indirect display adapter" that I saw earlier. Worth noting that I had manually uninstalled that driver within Device Manager before removing Citrix Workspace so that driver specifically might be the cause of the issue.
Update 2: Seems to be related to Citrix Screen Casting which is part of Citrix Workspace.
23 Replies
- jpedersonVAC4 years agoActive Contributor
I had the same issue and uninstalling Citrix Workspace fixed mine as well.
- dnguyen14 years agoActive Contributor
Thank you slimjim1 !!! I just uninstalled Citrix Workspace and am now able to connect via LogMeIn! Thank you so much for letting us know what worked for you since LogMeIn themselves stopped updating us. If anything changes on my end, I will post in the thread.
Update: I reinstalled Citrix Workspace and am still able to connect via LogMeIn
- slimjim14 years agoActive Contributor
JLSantos I managed to figure out the issue myself. After uninstalling Citrix Workspace and rebooting, Logmein magically worked again. Even the inability to stop/restart the service was fixed.
I found it from looking into graphics drivers as the only thing different about this PC was that it had an old dedicated graphics card. I noticed in device manager that Citrix had it's own entry under display adapters listed as "citrix indirect display adapter". I remember Logmein used to use it's own mirror driver that showed up in Device Manager so I took a wild guess that it was interfering with whatever Logmein does to tap into graphics drivers. Perhaps it's seeing that device as a display out and tries to get a feed from it only to fail since it isn't a real display device. This isn't a solution because I still need Citrix Workspace but this should point Logmein in the right direction. Going to reinstall Citrix Workspace and see if I can replicate it.
Update: Reinstalling Citrix workspace didn't bring back the issue. But it also didn't install the "citrix indirect display adapter" that I saw earlier. Worth noting that I had manually uninstalled that driver within Device Manager before removing Citrix Workspace so that driver specifically might be the cause of the issue.
Update 2: Seems to be related to Citrix Screen Casting which is part of Citrix Workspace.
- slimjim14 years agoActive Contributor
Support thought that it was a Root Certificate issue but their own links given to support didn't work to the certs they were told to try. The support rep said that they think it might be related to the latest SSU with windows 10, but it's impossible to just uninstall a SSU to test it..which all of my other machines have installed with no issue. Said they'd reach out if there we're any updates. That was 2 weeks ago.
- JLSantos4 years agoVisitor
Same issue here since May 2022. I tried every suggestion from LMI and even they connected to 1 machine for hours and didn't fix the issue.
More and more machines have the issue every day or week.
- slimjim14 years agoActive Contributor
I even temporarily disabled the Firewall for the network this machine is on (even though the 20 others on the same network are unaffected) and removed all AV on this machine (even though it's LMI's AV), and disabled Windows Defenders Firewall..to no avail. Whatever is causing this, It isn't a firewall and it clearly isn't a one off based on this thread.
- dnguyen14 years agoActive Contributor
I agree. Every rep who reached out to address my ticket had me uninstall/reinstall the program several times & then said it was the firewall which it is not. All other machines at our firm have not had any issue. I was hoping the community discussion board would get better results
- Khaos_Storm4 years agoActive Contributor
Same. Support hasn't really been helpful.
They just keep repeating "It's your firewall" and "How are you since we last talked?"
They've asked for logs several times (and I've provided them), and several times they have come back with these same responses.
It has been over a month since I opened my ticket, and this still isn't fixed. Still at "Must be your firewall" while the other 78 machines connect fine through the same firewall.
-Currently test-driving Splashtop as our replacement.
- dnguyen14 years agoActive Contributor
Please provide us with updates or if there is a temporary fix we can use. I had uninstalled and re-installed LogMeIn several times at the start of this and its going on weeks now without a solution. I am still unable to connect to the host computer even though the control panel says it is accessible. The only way I can restart LogMeIn is by restarting my computer. Otherwise, it just endlessly spins. As mentioned by another user, I can also connect to other machines from the affected machine, I just cannot connect to this specific one.
- slimjim14 years agoActive Contributor
GlennD I just sent 2 PMs with my Logs from attempting to connect since the log was too long to fit into the 60,000 character limit. If there's a way to upload straight ".log" files on this forum through PMs it also eludes me. My affected Machine also acts exactly as described by Orestes85.