Port 2395 (lan900-remote, lan900_remote)

IANA assigns port 2395 to lan900-remote, lan900_remote: LAN900 Remote IANA assigned this well-formed service name as a replacement for "lan900_remote"..

Registered (user) port, 1024-49151 TCPUDP

IANA assignment

Service nameProtoDescriptionAssigneeReference

lan900-remote TCP LAN900 Remote IANA assigned this well-formed service name as a replacement for "lan900_remote". Tom Quinlan -

lan900_remote TCP LAN900 Remote
This entry is an alias to "lan900-remote". This entry is now historic, not usable for use with many common service discovery mechanisms. Tom Quinlan -

lan900-remote UDP LAN900 Remote IANA assigned this well-formed service name as a replacement for "lan900_remote". Tom Quinlan -

lan900_remote UDP LAN900 Remote
This entry is an alias to "lan900-remote". This entry is now historic, not usable for use with many common service discovery mechanisms. Tom Quinlan -

Check what is listening on port 2395

Linux: is anything listening on TCP 2395?

sudo ss -tlnp 'sport = :2395'

Linux: UDP 2395

sudo ss -ulnp 'sport = :2395'

Linux / macOS: which process owns the port

sudo lsof -nP -i :2395

Older Linux / BSD (net-tools)

sudo netstat -tlnp | grep ':2395 '

Windows (Command Prompt)

netstat -ano | findstr :2395

Windows (PowerShell)

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

Test it from outside

From another machine

nc -vz -w 5 HOST 2395

From Windows

Test-NetConnection HOST -Port 2395

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

nc -vzu -w 5 HOST 2395

Block port 2395 in the firewall

ufw

sudo ufw deny 2395/tcp

iptables

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

nftables

sudo nft add rule inet filter input tcp dport 2395 drop

Windows Firewall

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

ufw

sudo ufw deny 2395/udp