Port 2146: Live Vault Admin Event Notification

What Port 2146 Is

Port 2146 is officially registered with IANA under the service name lv-not — Live Vault Admin Event Notification. It runs on both TCP and UDP.

This port belongs to LiveVault: a continuous remote backup service that launched in the early 2000s, before "cloud backup" was a common phrase. LiveVault sold to Iron Mountain, then became part of HP's service portfolio, and eventually landed at CyberFortress, where it still operates today. The IANA registration carries the original name.¹

What "Event Notification" Means Here

Backup systems need to know when things happen. Agent started. Backup completed. Backup failed. Disk nearly full. That's what an admin event notification channel does — it's the wire that carries status signals back to the management layer, separate from the data channel that carries the actual backup traffic.

LiveVault uses a family of ports for different functions. Port 2144 handles vault connections (actual backup data). Port 2145 handles bridge connections (persistent status links). Port 2146 was registered for admin event notifications — the administrative signaling layer.²

If you see port 2146 open on a machine, it almost certainly has the LiveVault agent installed, or once did.

What Range This Port Belongs To

Port 2146 sits in the registered ports range: 1024 to 49151.

These ports require registration with IANA but don't receive the same protections as well-known ports (0-1023). Any application can technically use any registered port — registration is a claim of intent, not a lock. The system works on trust and convention, not enforcement.

The registered range is where most real-world application protocols live. It's the middle layer of the port system: above the privileged territory of system services, below the chaos of ephemeral ports.

How to Check What's Listening on Port 2146

On Linux or macOS:

# Show what process is using port 2146
sudo ss -tlnp | grep 2146

# Or with lsof
sudo lsof -i :2146

On Windows:

# Show active connections on port 2146
netstat -ano | findstr :2146

# Then look up the PID
tasklist | findstr <PID>

If nothing is listening, the port is closed. If something is there and you don't recognize it, the process name will tell you what it is.

Why Unassigned-Looking Ports Matter

Port 2146 isn't truly unassigned — it has a registered owner. But to most people, it looks like a mystery port. That ambiguity is exactly what makes the port system interesting and occasionally dangerous.

When you see an unfamiliar port open on a system, you're looking at one of three things:

1. A legitimate registered service you don't recognize (like lv-not)
2. An application that chose a port without registering it
3. Something that shouldn't be there

The IANA registry resolves case 1. Process inspection resolves cases 2 and 3. The tools above do both.