Now let's put it all together and apply what you've learned to a real life case study.
A remote desktop user gets disconnected from the server. The server is hosted and not in our control.
First, we need to Define the Problem and narrow down the issue
Is this the only application with the problem?
What are the specifics of the issue - just broken or is it slow sometimes?
Just broken. Randomly disconnects
Is there an error message?
No error message
When did the problem start?
Issue was first reported 3 weeks ago
Has anything changed?
Not that we're aware of, either on the client machine or network. The client machine was a new install but that was 6 months before the issue was reported
Last patch update?
2 weeks ago but problem was happening before that
When does it happen?
Randomly. Could happen 4 times in an hour or twice over two days
Does it affect multiple people?
Three people are connecting to the server via RDC, but only one person has the problem
What are the differences in the work flow or behavior in these 3 people?
The one with the problem uses RDC much more often than the other two.
Windows 7 x64 Professional
Windows 7 x64 Professional
What devices are in our network path?
Client -> Netgear GS724T-> HP ProCurve 1800-24G -> Cisco ASA 5510 -> Comcast modem
What are the client and server IPs?
Client: 192.168.108.186 Server: 22.214.171.124
Capturing the data - In this case, you have run Wireshark on the problematic client's machine until there was a disconnect. You did not use a capture filter. The disconnect occurred about 2:50pmEDT
Verify the data - Make sure the data captured covers the time of the disconnect and that you see traffic between the client and server. Hint (highlight the following text with your mouse): Go to Statistics -> Summary. Make sure the captured time range covers the issue at 2:50pmET a
Wireshark Setup - Make sure you've configured Wireshark to your liking. Refer to the Wireshark Setup lesson.
Analysis - Highlight the hidden text after the word "Hint" to see a hint
- Find the beginning of the connections between the client and server. Hint: Add filter for SYN packets to the client and server filter: (ip.addr eq 192.168.108.186 and ip.addr eq 126.96.36.199) and tcp.flags==2
- Look at each connection to see if you can find a problem. Hint: Apply a TCP conversation filter on each SYN packet one by one to look at each conversation. Right click -> Conversation filter -> TCP. Look at the end of each connection to see how it closes
- What looks like a problem and what might be a normal window close? Hint: Most connections have no outstanding data in flight and the client closes the connection with a RST. The problematic connection appears to have packet loss and the client gives up and RSTs the connection. Does this problem correspond with the time of the issue? Problem connection: (ip.addr eq 192.168.108.186 and ip.addr eq 188.8.131.52) and (tcp.port eq 56770 and tcp.port eq 3389)
- What do you notice about when the retransmissions start? Hint: Look at delay of the original segment that gets retransmitted later - frame 34997. It appears there's a long delay just before the data is lost. Since this is RDC, it could be the user doing something else e.g. using another application outside the RDC connection, getting coffee, talking with someone, etc
- What's another test you could do to determine if the host is unresponsive or these packets are just not getting through? Hint: Run a continuous ping to see if the host also stops responding to ping. Add icmp as a display filter to the filter string and see if the host stopped responding to pings during the retransmissions. Filter: ((ip.addr eq 192.168.108.186 and ip.addr eq 184.108.40.206) and (tcp.port eq 56770 and tcp.port eq 3389)) or icmp
- What's a possible next step? Hint: Look at the logs of the ASA for dropped packets for this traffic. Take a capture either on the ASA or on the outside interface to see if the packets are getting dropped there. If the traffic is getting through, then need to follow up with the hosting provider
My Analysis - Before you watch this video, do the analysis yourself. Answer the questions above. Once you do that, follow along with the video