Hi,
Cannot figure out what is wrong connecting to DX.K3LR.COM:23
Had everything working fine under Catalina but upgraded to a newer M1 Mac Mini computer with Big Sur, but something is not allowing the cluster to connect. I tried about 4 other clusters and none work. Seems as if the computer is not allowing incoming connections and a port needs opened.....not very literate on this. Any suggestions?
Thank you
Bob
More details...
1. Had a 2020 Mac mini with Catalina do the same thing initially but mystery resolved and always would connect
2. Decided to repurpose that computer and got a new 2021 M1 Mac Mini with Big Sur...downloaded new Rum software...installed.....had normal issues loading logs, aligning the correct checkboxes, UDP ports for WSJT.....all fine
3. the only Cluster that will connect is my favorite K3LR......but it appears to time out...see 2 screen shots....no other cluster will connect or even respond - none that I tried
My guess is that a port needs opened for a return connection....meaning that once a connect command is sent, that's the only command that goes out and either the computer or program won't respond the the cluster request for a connection.....I did try a few things under system preferences/security & privacy/privacy and place rum log in a few places and none thing worked....did add Rumlog to accessibility......maybe wrong area.....the Firewall is turned off by default...tried multiple restarts and shutdowns and nothing works.....i'm also guessing this is something typical since this is the second occurrence on 2 different computers....hopefully this is my error.
I also understand that telnet is no longer part of Big Sur and wonder if that needs downloaded and installed....
Thanks Tom, BTW great program and thanks for all the work on designing it.
Hi Tom, you are exactly correct. I did this before with no success but after your last email, I went back and added K1TTT and W3LPL.....interesting that both connected......I then disconnected from both and tried K3LR.....it went into countdown mode but connected rather quickly.....the K3LR server must have hung up with my call for some reason...maybe I did not disconnect properly the last time, unsure....the other servers are connected between each other and K3LR may have recognized it then allowed me to connect....strange.....but it works fine.
Again, thanks for responding so quick and having such a great program....thanks to one an all for all the hard work
