7 replies
by dgust
I would suggest for a starter, that you purchase a copy of the NT Resource Kit for the OS version that you are interested in. Win2K is the latest and perhaps makes the most sense to purchase if you do not have an existing NT 4.0 or Novelle network.
I like the Preparing for the Win2K MCSE software books that are usually sold as a set. They have red covers and are quite through. They are even offered by one of the technical book sellers as a $9.95 intro book selection. They cover everything about TCP/IP and Win2K that most people should know.
by aisedohr
by robinarm
I found that a lot of the books available to me were too product specific and designed to pass exams (by remembering the answer) and not really designed to get an indepth understanding of what was happening. My advice to learning about networking would be to read as much as possible about the fundamentals. I recently moved jobs and my first network admin task was to troubleshoot a problem with a MS Proxy 2 (proxy server / firewall) that the last guy couldn't fix before leaving. I'd never worked with MS Proxy2 before so I read up on the product as much as I could. The books, however, did not really cover solving specific problem I was looking at since the book was really designed to get me through the MSCE exam. The books seemed to say "this is how to do it" but didn't cover what to do if that didn't work. I then read as much as I could on the nature of the problem area. Once I got that in-depth knowledge I could then trace the problem logically to the broken part and sort it.
For me this is the best way to learn. If you know what is meant to happen in a generic way then, regardless of the product and configuration your working with, you should be able to work out the answers logically by tracing the steps one by one. This will also make you more attractive to employers since your skills are more transferable and are not restricted to one vendors product.
by aisedohr
by ckilday
When it comes to troubleshooting, work first to isolate and identify the problem as best you can. This will keep you from wasting time attempting solutions that don't apply to the problem. Look for commonality. Look for distinction. For example,a user complains that they can't get to an application. Ok...do we have a user problem? A server problem? Or a network problem? Choose the wrong one and you can spend hours looking for something that isn't there. Do some up front detective work before providing a "fix". Find out if anyone else is experiencing the same or a similar problem. If your company has a Help Desk, call them and ask for reports of similar problems. They can probably search their trouble ticket database for you. Check and see if other users in the same location are having problems connecting to their applications. If you don't have one already, get a diagram of your network infrastructure (routers, switches, firewalls, hubs) and how they interconnect so you know where the network boundaries are. Learn what diagnostic tools and network management systems are installed and learn to use them. Compaq Insight Manager works very well for problems on Compaq servers and there are a number of network management tools out there to help you isolate your problem. Once the problem is correctly identified, the solution is usually pretty straightforward. Best wishes.
- ck
by aisedohr
by aisedohr
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending