Third in the Windows RPC pool — and the number can move between reboots.
Like the rest of 49152-65535, 49154 is a dynamic port that IANA never assigns; on Windows it is usually the third RPC endpoint allocated after boot. Because allocation follows service start order, the mapping is not stable, which is exactly why firewall rules pinned to individual numbers in this range break. Microsoft's answer is to allow the whole range internally or to configure static ports for the specific services that need them.
Do not expose
Do not open individual ports here to the internet — the service behind the number changes, and the RPC surface should be internal regardless.
$ nmap -sV -Pn -p 49154 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.