Port 2146 LV-NOT
Port 2146 is the IANA-assigned lv-not port for Live Vault Admin Event Notification (TCP / UDP).
What is port 2146 used for?
Port 2146 is assigned to lv-not and uses TCP / UDP. The IANA registry describes the service as “Live Vault Admin Event Notification”. It sits in the registered range, the block used by databases, application servers and developer tooling. Port conflicts here are common when several local services start at once.
Ports are the transport-layer address a service listens on. A client that wants to reach lv-not connects to port 2146. A TCP connection is refused when nothing is listening, while a UDP request simply goes unanswered. That is why a port conflict appears whenever two processes try to bind the same number.
Use the commands below to confirm whether port 2146 is actually in use before you change firewall rules. Blocking the port stops new inbound traffic at the firewall, but it does not stop a local process from listening, and it does not remove the service from the machine.
Browse all Infrastructure and administration ports
Source: IANA Service Name and Transport Protocol Port Number Registry.
Check and block port 2146
Copy-ready commands for the protocols assigned to this port. Run the check first, then block only what should not be reachable.
Check on Linux
sudo ss -tlpn 'sport = :2146'
sudo ss -ulpn 'sport = :2146'Check on Windows
Get-NetTCPConnection -LocalPort 2146 -State Listen -ErrorAction SilentlyContinue
Get-NetUDPEndpoint -LocalPort 2146 -ErrorAction SilentlyContinueBlock with UFW
sudo ufw deny 2146/tcp
sudo ufw deny 2146/udpBlock with iptables
sudo iptables -A INPUT -p tcp --dport 2146 -j DROP
sudo iptables -A INPUT -p udp --dport 2146 -j DROPThese commands are examples for a typical host. Check the listener before you change firewall rules, and persist iptables rules with iptables-save or netfilter-persistent. On Windows, use Windows Defender Firewall or New-NetFirewallRule for persistent blocks. The iptables rules here cover IPv4; mirror them with ip6tables if IPv6 is enabled.
Is port 2146 safe to expose?
This port is not on our curated list of services with a widely exploited profile. Exposure is only safe when the listening service is intended, patched and protected by a firewall. Keep the listening service patched and remove it if unused. A default-deny firewall policy with explicit allow rules is still the safest baseline.
Where port 2146 is usually used
Most traffic on port 2146 falls into these scenarios. The demo below is a safe way to confirm the listener before you change anything.
- Service discovery, configuration and secret management for other systems.
- Administration panels used by operators rather than end users.
- Automation that reads or updates control-plane state on port 2146.
Probe the control-plane service
These services are high-value targets. Verify the listener from a trusted host before changing firewall rules.
nc -vz 127.0.0.1 2146Common problems with port 2146
Connection refused or timed out
Refused usually means the host is reachable but nothing is listening on port 2146. A timeout more often means a firewall drop, a wrong host or a service bound to a different interface.
Port already in use
Find the process holding the port with sudo ss -tlpn 'sport = :2146' or sudo lsof -i :2146. Stop that process or configure it to bind another port; killing it without identifying it can take down a production service.
Firewall rule did not survive a reboot
UFW and Windows Firewall keep rules across restarts. Raw iptables rules do not: save them with iptables-save or the netfilter-persistent package, and re-apply after upgrades that reset the ruleset.
The port is blocked but still reachable
A firewall rule filters inbound traffic; it does not close the listener. Confirm with the check command above and bind the service to 127.0.0.1 when only local clients need it.
Port 2146 at a glance
| Port number | 2146 |
|---|---|
| Service name | lv-not |
| Transport protocol | TCP / UDP |
| Category | Infrastructure and administration |
| Range | Registered port (1024–10000) |
| Risk level | Standard/Low |
| Registered assignee | Not listed |
| Registry description | Live Vault Admin Event Notification |
| Source | IANA Service Name and Transport Protocol Port Number Registry |
Frequently asked questions
What is port 2146 used for?
Port 2146 (LV-NOT) uses TCP / UDP. Live Vault Admin Event Notification.
How do I check if port 2146 is open?
On Linux run `sudo ss -tlpn 'sport = :2146'` and `sudo ss -ulpn 'sport = :2146'`. On Windows run `Get-NetTCPConnection -LocalPort 2146 -State Listen -ErrorAction SilentlyContinue` and `Get-NetUDPEndpoint -LocalPort 2146 -ErrorAction SilentlyContinue` in PowerShell. If the port is open, the output shows a process listening on port 2146; empty output usually means nothing is bound to it.
How do I block port 2146?
With UFW run `sudo ufw deny 2146/tcp` and `sudo ufw deny 2146/udp`. With iptables run `sudo iptables -A INPUT -p tcp --dport 2146 -j DROP` and `sudo iptables -A INPUT -p udp --dport 2146 -j DROP`. Persist the iptables rules with your distribution's netfilter-persistent or iptables-save tooling so they survive a reboot.
Is port 2146 safe to expose?
This port is not on our curated list of services with a widely exploited profile. Exposure is only safe when the listening service is intended, patched and protected by a firewall. Nevertheless, keep the listening service patched and remove it if unused. A default-deny firewall policy with explicit allow rules is still the safest baseline.
Related ports
Primary data: IANA Service Name and Transport Protocol Port Number Registry.
Last reviewed 2026-10-30 · Methodology · About · Privacy