Introduction to Network Trace Analysis 3: TCP Performance
A lot of variables affect TCP performance but not all of them are easily configurable. Let’s start with our absolute constraint. The speed of light. Unfortunately, we need to abide by the pesky laws of physics. Let’s say I am communicating with a server on the exact opposite site of the earth 6,357km away.Introduction to Network Trace Analysis 5: SMB? Sounds good to me!
Let's start off with the question, what is this whole SMB thing anyway? SMB is a network file system protocol. This means that it can allow Machine A to read and write files on Machine B. This protocol serves as the backbone of much of the Enterprise Windows Ecosystem. For example, did you know that the group policy SYSVOL is an SMB share? Pretty cool right? In recent history, there have been tons of improvements to SMB.Introduction to Network Trace Analysis 4: DNS (it's always DNS)
Howdy everyone! I'm back to talk about one of my favorite causes of heartache, the domain name system (DNS). This will be our first foray into an application layer protocol. The concept of DNS is simple enough, but it can lead to some confusing situations if you don't keep its function in mind. No time to waste, let's get going!Introduction to Network Trace Analysis Part 0: Laying the Groundwork
Nearly all modern applications use the network to some degree and knowing how your specific technology interacts with the network will help you understand not only the portion that uses the network but also how your application is designed. If you can perform a basic network trace it can help direct further analysis and prevent at least a few trips down rabbit holes (I'm looking at you DNS).
