Still inside the dynamic range; the deeper into it a host goes, the more RPC services it is running.
49155 carries no assignment — RFC 6335 forbids one in this range — and shows up mainly on Windows hosts that have allocated several RPC endpoints at boot. Nmap sees it open on about 0.6% of scanned hosts, a little less often than 49152-49154, which tracks how many services a typical machine registers. macOS and other BSD-derived systems start their ephemeral allocation at 49152 too, so outbound connections from those hosts also occupy this number.
Do not expose
An RPC endpoint or an ephemeral client socket — neither is something to publish; block the range inbound at the edge.
$ nmap -sV -Pn -p 49155 TARGETSeen 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.