Robin/Phil
To show listening sockets (aka servers) on a Linux terminal;
sudo lsof -i -P -n | grep LISTEN
or
sudo netstat -tulpn | grep LISTEN
of course also possible to check a particular port
In Windows I found;
Start menu ¡ú All Programs ¡ú Accessories ¡ú System Tools ¡ú Resource
Monitor
or run resmon.exe,
or from TaskManager ¡ú Performance tab.
and expand the Network | Listening Ports items list
This is where you would see rigctld's 4532 and flrig's 12345.
There are of course methods that can block listening ports being
accessed despite them being visible as above. Firewalls can do
that, but not usually on the same host.
Cheers Bob VK2YQA
On 14/9/24 21:42, G8DQX wrote:
toggle quoted message
Show quoted text
Phil,
if there's no server running that's listening on port XXXX,
then the OS has nowhere to forward any connection request to.
That triggers the ¡°actively refused¡± response from the OS.
Anthropomorphically, It's as if you've gone to some street
address and asked to speak to someone who doesn't live there.
For security reasons, the reply is usually exactly the same
whether the required server/d?mon is not installed, is not
running, or the server/d?mon is running, but the request has
been blocked for some reason.
73,
Robin, G8DQX
On 14/09/2024 10:29, Philip Rose,
GM3ZZA via groups.io wrote:
Thanks Robin,
So it's not the server app that's "actively
refused" the request but the OS the app is running on. I'll
bear that in mind when I next drill down into my remote
operating.
Phil GM3ZZA
