# WHATPORT(32773)

## NAME

port 32773 — filenet-cm (IANA) / dynamic ONC RPC — Registered to FileNET Component Manager; in the wild it is a dynamically assigned ONC RPC program, not that product.

Protocol: TCP/UDP  
IANA registry

## DESCRIPTION

IANA assigns 32773 to FileNET Component Manager, part of the FileNet block spanning 32768–32777, and that product is rarely what you find. Historically this range is where Solaris and other System V hosts handed out ports to ONC RPC programs that registered with rpcbind, which is why Nmap names the port sometimes-rpc9. Nmap's comment records it as an RPC port on Solaris, most often rquotad. On Linux the same number falls inside the default ephemeral range (32768–60999), so it can equally be a container publish or an outbound socket. The only way to know is to ask rpcbind or fingerprint the listener.

## EXPOSURE

**Expose with care.** Legacy ONC RPC services here (statd, rusersd, rquotad, sprayd, walld) authenticate weakly or not at all and have a long CVE history; keep them off the internet and reachable only from trusted NFS clients.

## CHECK

```sh
rpcinfo -p TARGET
```

## SEE ALSO

- iana — [IANA port registry — 32773 (filenet-cm)](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=32773) (iana.org)
- spec — [RFC 1833 — Binding Protocols for ONC RPC Version 2](https://www.rfc-editor.org/rfc/rfc1833.html) (rfc-editor.org)
- docs — [rpcbind(8) manual page](https://man7.org/linux/man-pages/man8/rpcbind.8.html) (man7.org)
- source — [nmap-services — Nmap's port frequency and name table](https://github.com/nmap/nmap/blob/master/nmap-services) (github.com)

---

HTML: <https://whatport.net/32773/> · JSON: <https://whatport.net/32773.json> · full dataset: <https://whatport.net/ports.json>