Date
1 - 8 of 8
SDR Server returning status: unknown
|
radiodx3@...
Hello all. I finally have some time to work on this today, but short. I'll be unavailable starting tomorrow for a few weeks. I tried starting the server and it starts, but I get the "on-air status: unknown" message. The Network ports 50101 and 5199 are enabled, this occurs with the Windows Firewall on or off. I am on Windows 11, the logfile is attached. I triple-checked the port forwarding addresses just to be sure. Any help is appreciated
Brian - W8GTX |
|
|
|
Brian, the clue to your problem is the entry in the log of "Socket Bind failure." This indicates that SDR Server cannot open (50101) the port for listening. This is most often caused because the port is already in use by another program. I would check to ensure there is not already an instance of the server running. Open up the Windows task manager and look at both processes and services to see if it is running. The other cause is that you are not running the SDR Server Manager as admin, a normal user cannot open up a TCP socket.
-- Dennis KA6FUB |
|
|
|
radiodx3@...
Dennis, thank you, that seems to have been it, for the most part. I went into Windows Firewall and forced the port open for both inbound and outbound rules, and now it is working. Dennis, thanks again, your assistance got me thinking. Now, if it goes down after tomorrow, well I'll be laid up for some time. I hope it stays, I want to listen to the radio on my bedside laptop :)
|
|
|
|
radiodx3@...
BTW, you got me thinking when you mentioned 50101 is not listening. Without knowing that, I would have been doing circles ;)
|
|
|
|
Oddly enough I had the same issue, I wonder what's listening on 50101?
Must make the error more obvious.
From: main@SDR-Radio.groups.io <main@SDR-Radio.groups.io> on behalf of radiodx3 via groups.io <radiodx3@...>
Sent: 02 December 2022 01:08 To: main@SDR-Radio.groups.io <main@SDR-Radio.groups.io> Subject: Re: [SDR-Radio] SDR Server returning status: unknown BTW, you got me thinking when you mentioned 50101 is not listening. Without knowing that, I would have been doing circles ;)
-- - + - + -
Please use https://forum.sdr-radio.com:4499/ when posting questions or problems. |
|
|
|
Simon, from an elevated command prompt, use the "netstat -o" command to show the active connections with the PID that is associated with it.
-- Dennis KA6FUB |
|
|
|
Sometime, if a previous instance of a program was evicted or crashed, the ports it was using can remain allocated...
For me, the easiest general fix is to reboot Windows. If the problem persists after a reboot, you can look for the program that's actually allocating the port. (Others here have pointed to the tools to do that.)
73
On 12/1/22 23:47, Simon Brown wrote:
|
|
|
|
jdow
Netstat is a way to look for open ports. Of course, a codebase
search for 50101 would show it up if your code is doing it.
{^_^}
On 20221202 10:03:51, Paul - AI7JR
wrote:
|
|
|