He says that the connection 'just closes' and the command box 'just disappears'. This user complains that, 'every day' (lUser speak for 'about once a month') when he attempts to FTP to the address he has been given, he is unable to do so. He also cannot interpret screen commands, read simple dialog boxes, copy down an error message reliably or keep windows displaying error codes open when requested to do so by first line support. This user is something of a luddite - he has been told how to logon and retrieve the file but nothing else about how FTP works. The user is using a workstation with the IP address: 192.168.1.40, and the server is located at 192.168.1.151. You have a user (let's call him 'Donut') on your network who regularly has to FTP to a machine elsewhere on your network to retrieve a file. it has, on many occasions, given me the answer to problems it might have taken me hours to diagnose in less than ten minutes. Wireshark can truly be your friend when attempting to troubleshoot a potentially tricky network issue - it's ability to sneak a peek at the raw data travelling across your network can prove invaluable. Unfortunately, since your salary is usually dependent on cleaning up the mess these tards have made of your precious network - and management seem to think they are actually doing something useful with their PCs instead of playing games, sending colleagues who work twelve feet away stupid emails or looking for 'interesting' ways to breach your firewall and download malware, this is seldom an option in most workplaces. They should never be kept in the same room and, in a perfect world, would never come into contact with each other. The same maxim you would apply to small children and savage wild animals should be applicable to 'most users' and 'computers'.
Last time we looked at Wireshark we were concentrating on how it actually works - this time out we'll be looking at an example of a way you could put it to practical use 'on the job'.Īs anyone who has ever worked in tech support will tell you, users are the bane of your life.
Out of habit I STILL call it Ethereal from time to time - but as even I've got used to using the new name now I think the thread titles should be changed I've given classes to peeps at work on Ethereal a lot in the past six months or so and have finally started to knock together some notes to use in a formal presentation.įirst up, I should probably start out by saying that Ethereal is (and has been for some time) now called Wireshark. Well, this is it - the final part of a tutorial I have been promising for months. Please disable your ad-block, or become a premium member to hide all advertisements and this notice. Blocking our ads means your killing our stats! and it needs advertisements in order to keep running. This website is run by the community, for the community.
0 kommentar(er)
