So Netstat tells you which processes are holding which ports open, and who is connected to or from those ports. If you are new to Exchange, or if you see something unexpected in the list, you may need a little help identifying a particular process. That's where Tasklist comes in.
Suppose you found out that a process numbered 2688 was holding open port numbers 135 and 6001, but you didn't know what the process was or what it belonged to.
If you wanted to find out more information, you could enter the Tasklist command. When you did, Windows would display a list of all of the processes that are running on the server, as shown in Figure C. As you scrolled through the list, you would discover that process number 2688 refers to store.exe (this may be different on your system).
The Tasklist command lists all of the processes that are running on the server.
Knowing that the ports are being used by store.exe is great -- assuming that you know what store.exe is. But what if you aren't familiar with a particular process? You can easily find out by entering the following command (substitute # for the process ID):
Tasklist /svc /fi "pid eq #"
For example, if you wanted to find out what process ID number 2688 was, you would enter: Tasklist /svc /fi "pid eq 2688" After doing so, you would see that store.exe is part of the Exchange information store. The actual output looks like Figure
You can use the Tasklist /svc /fi "pid eq #" command to figure out what service or application a process belongs to.
|ABOUT THE AUTHOR:|
| Brien M. Posey, MCSE
Brien is a Microsoft Most Valuable Professional for his work with Windows 2000 Server and IIS. He has served as CIO for a nationwide chain of hospitals and was once in charge of IT security for Fort Knox. As a freelance technical writer, he has written for Microsoft, TechTarget, CNET, ZDNet, MSD2D, Relevant Technologies and other technology companies.