Ok, one last question on this subject. Where would I look to find out what application/process is responsible for the port? This seems to be highly guarded information
I'm going to have to say what program is actually using it. I'd like to narrow it down to an .exe actually.. Like alot of firewalls do, I just want to know what's open and 'who' is responsible. the GetTcpTable() function in the iphlpapi.dll is really usefull, but I just wanted the extra step. Under XP it's possible through the same DLL, but I use mostly 2k..