Famous Desktop Manager 10060 Socket Error

[caveman]

Hi all,

I'm tearing my hair out trying to fix this problem - can you offer any advice?

I've been using the GDM on XP SP3 for a day without any problems, but after installing a Windows Automatic Update today I'm getting the following message when I try to start the GDM:

"Socket Error # 10060 Connection timed out."

I've checked the forums as this seems to be quite a common problem. In response to the common advice, I deleted the Gixen .dll files:

libssl32.dll
libeay32.dll
ssleay32.dll

... and then I installed the latest OpenSSL-Win32 (v1.0.1 14 Mar 2012)

GDM let me enter just 1 snipe and then froze (I checked the web UI and the snipe was successfully scheduled). Since then I've been getting the same #10060 error and cannot access the program. A few times

Furthermore, GDM stays active in my Windows task manager processes even after being closed (it uses about 18MB of memory). I don't know if this is related to the problem.

The GDM is what sets Gixen apart from the other web snipers in my opinion, so it's a real shame to lose this functionality!

Any advice from you Gixen veterans?

Thanks in advance.

[mario]

I am not sure why installing SP3 would cause this, in fact I use XP to compile and test GDM. Since you already tried installing openSSL from scratch, I honestly have no idea what else to recommend.

[caveman]

Thanks Mario. It wasn't SP3, it was a regular (weekly-ish) XP automatic update.

It gets stranger... it's all working perfectly again now!

I'll keep an eye on it.

[jd737stephanie]

i upgraded to win7 64 bit. got socket 10060 error. tried installing open ssl. got frustrated and confused. still got error. changed compatibility to xp sp3. no more error. cool. although i must say that it now takes a VERY long time to connect and refresh stuff. but it works.

[Gixen]

[skysentinel]

I am having the same problem with the socket error #10060 time out, but I am using Windows 7. I can't imagine anyone using the desktop manager and Win 7 NOT having the same problem as me. Is there a reason why this problem can't be resolved?

[skysentinel]

[garfieldgirl]

I have seen several folks online with this issue, so I thought I would chime in here with the all too simple fix. I'm unsure what the actual cause is; however, something is obviously different in functionality on Windows versions greater than XP SP2. It's odd though, it doesn't happen to everyone.

I tested this on several machines, (that luckily were running Vista, W7, W8.1, and W10, respectively) and it worked on all of them. I had everyone install by creating a new folder in C: "Program Files (x86)" for 64 bit, and "Program Files," on 32 bit.

Make sure Windows firewall isn't blocking outgoing traffic for "GixenDesktopManager.exe," and likewise, make sure your security software isn't blocking it as well.

For the last step, you need to enable "Compatibility Wizard," and choose "Windows XP SP2." You may be able to select "Windows XP SP3," however, some were unable to get the app working on SP3, and there is no functional benefit to choosing it. Therefore, for simplicity, choose "Windows XP SP2." From what I can tell, there is no need to update the OpenSSL DLLs that are packaged with the app. When the app is in 32 bit, XP SP2 mode, those DLLs are just fine.

If you are unfamiliar with compatibility wizard, it is easy to find. Simply right click the executable you extracted, choose properties, and select the compatibility tab. From there, select "Windows XP SP2," and click apply to save your selection.

You may want to right click the application and choose "create shortcut." It should tell you that you cannot create a shortcut here, "would you like to place a shortcut on the desktop instead?" Select yes to save a shortcut to the desktop.

From there, you can launch the app from the desktop, or by directly clicking the executable.

I hope this helps anyone with the same issue. Take care.