Unregistered high port; a Windows RPC service listening here is the common explanation.
Nothing is registered at 49161 and nothing can be: RFC 6335 places 49152-65535 in the Dynamic Ports range, outside IANA assignment. Windows RPC servers bind ports from this range at service start and register the mapping with the endpoint mapper on TCP 135, which is the only reliable way to name what is listening. Because allocation is first-come, the same service will sit on a different number after the next reboot, so firewall rules written against a specific port here break.
Do not expose
If a service genuinely needs to be reachable, pin it to a fixed registered port and allow that instead of opening a dynamic range to untrusted networks.
$ sudo lsof -nP -iTCP:49161 -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.