In-Reply-To: <[EMAIL PROTECTED]>
>First thing to do is get a copy of fport from foundstone(.com look >under tools). That will tell you what the program is that has the >port open. Good advice. > Then mess with that program How so? fport.exe doesn't open the ports, nor does it provide any means of closing them. When you say "mess with that program", what are you referring to? I'm curious to see if you've discovered a hidden/undocumented switch of some kind. > (or the OS in some cases) to get the port to close. It's not entirely clear what you mean by 'the OS in some cases'. If a port is opened and is 'LISTENING', then there is most likely some application that has bound to that port. It would make sense, then, that if you disabled the application, the port would no longer be 'LISTENING'. If IIS is bound to port 80, disabling IIS will 'close' port 80.
