So back to last week I said I had something super sorta cool in store depending if you like video games and it is somewhat related to programming which my blog isn't about BUT ANYWAYS I didn't post about it since I was trying to find a video of it in action so when I find one I will. Also Jelkner (I will hereby refer to you by your username) mentioned acquiring the network hardware I wrote about. Well unless we already have this stuff you would have to pay hundreds of dollars on this stuff. Except of course a punch-down tool... Now onto USER ERROR and errors.
When something is wrong it's always the user's fault. At least in my experience. Basically the entire chapter is diagnosing problems. First you start with the simple questions when a user can't log in like is the computer on, is the caps key on, do you have more than 2 brain cells? If somehow that doesn't work then you have to haul your arse down to the user and try things out for yourself. If it's hardware replace it, if it's software re-install it.
Now if after doing your magic the workstation still doesn't work and trying the user's login from another workstation doesn't work either you has a problem with your segment. Check the server for user permissions and if that isn't the problem have fun. (Just so you know I read the chapter, write up what I read and then re read certain parts to make sure I got the right info down.)
So if it's not the server then you have to check the cabling for things like crosstalk where to cables are bleeding onto each other, attenuation where signal is degrading over distances, collisions although that shouldn't happen in this day and age, electromagnetic interference and it could just be a bad cable.
The next part discusses troubleshooting when you have a wireless network and then the next next part of the chapter gives you steps to take in solving network problems. Yay.