The two servers 10.1.1.1 and 10.2.2.2 are sitting on different network segments, one of them protected by a firewall. For those who are new to network analysis we use this blog post to introduce helpful Wireshark features and present a techniques to gather extra information about the network. Seasoned network engineers will quickly find the culprit by a careful look at the packet list of both traces. We need to find the root cause for this problem. The Skype administrator has identified the TCP port number for one of the failed connections. Network traffic was recorded on both servers. Still, the desired data exchange does not happen. The firewall log file documents that the connection is allowed. Two servers running Skype for Business try to exchange information. We assume that the reader is familiar with TCP basics like session setup, retransmissions, window size etc. We identify the root cause and gather information about the network topology. ![]() ![]() ![]() This post demonstrates how to correlate two or more trace files to analyze a broken connection.
0 Comments
Leave a Reply. |