Submit a ticketCall us

Putting Your Logs Where They Belong with the New SolarWinds Log Manager for Orion

The new SolarWinds® Log Manager for Orion® finally puts your log data right where it belongs, in the heart of your Orion console. Gain insight into the performance of your infrastructure by monitoring your logs in a unified console allowing you to see a wealth of information about the health and performance of your network and servers.

Reserve a Seat for Wednesday May 23rd 11am CDT | Reserve a Seat for Tuesday May 22nd 10:30am GMT | Reserve a Seat for Tuesday May 22nd 1pm SGT / 3pm AEST

Home > Success Center > Netflow Traffic Analyzer (NTA) > Unable to assign Port 0 TCP/UDP to NTA service and application ports

Unable to assign Port 0 TCP/UDP to NTA service and application ports

Table of contents
Created by Deney De Guzman, last modified by Karen Valdellon on Jun 28, 2016

Views: 874 Votes: 1 Revisions: 7


This article discusses why Port 0 TCP/UDP cannot be assigned to NTA service and application ports.


All NTA versions


Port 0 (UDP or TCP) is a reserved port in networking, meaning it should not be used for any TCP or UDP communications as stated by IANA (Internet Assigned Numbers Authority). Since this is directed as a “reserved port,” our application follows the standard that it cannot be used or assigned. This is why that port is not applicable to be assigned or errors out.



Port 0 is defined on the SolarWinds NTA application but is not an option to be selected. Refer to the following screenshot of the database:



As best practice, Port 0 should not be seen or used on your network, although this port is a valid TCP/UDP port, it is highly recommend that one should block any traffic using this port at your firewall. No program should be listening on Port 0 and no program should connect from Port 0 thus it should be blocked.


If Port 0 is not blocked or is visible on your network, this should be seen by your devices and will be captured by your flows on the devices and sent out to NTA such as the following:



However, as recommended best practice, this should immediately be blocked and not used on the network.




Last modified