LabVIEW blocks UDP port 6000

[pawel]

Hi Smercurio

It took me a while because I had to reinstall Win2000 to WinXP as only WinXP has the netstat -a -o ability.

Here is the output.

Active Connections

  Proto  Local Address          Foreign Address        State           PID
  TCP    pds-2000:epmap         pds-2000:0             LISTENING       860
  TCP    pds-2000:microsoft-ds  pds-2000:0             LISTENING       4
  TCP    pds-2000:4899          pds-2000:0             LISTENING       900
  TCP    pds-2000:netbios-ssn   pds-2000:0             LISTENING       4
  TCP    pds-2000:4899          pap.reson.root:2319    ESTABLISHED     900
  TCP    pds-2000:1025          pds-2000:0             LISTENING       1576
  UDP    pds-2000:microsoft-ds  *:*                                    4
  UDP    pds-2000:isakmp        *:*                                    636
  UDP    pds-2000:2343          *:*                                    232
  UDP    pds-2000:4500          *:*                                    636
  UDP    pds-2000:5000          *:*                                    2016
  UDP    pds-2000:5001          *:*                                    248
  UDP    pds-2000:5002          *:*                                    408
  UDP    pds-2000:6000          *:*                                    2016
  UDP    pds-2000:6001          *:*                                    248
  UDP    pds-2000:6002          *:*                                    408
  UDP    pds-2000:ntp           *:*                                    924
  UDP    pds-2000:netbios-ns    *:*                                    4
  UDP    pds-2000:netbios-dgm   *:*                                    4
  UDP    pds-2000:ntp           *:*                                    924

I can see all the blocked ports, and PIDs. What now?

thanks

Pawel

[smercurio_fc · Accepted solution]

As I noted in my reply #8, the last column is the process ID that has the port open. You can use Task Manager to find out what process it is, and that will tell you who has that port open. In my case I found that the Lookout Citadel Server (lkcitdl.exe) was the process that had the port open. Once I shut down that service, the port was available.

[pawel]

Thanksa  lot.

I will chekc if I can shut that process freely and hopefully that will sove the problem.

thanks

[smercurio_fc]

Note that if the process is a service (like the Lookout Citadel Server), then you will need to disable it via the Services MMC plug-in. This can be accessed via the Administrative Tools (if you have it shown in your Start menu), or you can run it directly by select Start->Run... and entering "services.msc". You can also right-click on "My Computer" and selecting "Manage".