2 entries are registered on port 2049. It is a registered port (1024–49151) — IANA records an assignee, but nothing stops other software from listening here, which is why the number carries more than one entry.
services registered on this number
1 transport in use
entries encrypted on the wire
2 of 2 iana-registered
| port | service | proto | category | risk | views |
|---|---|---|---|---|---|
| :2049 | Network File System | UDP | File Transfer | caution | 7.2k |
| :2049 | NFS | UDP | File Transfer | caution | 6.4k |
2049/UDP is commonly used by NFS (Network File System), a protocol developed by Sun Microsystems that enables remote access to shared file systems across a network. It allows systems to mount disks located on remote hosts as seamlessly as if they were part of the local file system hierarchy. This facilitates file sharing, centralized management, and collaboration within distributed network environments.
port 2049 as Network File System →Network File System (NFS) is a widely used distributed file system protocol that enables users and applications to access files over a network as if they were on local storage. Port 2049 typically serves as the primary communication channel for NFS over UDP. It facilitates remote file access across heterogeneous systems, centralizing data management and improving collaboration.
port 2049 as NFS →The registry says what 2049 is registered to. What is listening on it right now is decided by the host, and only the host can be asked. Each of these prints the process behind the socket.
ss -ltnp | grep ':2049\b'lsof -nP -iTCP:2049 -sTCP:LISTENnetstat -ano | findstr :2049On Linux and Windows the process name comes back with the socket; on macOS lsof needs sudo to name a process that isn't yours. Match what it prints against the 2 entries above.
A port number is not a service. Anything may listen on 2049 — what you actually met is decided by the host, not the registry. If a service is missing here, it belongs in the registry.
contribute an entry