Identifying the Source of TCP Port Conflicts
de Rick K1MU
Commander, DXKeeper, and SpotCollector accept directives from other applications conveyed by messages using the TCP/IP protocol. The default TCP/IP Port from which each application accepts TCP messages and the means of choosing an alternative TCP/IP Port are shown in this table:
Application |
Default TCP/IP Port |
Configuration |
DXKeeper |
52001 |
Network Service panel on the Configuration window's Defaults tab |
Commander |
52002 |
TCP Network Service panel in the Network Service window displayed by clicking the Net Serve button on right side of the Configuration window's General tab |
SpotCollector |
52003 |
Network Service panel on the Configuration window's General tab |
If one of the above applications informs you on startup that its TCP/IP port is already in use, either configure that application to accept an alternative TCP/IP Port (and then configure the interoperating application to send directives to that alternative Port, or identify the application that is using the TCP/IP Port and reconfigure it to use an alternative port; either way, restart the DXLab application after making the change.
Identifying the Application that is Using A TCP/IP Port
To determine which application has opened a particular TCP/IP Port - 52001 in this example,
direct Windows to open a Cmd window (click the Windows Start button, type cmd, and press the Enter key)
enter this text in the Cmd window, and press the Enter key: netstat -ano | findstr 52001
the last column of this command's output is the ProcessID (PID) of the process that has opened port 52001. To identify the name of this process, enter this text in the Cmd window, and press the Enter key: tasklist /FI "PID eq XXXXX" where XXXXX is the PID revealed by the netstat command; the Image Name revealed by the tasklist command is the process that has opened Port 52001.
If there is no output of the netstat command in step 2, then Windows is confused as to TCPI/IP Port status; terminate all applications and reboot Windows.
Post a question or suggestion on the DXLab Discussion Group