(for Windows 95 / 98 / ME / NT 4.0 / 2000 / XP / 2003)
This is a tool that lists processes in your Windows system and the ports each one listen on. Unfortunately there are some stability problems due to the somewhat "strange" techniques Inzider uses. I guess there is still much left to wish for, but over all I think Inzider is a success, and it's quite popular despite the problems. On Windows NT/2000/XP, Inzider is still unable to check processes started as services.
Download the install program file and run it. The install program is created with the freeware (for non commercial use) GkSetup
written by Gero Kühn. After installation, run Inzider from the Start menu. It will take some seconds and then you will see a list of processes and which ports they listen on. Sometimes all processes aren't listed on the first try. If this happens, close the program and restart it. Repeat this until all processes are shown (which usually takes at most 2-3 tries). To minimize the risks of experiencing problems, please save all unsaved work before running Inzider. Also close any valuable documents and similar that you have open. After you finish using Inzider, reboot the system to guarantee it's stability.
Inzider may in some cases cause Windows programs or the Windows operating system itself to crash. In rare cases this might cause permanent damage to your Windows installation.
Q: When I try to install Inzider, I get an error message saying "GkWare SFX Module V1.90/Is - The data section attached to this self-extractor has been damaged. Please download this file again to get a complete copy.". What should I do now?
A: Reboot the computer and run the setup program again, then the installation should work.
Q: What does "bound at 0.0.0.0" mean?
A: It means that the process has bound the port at all available IP addresses.
Q: Why aren't all processes listed in Windows NT/2000/XP?
A: This is because Inzider is unable to inject it's "spy" code into processes running as services. Perhaps a future version will be able to.
Q: Some programs network connections freeze after Inzider has run. Why is that?
A: I've located the exact line in the code that does this, but the underlying problem seems to be quite complicated. I'm working on a solution but it will probably take some time to finish.
Q: Windows 9x bluescreens when I run Inzider, or all processes crasch. What's wrong?
A: If this happens there is probably some bug left in Inzider, please send me a mail to firstname.lastname@example.org and tell me exactly what happened. Also tell me which processes were running at the time and other facts you think are "special" in your case, or worth knowing to find the bug. It would also be helpful to know how often the problems occur, for example each time Inzider is run, or about every fifth time, and so on.
Q: Why are you talking about bugs and problems all the time? Is Inzider poorly written or something?
A: Well, no. I've tried to write it well, but it does some "strange stuff" in order to retrieve the information it needs. This is unavoidable as far as I know, and the problems I talk about are side effects from this. Normally you should avoid doing things that are not documented or not meant to be done, but in this case I know of no other way to do what Inzider does. If I find another way that makes the program more stable, I will probably implement it in a future version.
Q: Does Inzider do any "permanent" changes in my computer?
A: No. All it does is a regular intallation of files and adds itself to the Start menu. You can delete its files by hand if you wish (although it would be easier to use the uninstall option on the Start menu.) There is no replacement of system files performed by Inzider, that's one of the best features I think.
Q: When I try to delete the Inzider files, I can't delete the inz.dll, why is that?
A: That is because Inzider has failed to eject the DLL from one or more processes for some reason. You can't delete a file which is in use, so just reboot your system to release the file and you will be able to delete it.
Q: My firewall warns me that Inzider is trying to inject inz.dll into Internet Explorer and/or other programs. What does that mean?
A: As part of the port to process mapping Inzider injects the inz.dll into all processes it can. The technique of DLL injection can also be used for bypassing outbound firewall blocking, and since the firewall can't tell what the DLL will do after it has been injected it gives you a warning.
Q: I have a question that is not covered here. Where can I get help?
A: Send me
your question. I can't promise that I will have time to answer, but I'll do my best.