15-09-2020, 03:04 PM,
|
|
G4UGB
Member
|
Posts: 72
Threads: 20
Joined: Feb 2015
Reputation:
0
|
|
Telnet DX Cluster problems.
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
|
|
17-09-2020, 01:21 PM,
|
|
G4UGB
Member
|
Posts: 72
Threads: 20
Joined: Feb 2015
Reputation:
0
|
|
RE: Telnet DX Cluster problems.
Hello Jordi,
Thank you - I changed the address to what you said but - still get the error message
;Disconnected (185.73.168.155:23/ Socket Error #10060 Connection timed out'.
But like I mentioned in the last message - SWL is excluded in both my Windows Defender Firewall and in my Malwarebytes anti-virus software. I seem to be connected to GB7AAA however and the DX Messages window is populating. So no change - to the problem - but thank you again for the reply.
Kind Regards,
Richard G4UGB
|
|
18-09-2020, 06:39 PM,
|
|
dk4rh
Junior Member
|
Posts: 48
Threads: 8
Joined: May 2020
Reputation:
0
|
|
RE: Telnet DX Cluster problems.
Hi Richard,
I'm a little bit interested in ... saw the login and that port 23 is used.
Have done the configuration (only parameter adapted for my and my location). Is running well.
What makes my wonder - the host seems to use another Dialin to the internet in the result it get an IP-Adress in another range.
currently it has 80.34.3.9 (can be checked with ping ea1dx.lynxdxg.com)
Think you could check, if your error-message is from the IP-Address, which you get via the ping.
Maybe for another host 'automatic starting' is active ?
73 de Roland, DK4RH
vy 73 - DK4RH, Roland
|
|
18-09-2020, 11:23 PM,
|
|
G4UGB
Member
|
Posts: 72
Threads: 20
Joined: Feb 2015
Reputation:
0
|
|
RE: Telnet DX Cluster problems.
Hello Jordi - (and thanks to Roland DK4RH for the comments),
I deleted everything after the $$$$ in the script that you suggested and bingo - it connected immediately. I haven't a clue really - as to why that should be because it always connected instantly with those script additions previously. Anyway - it is now working and instant population of the DX Messages window again. I wasn't even aware that I had somehow - added those extra scripting commands to be honest I thought they were inserted by SWL.
BIG thank you again Jordi !!!
73 de Richard G4UGB
|
|
|