Port 2692: Admins LMS — Registered, Forgotten

What This Port Is

Port 2692 sits in the registered ports range (1024–49151). IANA lists it as assigned to a service named Admins LMS — a learning management system — on both TCP and UDP, registered to an individual named Dagfinn Saether.¹

That's the complete official record. No RFC. No documentation. No public codebase. No evidence of deployment in the wild.

The Gap Between Registration and Reality

The registered ports range exists because IANA lets organizations and individuals claim port numbers for their services. The process is straightforward: apply, get assigned, use your port. But "get assigned" doesn't mean "actually used."

Thousands of registered ports are attached to services that were proposed, partially built, or simply never deployed at scale. Port 2692 appears to be one of these. The registration dates from the era when individual developers could reserve a port for a product that may have existed only internally, or shipped to a handful of customers, or never shipped at all.

This matters because it means if you see traffic on port 2692, it almost certainly isn't Admins LMS. It's something else — a custom application, a misconfigured service, or software that picked an available port number without checking the registry.

What to Do If You See This Port Open

If something is listening on port 2692 on your system, find out what it is before assuming anything.

On Linux or macOS:

# See what process owns the port
ss -tlnp | grep 2692
# or
lsof -i :2692

On Windows:

netstat -ano | findstr :2692
# Then look up the PID in Task Manager, or:
Get-Process -Id (Get-NetTCPConnection -LocalPort 2692).OwningProcess

If you don't recognize the process, treat it as you would any unexpected open port: investigate before trusting.

Why Unassigned (and Forgotten) Ports Matter

The port system depends on coordination. When a well-known service occupies port 443, every browser in the world knows where to find HTTPS. When port 2692 is technically assigned but practically empty, it creates ambiguity — any application can use it, and nothing will break until two applications try to claim it on the same machine simultaneously.

The registered ports range is a registry, not an enforcer. No one checks.