I am networking student, i hve lots of doubts to be cleared, unfortunately no good guide to leed me?

I belive only in Internet.......even then i couldnt get some answer or solution that i am looking for......can any one help me in this issue.........how can i educate myself......please help me..


(please dont answer that whats your doubt.......i have many silly doubts which seems i am unfit for the networking field...........but i am much interested in networking,system side,hardware,etc. So let me know a good one(ebook or url or any other) which explains every thing, right frm basic to high technical.............

I am networking student, i hve lots of doubts to be cleared, unfortunately no good guide to leed me?
There are too many facets of "networking" to be able to say "pick up book X, read it through and by the time you're done, you'll be some type of expert." It just doesn't exist. You need to narrow your search to an area that interests you the most. You can also go from a very broad definition to a very narrow one. For example, you could be a WAN engineer which would take care of designing all aspects of access to and from remote sites including routers, switches, ISP circuit aquisition, bandwidth allocation, Quality of Service, etc. However, you could narrow it down to specializing in routers and switch configurations. This would be a Cisco engineer or a Juniper Engineer.





Usually, you want to end up somewhere in the middle, though so that you don't narrow yourself out of a job if the CEO of said company decides to invest everything in Enron... That means you have to know some about all of the pieces of the puzzle.





In the network world, no one is an island - meaning that you are going to have to interact with other people and that might also mean that you need to work with them to get them to do their portion of the job, such as provision the circuit properly. Time is your friend as you should continuously learn more and more about the network industry as your career progresses. Some of the things you once knew will be forgotten, such as how mainframe protocols work, but that's probably because you don't need that knowledge anymore as the industry has changed. What it boils down to is simple: learn the basics in school (what the different networking equipment is, how they work (in general), details about circuit speeds and protocols used on them, general knowledge on IP Addressing, etc).





Working in a small company, they expect you have a broader knowledge. You might be the "Network Engineer" but handle things like Systems Administrator, Network Security, and Help Desk combined in one job. They simply have less stuff going on and less overhead to pay for a specialized staff for each area of "networking." Larger companies have the money to pay to specialize their people as "Server Administrators", "System Analysts", "System Administrators", "Hep Desk", "Network Engineers", etc. The list goes on and on and they tend to be more than two people deep in each position because they need to ensure that the job gets done if you call in sick.





Don't fret it. You don't need to be a CCIE coming out of college. Most employers would be surprised if you were at the CCNA or Network+ level by that time. It's sad, but true.





WG
Reply:try starting here hope this helps you a little bit


http://labmice.techtarget.com/networking...