Port 5145 (rmonitor-secure, rmonitor_secure)

IANA assigns port 5145 to rmonitor-secure, rmonitor_secure: RMONITOR SECURE IANA assigned this well-formed service name as a replacement for "rmonitor_secure"..

Registered (user) port, 1024-49151 TCPUDP

IANA assignment

Service nameProtoDescriptionAssigneeReference

rmonitor-secure TCP RMONITOR SECURE IANA assigned this well-formed service name as a replacement for "rmonitor_secure". Kory Hamzeh -

rmonitor_secure TCP RMONITOR SECURE
This entry is an alias to "rmonitor-secure". This entry is now historic, not usable for use with many common service discovery mechanisms. Kory Hamzeh -

rmonitor-secure UDP RMONITOR SECURE IANA assigned this well-formed service name as a replacement for "rmonitor_secure". Kory Hamzeh -

rmonitor_secure UDP RMONITOR SECURE
This entry is an alias to "rmonitor-secure". This entry is now historic, not usable for use with many common service discovery mechanisms. Kory Hamzeh -

Check what is listening on port 5145

Linux: is anything listening on TCP 5145?

sudo ss -tlnp 'sport = :5145'

Linux: UDP 5145

sudo ss -ulnp 'sport = :5145'

Linux / macOS: which process owns the port

sudo lsof -nP -i :5145

Older Linux / BSD (net-tools)

sudo netstat -tlnp | grep ':5145 '

Windows (Command Prompt)

netstat -ano | findstr :5145

Windows (PowerShell)

Get-NetTCPConnection -LocalPort 5145 -State Listen | Select LocalAddress,OwningProcess

Test it from outside

From another machine

nc -vz -w 5 HOST 5145

From Windows

Test-NetConnection HOST -Port 5145

UDP probe (no reply does not prove it is closed)

nc -vzu -w 5 HOST 5145

Block port 5145 in the firewall

ufw

sudo ufw deny 5145/tcp

iptables

sudo iptables -A INPUT -p tcp --dport 5145 -j DROP

nftables

sudo nft add rule inet filter input tcp dport 5145 drop

Windows Firewall

New-NetFirewallRule -DisplayName 'Block TCP 5145' -Direction Inbound -Protocol TCP -LocalPort 5145 -Action Block

ufw

sudo ufw deny 5145/udp