No IANA assignment exists here; a listener on 49159 is typically a Windows RPC service that took the next free dynamic port.
The IANA registry stops at 49151. Everything from 49152 up is Dynamic/Private space that RFC 6335 explicitly excludes from assignment, so no service owns 49159 and none can. Windows allocates RPC server endpoints from this range in ascending order as services start, which is why domain controllers and file servers frequently show a cluster of open ports in the low 49150s and 49160s. Outside Windows the same number turns up as a client-side source port for an outbound connection, in which case nothing is listening at all.
Do not expose
An unidentified high-port listener should not be exposed until you know which RPC interface answers on it; enumerate it from port 135 first.
$ sudo lsof -nP -iTCP:49159 -sTCP:LISTENSeen this on your network? Beige Box scans your Wi-Fi and shows every open port on every device — and its Ports tool links straight back here.
Get Beige Box →also available as JSON · Markdown
Corrections or a missing port? Reply @rimrocksystems.