Friday, April 30, 2010


The End. The rest of the chapter is just a more in depth explanation on troubleshooting a network. I don't really understand why it went through a quarter of the chapter with overly simple version and then an in-depth version. Also these posts have become harder to write due to the fact that the last chapter is just steps to do whatever and not actual concepts. But I will prevail!

So right now I'm reading about policies and regulations. Policies are basically what you do under certain circumstances like when a user is locked out of an account, a hacker breaks into your network or when a gia... nevermind. Procedures are procedures which you do when a policy comes into effect. Regulations are rules imposed by guvamnets and other organizations that your company must follow if you don't want to get hauled off to jail.

So this post has been sitting in my edit post section for a bit. Oh well here's some more stuff.

I went back to subnetting and I do understand it better than I did before, no thanks to the book BUT thanks to Ralph Becker's IP Address Subnetting Tutorial.


So an I.P. address is composed of two parts, the network address and the node address. If you have a Class A network the first octet is the network address and the last 3 the node address. A Class B network the first two octets are the network address and the last two are the node address. I hope you can guess what the Class C address is. When the node octets of the address are set to 0 you get the network address. When they're all set to 1 you get the broadcast address.

Now here is where I got caught up which is subnet masks. Mr. Elkner gave me an explanation of subnet masks and I will reiterate it for my own clarification. When you have a network address and you want more subnets than nodes you can apply a subnet mask to give yourself more subnets. So let's say you have the class B address The first two octets are the network address. The last two are the host/node address. By applying a subnet mask you get more subnets. Everyone outside your network sees your network address but inside the network you have your own little system of subnets.

Wednesday, April 28, 2010

User Error

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.