smartcat tcp port connection refused on 3 out of 8 tcp ports 1.10.16

  • 1
  • Problem
  • Updated 1 year ago
I'll start with the good news: I havent had a rig (6700) crash on 1.10.16 in 5 days (since doing to 2 button reset, but as has been shown thats not a cure, the problem will be back).

However this morning I fired things up and found one of my 4 wsjtx sessions had a rig issue. Seems smartcat is giving connection refused on port 60004 (I map slices A..H to 60000..7); Other slices have issues too; ports 60000, 60001 dont respond.
Restart smartcat didnt fix it..restart smartsdr didnt fix it...
I'm sure a win10 reboot will "fix it";

however smartcat shows the tcp ports all blue, as in good to go...
If I select the smartcat entry for tcp port 60004 (slice E) and do log, it shows the correct frequency, and changing freq and reexecuting the cmd it changes as expected.
So it appears smartcat can talk to the rig but isnt listening on 60004, or is having a problem opening port 60004. 

netstat -an  shows no listeners on ports 60000, 60001, 60004
  TCP    0.0.0.0:52002          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:60002          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:60003          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:60005          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:60006          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:60007          0.0.0.0:0              LISTENING

Shouldnt smartcat output a warning if it cant open the specified port to listen?

running win10 1607, 14393.1198 
Photo of NM1W

NM1W

  • 130 Posts
  • 23 Reply Likes

Posted 1 year ago

  • 1

Be the first to post a reply!