What Port 2490 Is
Port 2490 is registered with IANA for qip-qdhcp on both TCP and UDP. That name breaks down as QIP (Lucent's IP address management software) + QDHCP (QIP's internal DHCP service component).
The product is VitalQIP, an enterprise DDI platform — DNS, DHCP, and IP address management in one system. It was built for the scale problems that large carriers and enterprises face: managing hundreds of thousands of IP addresses, keeping DNS and DHCP synchronized, automating lease management across massive networks.1
Port 2490 is specifically the channel QIP's DHCP server component uses for internal service communication.
The Software Behind It
VitalQIP started at Lucent Technologies — the Bell Labs spinoff that built the infrastructure of the early Internet. Lucent became Alcatel-Lucent, which was acquired by Nokia. The product survived all three eras and is still maintained today as Nokia VitalQIP.2
It's enterprise-grade, carrier-grade software. If you've never heard of it, that's expected. It's designed for the networks behind the networks — the systems that ISPs and large enterprises use to manage IP space at scale, not something a typical sysadmin encounters.
What Range This Port Lives In
Port 2490 sits in the registered port range (1024–49151). This range is managed by IANA, and vendors and organizations can formally register port numbers for their software. Registration doesn't mean the port is in common use — it means someone filed the paperwork.
The registered range is the middle ground between well-known ports (0–1023, the familiar ones like HTTP's 80 and SSH's 22) and dynamic/ephemeral ports (49152–65535, assigned temporarily by the OS for outgoing connections).
Is This Port Running on Your System?
Almost certainly not, unless you're a network administrator who's specifically deployed VitalQIP. It's not bundled with any operating system, not enabled by default anywhere, and not commonly seen in security scans.
To check what's actually listening on this port on your machine:
Linux/macOS:
Windows:
If something is listening on 2490 and you're not running VitalQIP, that's worth investigating.
Why Unassigned-in-Practice Ports Matter
Most registered ports are like this one: formally assigned, rarely seen. The IANA registry has thousands of entries for software that's either niche, obsolete, or both.
This matters for two reasons. First, it establishes a paper trail — if you do encounter traffic on port 2490, you know where to start looking. Second, it prevents collisions. If two vendors independently chose the same port for unrelated software, you'd have a conflict that's nearly impossible to debug. The registry, imperfect as it is, keeps the port space from becoming completely chaotic.
이 페이지가 도움이 되었나요?