TCPView - Free
When you need to know what ports your develepors' latest custom app uses on Windows, and no one one their entire team has a clue but they still expect you to fix the firewall to allow "their" traffic anyway because they are supposed to be in production in less than 24 hours and they are just now getting around testing the app in the final production configuration.
"It always worked on our other clients' networks with no problem. Of course, our implentations were smaller there..."
or
"It was custom written for us 8 years ago and was designed to run on '95 over IPX/SPX, but our new large production process that we are about to roll out needs this to work until the second phase deployment when we'll be updating that piece. We've thrown together a hack to get it working over Winsock on TCP/IP, but I don't know what ports we're using..."
or
"I'm not sure what the names of the exe's are that are supposed to be waiting for incoming data, not to mention which ports they use."
I hate those phrases.
When you need to know what ports your develepors' latest custom app uses on Windows, and no one one their entire team has a clue but they still expect you to fix the firewall to allow "their" traffic anyway because they are supposed to be in production in less than 24 hours and they are just now getting around testing the app in the final production configuration.
"It always worked on our other clients' networks with no problem. Of course, our implentations were smaller there..."
or
"It was custom written for us 8 years ago and was designed to run on '95 over IPX/SPX, but our new large production process that we are about to roll out needs this to work until the second phase deployment when we'll be updating that piece. We've thrown together a hack to get it working over Winsock on TCP/IP, but I don't know what ports we're using..."
or
"I'm not sure what the names of the exe's are that are supposed to be waiting for incoming data, not to mention which ports they use."
I hate those phrases.