Port 8207LM SServer

LM SServer is the registered service name for TCP and UDP port 8207.

transport: tcp · udp
in transit: cleartext
assignment: official
risk: 1/10
lookups: 0

Technical Details

what runs on :8207

LM SServer is registered on port :8207 over tcp and udp to Chris Flynn. We don't have a technical write-up for it beyond the IANA registry entry.

In nmap's internet-wide scan data this port is found open rarely. What's listening is often not the registered service, so check before you assume.

find what's listening on :8207

this machine

# linux
sudo ss -tulpn 'sport = :8207'

# macos / bsd
sudo lsof -nP -i :8207

# windows (then: tasklist /FI "PID eq <pid>")
netstat -ano | findstr :8207

another host

nmap -sV -p T:8207 <host>
sudo nmap -sU -sV -p U:8207 <host>

run it? the handshake, the implementations you meet in the wild and the flags that matter come from the engineers who do.

add technical details

Security Information

exposure of :8207

risk score

1/ 10safe

routine exposure. this port is rarely the way in on its own — keep it patched and logged and move on.

in transit

cleartext

credentials and payloads are readable by anyone on path

assignment

official

registered with iana for this service — scanners fingerprint it by number

reachable over

tcp · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

no security notes recorded for :8207 yet

known exploits, hardening advice, what a compromise looks like — suggest an edit if you know its exposure.

Record

iana registry entry

port: :8207
service: LM SServer
transport: TCPUDP
encryption: cleartext
assignment: iana registered
risk: 1/10safe
category: uncategorised
usage: Port 8207 is assigned for the LM SServer service over TCP and UDP. The assignment is registered to Chris Flynn; no product, protocol, or deployment details are recorded.
lookups: 0rank 993
added: 2026-08-22
updated: 2026-08-22
references: IANA service name registry — port 8207

Something wrong?

This record is maintained by the engineers who use port 8207. Every field on it is editable — change what's wrong, say how you know, and a reviewer publishes it, usually within a minute. Last touched 2026-08-22.

01edit any field on a page of its own
02a model checks it for accuracy and spam
03clean and confident goes live immediately

edit this record →back to the registry

Related Ports

browse categories →

ports registered around :8207, by lookups.

port	service	proto	category	risk	views
:8243	Apache Synapse HTTPS Listener	TCPUDPtls	Web Services	caution	22.3k
:8200	GoToMyPC	TCP	Remote Access	caution	9.9k
:8194	Sophos RMS	TCP	Security	caution	8.3k
:8222	VMware Server UI (Insecure)		Web Services	caution	8.2k
:8192	Sophos RMS	TCP	Security	caution	7.4k
:8193	Sophos RMS	TCP	Security	caution	7.0k
:8201	TRIVNET	TCPUDP	—	safe	0
:8182	VMware Fault Domain Manager	TCPUDPtls	System	caution	0

risk mix of the 8 listed

safe13%
caution88%

2 of 8 encrypted

Port :8207LM SServer

Technical Details

Security Information

Related Ports

Port 8207LM SServer