My only input into this is there is a huge difference between certifications and experience. If you have to study, and cram for an exam because you dont know the material, then you may get the certification, but once you are asked to use the information you can be severly burned. Take your time getting the Certs, by knowing the material. Knowing more then what you have on paper is always better then claiming you know it, being put on the spot, and getting fired because you didnt know a simple routing statement because you crammed and forgot it all.
On a side note, also look into the CNX certification, it is supported by NAI (Yea Sniffers !!!, /me hugs his dolche) and the Entry level exam seems to cover networking and subnetting in general more in depth then the CCNA. Cisco is not the only networking equipment out there.
Knowing equipment and networking isnt the only key also, integration is the most important factor.
Best bet is find 2 or 3 machines, load up different operating systems, learn IP first. It is the common ground in network nowadays, then start learning how it works in depth (route statements, and security) from there you can figure out how each machine interacts, Dont forget to learn how to use the operating systems also, knowing what a collision on the wire looks like in bits doesnt help you if the performance issue is a slow harddrive in a webserver.
spidey, in reguards to Novell being the best.... I like it and all, but ever since 3.12 (okay, 3.2 with y2k pathces) it has been downhill, Novell is not an app server, but for file and print it can be beat
- Arcnet and Novell 2.2 nondedicated on a 286