[WT-support] UDP problem

[Olivier F5MZN]

Hi Slaw,

I could not suggest anything better than Pablo EA4TX and my guess is 
also that another process like an antivirus, antispyware (or maybe a 
virus/trojan/... itself) ... is causing the trouble.

Can you try to run the command "netstat -anop udp" in a CMD.EXE window?

C:\>netstat -anop udp

Connexions actives

   Proto  Adresse locale         Adresse distante       Etat
   UDP    0.0.0.0:445            *:*                              4
   UDP    0.0.0.0:500            *:*                              740
   UDP    0.0.0.0:1029           *:*                              1528
   UDP    0.0.0.0:1060           *:*                              1528
   UDP    0.0.0.0:1061           *:*                              1528
   UDP    0.0.0.0:4500           *:*                              740
   UDP    0.0.0.0:9871           *:*                              600
   UDP    127.0.0.1:123          *:*                              1492
   UDP    127.0.0.1:1033         *:*                              3116
   UDP    127.0.0.1:1900         *:*                              1612
   UDP    192.168.0.221:123      *:*                              1492
   UDP    192.168.0.221:137      *:*                              4
   UDP    192.168.0.221:138      *:*                              4
   UDP    192.168.0.221:1900     *:*                              1612

As you can see is this example, port 9871/UDP is currently shown:
"0.0.0.0:9871   *:*  600" means that the process number 600 (PID=600) is 
listening on any interface on port 9871. The Task Manager tells that PID 
600 is owned by WT.EXE, which is true: WT was running on my computer.

You can also try the command "netstat -abnp udp" in order to show 
directly the program name, but it is much more verbose:

C:\>netstat -abnp udp

------ 8< ------ [snip]

   UDP    0.0.0.0:9871           *:*                              600
   [wt.exe]

------ 8< ------ [snip]

In your case, when WT is not running, you should not see any process 
listening to the port 9871. Please check and tell it to us.

73,
-- 
Olivier / f5mzn