Best way to truly learn Networks/Routers on a time limit?

[eno]

I am applying for a new position where the main focus is " In-home Networking" setups. Mainly running peoples routers and setting up there networks to share files. I have installed my own basic router on my 2 computer setup but thats about it for the networks. I know this is extremly basic for most of you but I need to find a way to be able to entirely troubleshoot and understand networks so I can be competent at my job. Thanks too anyone who helps.

1.) Best ways/course/books to learn this stuff inside out. Remember I have about 1month to cram.

PS : I posted a similar topic in the off topic area last week more geared towards repair side of computers, this post I am only concerned with networks and troubleshooting purposes. I did order this Book.

Book will be here in a week or two depending on the sites speed.

 

[Washoe]

looks like a decent book to me

 

[Boscoh]

You can't really learn networking and routing in a month. It's going to take a while, and a lot of practical experience before you really understand things.

That said, here are a few links to some books, all of which are sitting on my shelf. Most of this stuff I know in my head now, but at one time I referenced them quite a bit:

http://www.ciscopress.com/title/158713800X

http://www.ciscopress.com/title/1578700698

http://www.ciscopress.com/title/1587200945

 

[bigshooter]

For what he's goign to be doing, those books would be overkill. Way too much info for him to figure out in a month. Find a network+ book. It's kind of like the A+ certification, but with networking. It's pretty basic and will give you a good comprehensivebase. If you want to get into more advanced stuff later, go for the cisco stuff. You'll learn more advanced concepts as well as how to implement them with Cisco products.

You'll probably also want to beef up on MS OS products, probably WinXP home and Win98. They are the most common home OS's out there. That will probably be the biggest help for you since most people are going to have a Linksys/DLink router that pretty much sets itself up.

 

[cmetz]

What you need is experience. You can't get that in a month, and you can't get that from a book. If you're just trying to cram in order to BS your way through an interview, you are doing yourself and your potential employer a huge disservice. I suggest you reposition yourself as someone with some experience and a lot of ability (and desire) to learn.

Woe betide he who comes to me in an engineering interview claiming to know things he does not.

 

[bigshooter]

This is for a home networking interview. I think he can cram enough in in a month to BS his way through an interview AND do a reasonably good job. There's not much to setting up a home network. I also wouldn't call this an engineering job. In fact I really dislike calling anyone who doesn't have an engineering degree an engineer of any sorts. The title network engineer is a joke in most senses.

 

[cmetz]

bigshooter, you are totally right about people being mislabelled engineers. Many of them that I work with are actually EEs (or "computer engineers" who are actually competent). I have no problem with "network engineers" who are Real Engineers(tm) - but of course most in the world just aren't. At the end of the day, it's not about the label, it's about what the person can do.

Just because it's "home networking" doesn't at all change the fact that it's going to be mostly about experience, which the poster doesn't have. If he goes in claiming to have experience and capability he doesn't, he either is caught and thus does poorly in the interview, or he isn't caught and then is thrown out to customer sites where he performs below expectations in the field. I think he's currently positioning himself in a way where there's not much winning, and by repositioning himself in a different way he can be put into a position where he might get the job (depending on what they're looking for initially) and if he does he won't be hosed going in.

 

[bgroff]

Originally posted by: bigshooter
This is for a home networking interview. I think he can cram enough in in a month to BS his way through an interview AND do a reasonably good job. There's not much to setting up a home network. I also wouldn't call this an <EM>engineering</em> job. In fact I really dislike calling anyone who doesn't have an engineering degree an engineer of any sorts. The title network engineer is a joke in most senses.

If you really want to take that argument about "Engineers" to its logical conclusion, you should move to the state of Texas. Legally, the only person who can use the title "Engineer" must be a licensed practicing Professional Engineer. This means that they would have had to take and passed both the EIT test and the PE test.

 

[eigen]

Read the books then go and explore some networks. Get some packet sniffing software look at how the routing alorithmns work, how packets look on the network etc.

 

[eno]

Good stuff. I am not trying to BS my way through a interview. Where I work I have no other way of gaining this experience unless I switched jobs and found some small job where I could work for dirt to learn the trade. I am only doing basic consumer level home networks, and I am a smart fella. I am not bought ready to jump into a position then have to quit cause I can't do a good job. But as far as learning basic networks, I believe I can learn it in time to be a competent employee on the jobsite. I will be able to buy and test the wireless/wired networking components to get some hands on experience. As of now I am learning the ins and outs of basic networks and soon I will have some hardware to play with to test on my 3 computers I have here. Thanks for all your input.

 

[bigshooter]

Originally posted by: bgroff

Originally posted by: bigshooter This is for a home networking interview. I think he can cram enough in in a month to BS his way through an interview AND do a reasonably good job. There's not much to setting up a home network. I also wouldn't call this an engineering job. In fact I really dislike calling anyone who doesn't have an engineering degree an engineer of any sorts. The title network engineer is a joke in most senses.

If you really want to take that argument about "Engineers" to its logical conclusion, you should move to the state of Texas. Legally, the only person who can use the title "Engineer" must be a licensed practicing Professional Engineer. This means that they would have had to take and passed both the EIT test and the PE test.

Exactly.... I am a systems administrator, and would never call myself an engineer. I hate the way MS uses it in it's certs, as well as job titles like Desktop Engineer, (software engineer is ok in my opinion, because I know some pretty smart that can code circles around me), hardware engineer, and the like. If I go back for CE or EE, I also want my degree/title to mean something.

 

[mboy]

Since this is just home stuff, No IOS, basic, if any ACL's, etc. Go buy 3 or 4 differnt, cheap (and a wifi or 2) home router. Lock yourself in your house for the month and network as many of your PC's with they varying equipt. you can.

 

[lowpost]

Exactly.... I am a systems administrator, and would never call myself an engineer. I hate the way MS uses it in it's certs, as well as job titles like Desktop Engineer, (software engineer is ok in my opinion, because I know some pretty smart that can code circles around me), hardware engineer, and the like. If I go back for CE or EE, I also want my degree/title to mean something.

Microsoft isn't the only one. RHCE... red hat certified engineer. I'm sure there are others.