I run into smart people who are solid troubleshooters but when they feel like a packet capture is the next logical step (usually the last one for them), they will open Wireshark, scroll, scroll, scroll, shrug, and close Wireshark. I don't usually say those things to customers. IT'S YOUR TERRIBLY TERRIBLY WRITTEN APP, YOU GIT" IT'S ALMOST NEVER THE NETWORK AND HERE'S THE PROOF. I don't have to spin my wheels wondering "is it this? could it be that?" I know packet analysis doesn't always solve the issue, but you can know better where to dig in and definitively be able to say "IT'S NOT THE NETWORK, YOU JERKS. But in this job where I have to troubleshoot our networking product that touches every layer of the stack, I've learned a great deal in quickly analyzing problems with packet analysis (Wireshark, basically) where to point the finger and what the likely culprits are. Admittedly, as a sysadmin, my packet analysis skills were next to nil. I've been a support engineer for going on 6 years and a sysadmin before that.
0 Comments
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |