USUALLY, when client and SERVER applications are on the same computer, there is no network traffic. Thus, you cannot use Network Monitor to understand what is happening between the applications.

When you are TROUBLESHOOTING HTTP or other text-based protocols, if you have two computers, and the client is getting back unexpected results, RUN Network Monitor on the server to see if the server is sending the correct data.

You may need to trace on both the client and server if a firewall or intranet is causing network problems. In this scenario, you can compare traces more efficiently if you use the Net Time command to synchronize the system time on the computers.

If you have three computers that communicate in a three-tier architecture, you can run Network Monitor on the middle tier because all traffic crosses that computer.

Usually, when client and server applications are on the same computer, there is no network traffic. Thus, you cannot use Network Monitor to understand what is happening between the applications.

When you are troubleshooting HTTP or other text-based protocols, if you have two computers, and the client is getting back unexpected results, run Network Monitor on the server to see if the server is sending the correct data.

You may need to trace on both the client and server if a firewall or intranet is causing network problems. In this scenario, you can compare traces more efficiently if you use the Net Time command to synchronize the system time on the computers.

If you have three computers that communicate in a three-tier architecture, you can run Network Monitor on the middle tier because all traffic crosses that computer.