Skip to content

Cannot connect to rtl_tcp on local network #100

Description

@Fairlight60

I have two Windows 10 machines on a local network, a tablet running Android 10, an RTL-SDR V3, RF Analyzer 2.0 full version, and the latest Osmocom binaries (64-bit from June 28, 2026).

When I run rtl_tcp on one Windows machine, the other Windows machine can access it through SDR Console v3.3 without problem, I can connect to it using SDR Touch on my tablet, but not using RF Analyzer, I always get the message "Couldn't connect to rtl_tcp instance". The connection does seem to initiate according to the rtl_tcp logs (as you can see with the line "client accepted") but it stops almost instantly :

E:\Radio\rtl_sdr>rtl_tcp -a 192.168.0.10 -p 1234
Found 1 device(s):
  0:  RTL-SDR Blog, RTL-SDR Blog V3, SN: 4

Using device 0: Generic RTL2832U OEM
Found Rafael Micro R820T tuner
[R82XX] PLL not locked!
Tuned to 100000000 Hz.
listening...
Use the device argument 'rtl_tcp=192.168.0.10:1234' in OsmoSDR (gr-osmosdr) source
to receive samples in GRC and control rtl_tcp parameters (frequency, gain, ...).
client accepted! 192.168.0.12 55204
comm recv bye
Signal caught, exiting!
worker cond timeout
Signal caught, exiting!
all threads dead..
listening...

Of course I made sure that the IP address and port are correct and the firewall is not an issue, as I said it works correctly with SDR Touch. I also tried reading the RF Analyzer logs but they're a little overwhelming and I didn't find an obvious reference to the problem. This issue also looks similar to this other one.

Please help, thank you!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions