Thanks for testing, but this is not exactly the problematic scenario. When I simply stop LMS and Squeeze Ctrl and then start Squeeze Ctrl and finally start LMS it also connects in my system. The problem happens if
1. the computer running LMS was completely shutdown and is woken up by Squeeze Ctrol sending a WOL request AND
2. Squeeze Ctrl was not running before or was really terminated. That means the device running Squeeze Ctrl should be restarted for testing when the server runinng LMS is shutdown.
This is the typical scenario for me in the morning since both, the computer running LMS and the table running Squeeze Ctrl (and SB Player) are both turned off during night.
In this scenario when starting Squeeze Ctrl it sends the WOL request and the computer running LMS as well as LMS are started but Squeeze Ctrl never connects. Only when I click on "connect" the connection is established at once.
I have now written a script (using Automagic) which, when started, checks if LMS is running (by sending a HTTP request) and if it is running it simply starts Squeeze Ctrl. If LMS is not running the script sends a WOL request, waits until LMS is running and then starts Squeeze Ctrl. In this way the connection is always successfully established.
So to me it still looks like Squeeze Ctrl simply does not try to connect to LMS after having sent a WOL request. Either it does not try at all or at least not long enoght in this senario. Can you also test the above scenario to look if there is a problem in connection with a connection after a WOL request? Thereby, the above second condition seems to be important. I have the impression that the server timeout set in Squeeze Ctrl is only used when Squeez Ctrl tries to REconnect to a previously connected server to which connection was lost. However, if Sqzeeze Ctrl tries to connect the first time after a restart of the device running Squeeze Ctrl it seems that it tries to connect only very shortly (although I have set the server timeout to 30 seconds). And if it cannot connect immediately (which is the case if the server is still booting after a WOL request) it gives up.
If you have WOL not configured you could at least test to completely shutdown the computer running LMS and the device running Squeeze Ctrl, then to start this device, then to start SqueezCtrl and while Squeeze Ctrl tries to connect to start the computer running LMS. In my system Squeeze Ctrl only tries to connect for about 2 seconds and then gives up. This means that the connection is not established since it takes about 20 seconds for the server to boot and to start LMS.
Thanks a lot for your efforts.