15-09-2020, 03:04 PM
Hello Jordi,
Could you advise please - since the last upgrade I am unable to raise the EA1DX-5 cluster and it gives me a 'Timed Out Socket Error 10060'. I read a previous thread on here where you mentioned a fix but I have added SWL exclusions to both Windows Defender Firewall and my Malwarebytes Anti-Virus program to no avail.
If I go into 'Active Servers' and remove EA1DX-5 'Stop All Servers' it disappears from the Active Server window and also removes it from the Active Server Window completely. If I then check the list of 'Available Servers - it is not checked. I then check GB7AAA ((for instance) but it also comes back with Timed out Socket 10060 error. Seems like I cannot connect to any Cluster server - but yet my DX Messages list slowly (SLOWLY) partially fills up over time.
Next time I try it - it starts trying to connect to EA1DX-5 again (with the same Socket 10060 error) - yet that is not ticked as an available server but - it appears back in the Active Server window as if somewhere in SWL it is programmed to automatically connect to this server ??
Any tips or advice how I might cure this issue ??
Kind Regards,
Richard G4UGB
Could you advise please - since the last upgrade I am unable to raise the EA1DX-5 cluster and it gives me a 'Timed Out Socket Error 10060'. I read a previous thread on here where you mentioned a fix but I have added SWL exclusions to both Windows Defender Firewall and my Malwarebytes Anti-Virus program to no avail.
If I go into 'Active Servers' and remove EA1DX-5 'Stop All Servers' it disappears from the Active Server window and also removes it from the Active Server Window completely. If I then check the list of 'Available Servers - it is not checked. I then check GB7AAA ((for instance) but it also comes back with Timed out Socket 10060 error. Seems like I cannot connect to any Cluster server - but yet my DX Messages list slowly (SLOWLY) partially fills up over time.
Next time I try it - it starts trying to connect to EA1DX-5 again (with the same Socket 10060 error) - yet that is not ticked as an available server but - it appears back in the Active Server window as if somewhere in SWL it is programmed to automatically connect to this server ??
Any tips or advice how I might cure this issue ??
Kind Regards,
Richard G4UGB