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
Solved
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 com...
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.
Hi slimjim1
We are researching this issue currently and would appreciate your help. In order to continue our investigation of this issue, we require your assistance in creating a test on a host computer currently affected. I have attached 2 registries for this test and the instructions below.
*NOTE* This is not a fix yet, however, it is a test that will help us and our team properly address the root cause of the disconnection with our servers.
- Create a new text file in Notepad or similar and paste the following text into it:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\LogMeIn\V5\WebSvc]
"UseGateway"="control.lmi-app12-20.logmein.com" -
Save the file as Gatewaychange.reg
- Right-click the file and select Merge
- Restart LogMeIn Services
- Please activate the Debug level logs on your control panel:
LogMeIn Control Panel > Options > Preferences >Advanced > Check the box "enable debug level" - After restarting the LogMeIn services, please test a connection. If a connection continues to have connectivity issues please retrieve the logs on the path : C:\Users\All Users\LogMeIn\ > Attach logmein.log
- After catching the logs, please create a new text file with the following:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\LogMeIn\V5\WebSvc]
"UseGateway"=-
and save it as Gatewaychangereset.reg - Run Gatewaychangereset.reg
- Restart logmein services. (This will revert the changes made before)
- If by any chance by changing the gateway with the first registry on Step 1. You may use it as a temporary fix for a connection option.
This test will help us continue to work on our investigation and may help as a temporary fix. We appreciate your patience and help with this issue.
To send us the log files please click on my community nickname and you should see an option in the upper right to Send a Message.
I attempted to do this, but the LogMeIn service will not start.
So I can't set log outputs, and it isn't generating anything for the logs.
Thank you, I will inform the team.
Please create a new text file with the following text and save it as Gatewaychangereset.reg:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\LogMeIn\V5\WebSvc]
"UseGateway"=-
Run Gatewaychangereset.reg and restart the LogMeIn service.
