I have looked at netstat -b and found this under port 80: Proto Local Address Foreign Address State TCP 74.225.231.4:80 79-113-39-251:49540 CLOSE_WAIT[System] TCP 74.225.231.4:80 79-113-39-251:49552 CLOSE_WAIT[System] TCP 74.225.231.4:80 79-113-39-251:49554 CLOSE_WAIT[System] TCP 74.225.231.4:80 79-113-39-251:49555 CLOSE_WAIT[System] TCP 74.225.231.4:80 79-113-39-251:49557 CLOSE_WAIT[System] TCP 74.225.231.4:80 79-113-39-251:49562 CLOSE_WAIT[System]Then I tried netstat -ao and this showed: TCP 74.225.231.4:80 79-113-39-251:49540 CLOSE_WAIT 3244 TCP 74.225.231.4:80 79-113-39-251:49552 CLOSE_WAIT 3244 TCP 74.225.231.4:80 79-113-39-251:49554 CLOSE_WAIT 3244 TCP 74.225.231.4:80 79-113-39-251:49555 CLOSE_WAIT 3244 TCP 74.225.231.4:80 79-113-39-251:49557 CLOSE_WAIT 3244 TCP 74.225.231.4:80 79-113-39-251:49562 CLOSE_WAIT 3244For some reason i cannot find a program using that particular PID in task manager. This is strange, and I really need to free port 80.EDIT: I would also like to add that port 80 is not in use when I set the listening address on the host application to 127.0.0.1 and 74.225.231.4. It is when I am listening on 0.0.0.0 that the issue arises.PS: i need to use 0.0.0.0 because i have a dynamic IP

I just got further into the problem and found in an output file generated by cmdprompt when i typed netstat -ano (only the significant part will be shown) Proto Local Address Foreign Address State PID TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 3244And then i tried tskill 3244 and this output came out:C:\Windows\system32>tskill 3244Could not find process: 3244Same with taskkill:C:\Windows\system32>taskkill /pid 3244ERROR: The process "3244" not found.Does anyone mind telling me what Vista can possibly be doing?

I solved my problem by closing DW20.exe which was a Windows Error Reporting service that was running. However, no sign of that process with ID 3244, but port 80 is working fine.

Many thanks for posting this question. We had a similar problem running WebLogic Node Manager, version 10.0.0.0, on Windows Server 2008. Whenever we shut the Node Manager down, a 'System' process would appear on that port, with the same PID that the Node Manager previously had, and both Task Manager and 'taskkill' reported that no process existed with that PID. So, had to change the Node Manager port (which involved a registry change) to restart the Node Manager, or else reboot the box. However, we don't use dynamic addresses, and when we switching from listening on 'all interfaces' (no address specified) to 'localhost', the problem went away :). I think that this must be a bug in Windows Vista (and Server 2008, which uses the same codebase).