I am not at all planning to waste my time trying to fix this (or figure out what's causing it other than writing this single post ). When I stopped it, connection attempts stopped. I managed to link that executable to a service 'WD Drive Manager'. I compared to another device and found the same process. TCPView showed me a process names 'WDDriveService.EXE. (click on a thumbnail version to see full size image)Īgain, this is merely a question just out of curiosity. C:WINDOWSsystem32>taskkill /F /PID 1128 SUCCESS: The process with PID 9500 has been terminated. I logged on to one of the devices and ran TCPView and found connection attemps to those IP with PID 0. The above command displays all the connections with PID.

Let me say at the very beginning that yes, this is a same old 'Last XP' install (mentioned in that infamous thread) that I am planning to get rid of and install a new legit copy of XP (for which I already have installation CD ready honestly, I just haven't got time in the past few days to do it!) as soon as possible, so please spare me with posts urging me to do so because again, I will in the following few days!Īnyway, even though I suspect that this is indeed somehow related to 'broken' XP (and I am even more certain that you'll say it is), I will ask anyway: what do you think (if by any chance this is not Last XP's fault!) is causing these countless (obviously this is the so called 'System Idle Process' I know that because of the PID: 0) connections in TIME_WAIT state? Is maybe there any particular configuration setting in registry (or elsewhere) that could cause this (and with which I can eliminate this behavior)?! We can see the PID of every socket connection using the following command.

Pid 0 tcpview