Deciphering the many jobs of the network administrator
Dusting, vacuuming, and mopping
Managing the network users
Choosing the right tools
Getting certified
Help wanted. Network administrator to help small business get control of a network run amok. Must have sound organizational and management skills. Only moderate computer experience required. Part-time only.
Does this ad sound like one that your company should run? Every network needs a network administrator, whether the network has 2 computers or 200. Of course, managing a 200-computer network is a full-time job, whereas managing a 2-computer network isn’t. At least, it shouldn’t be.
This chapter introduces you to the boring job of network administration. Oops … you’re probably reading this chapter because you’ve been elected to be the network manager, so I’d better rephrase that: This chapter introduces you to the wonderful, exciting world of network management! Oh, boy! This is going to be fun!
Knowing What Network Administrators Do
Simply put, network administrators administer networks, which means that they take care of the tasks of installing, configuring, expanding, protecting, upgrading, tuning, and repairing the network. Network administrators take care of the network hardware, such as cables, hubs, switches, routers, servers, and clients, as well as network software, such as network operating systems, email servers, backup software, database servers, and application software. Most importantly, network administrators take care of network users by answering their questions, listening to their troubles, and solving their problems.
On a big network, these responsibilities constitute a full-time job. Large networks tend to be volatile: Users come and go, equipment fails, cables break, and life in general seems to be one crisis after another.
Smaller networks are much more stable. After you get your network up and running, you probably won’t have to spend much time managing its hardware and software. An occasional problem may pop up, but with only a few computers on the network, problems should be few and far between.
Regardless of the network’s size, all network administrators must attend to several common chores:
Equipment upgrades: The network administrator should be involved in every decision to purchase new computers, printers, or other equipment. In particular, the network administrator should be prepared to lobby for the most network-friendly equipment possible, such as network-ready printers, ample network disk storage, and an adequate backup system.
Configuration: The network administrator must put on the pocket protector whenever a new computer is added to the network. The network administrator’s job includes considering what changes to make to the cabling configuration, what computer name to assign to the new computer, how to integrate the new user into the security system, what rights to grant the user, and so on.
Software upgrades: Every once in a while, your trusty OS vendor (likely, Microsoft) releases a new version of your network operating system (NOS). The network administrator must read about the new version and decide whether its new features are beneficial enough to warrant an upgrade. In most cases, the hardest part of upgrading to a new version of your network operating system is determining the migration path — that is, how to upgrade your entire network to the new version while disrupting the network or its users as little as possible. Upgrading to a new NOS version is a major chore, so you need to carefully consider the advantages that the new version can bring.
Patches: Between upgrades, Microsoft releases patches and service packs that fix minor problems with its server operating systems. For more information, see the section “Patching Up Your Operating System and Software” later in this chapter. (Other software vendors also regularly release patches and service packs, so it isn’t only Microsoft software that must be kept up to date.)
Performance maintenance: One of the easiest traps that you can get sucked into is the quest for network speed. The network is never fast enough, and users always blame the hapless network manager. So the administrator spends hours and hours tuning and tweaking the network to squeeze out that last 2 percent of performance.
Ho-hum chores: Network administrators perform routine chores, such as backing up the servers, archiving old data, freeing up server hard drive space, and so on. Much of network administration is making sure that things keep working and finding and correcting problems before any users notice that something is wrong. In this sense, network administration can be a thankless job.
Software inventory: Network administrators are also responsible for gathering, organizing, and tracking the entire network’s software inventory. You never know when something is going to go haywire on Joe in Marketing’s ancient Windows XP computer and you’re going to have to reinstall that old copy of WordPerfect. Do you have any idea where the installation discs are?
Choosing the Part-Time Administrator
The larger the network, the more technical support it needs. Most small networks — with just a dozen or so computers — can get by with a part-time network administrator. Ideally, this person should be a closet computer geek: someone who has a secret interest in computers but doesn’t like to admit it. Someone who will take books home and read them over the weekend. Someone who enjoys solving computer problems just for the sake of solving them.
The job of managing a network requires some computer skills, but it isn’t entirely a technical job. Much of the work that the network administrator does is routine housework. Basically, the network administrator dusts, vacuums, and mops the network periodically to keep it from becoming a mess.
Here are some additional ideas on picking a part-time network administrator:
The network administrator needs to be an organized person. Conduct a surprise office inspection and place the person with the neatest desk in charge of the network. (Don’t warn anyone in advance, or everyone may mess up his or her desk intentionally the night before the inspection.)
Allow enough time for network administration. For a small network (say, no more than 20 or so computers), an hour or two each week is enough. More time is needed upfront as the network administrator settles into the job and discovers the ins and outs of the network. After an initial settling-in period, though, network administration for a small office network doesn’t take more than an hour or two per week. (Of course, larger networks take more time to manage.)
Make sure that everyone knows who the network administrator is and that the network administrator has the authority to make decisions about the network, such as what access rights each user has, what files can and can’t be stored on the server, how often backups are done, and so on.
Pick someone who is assertive and willing to irritate people. A good network administrator should make sure that backups are working before a hard drive fails and make sure that antivirus protection is in place before a virus wipes out the entire network. This policing will irritate people, but it’s for their own good.
In most cases, the person who installs the network is also the network administrator. This is appropriate because no one understands the network better than the person who designs and installs it.
The network administrator needs an understudy — someone who knows almost as much about the network, is eager to make a mark, and smiles when the worst network jobs are delegated.
The network administrator has some sort of official title, such as Network Boss, Network Czar, Vice President in Charge of Network Operations, or Dr. Network. A badge, a personalized pocket protector, or a set of Spock ears helps, too.
Establishing Routine Chores
Much of the network administrator’s job is routine stuff — the equivalent of vacuuming, dusting, and mopping. Or if you prefer, changing the oil and rotating the tires every 3,000 miles. Yes, it’s boring, but it has to be done.
Backup: The network administrator needs to make sure that the network is properly backed up. If something goes wrong and the network isn’t backed up, guess who gets the blame? On the other hand, if disaster strikes, yet you’re able to recover everything from yesterday’s backup with only a small amount of work lost, guess who gets the pat on the back, the fat bonus, and the vacation in the Bahamas?
Protection: Another major task for network administrators is sheltering your network from the evils of the outside world. These evils come in many forms, including hackers trying to break into your network and virus programs arriving through email.
Clean-up: Users think that the network server is like the attic: They want to throw files up there and leave them forever. No matter how much storage your network has, your users will fill it up sooner than you think. So the network manager gets the fun job of cleaning up the attic once in a while. Oh, joy. The best advice I can offer is to constantly complain about how messy it is up there and warn your users that spring cleaning is coming up.
Managing Network Users
Managing network technology is the easiest part of network management. Computer technology can be confusing at first, but computers aren’t nearly as confusing as people. The real challenge of managing a network is managing the network’s users.
The difference between managing technology and managing users is obvious: You can figure out computers, but you can never really figure out people. The people who use the network are much less predictable than the network itself. Here are some tips for dealing with users:
Training: Training is a key part of the network manager’s job. Make sure that everyone who uses the network understands it and knows how to use it. If the network users don’t understand the network, they may unintentionally do all kinds of weird things to it.
Respect: Never treat your network users like they’re idiots. If they don’t understand the network, it isn’t their fault. Explain it to them. Offer a class. Buy them each a copy of Networking All-in-One For Dummies and tell them to read it during their lunch hour. Hold their hands. But don’t treat them like idiots.
Aids: Make up a network cheat sheet that contains everything that the users need to know about using the network on one page. Make sure that everyone gets a copy.
Responsive: Be as responsive as possible when a network user complains of a network problem. If you don’t fix the problem soon, the user may try to fix it. You probably don’t want that.
The better you understand the psychology of network users, the more prepared you’ll be for the strangeness they often serve up. Toward that end, I recommend that you read the Diagnostic and Statistical Manual of Mental Disorders (also known as DSM-IV) cover to cover.
Patching Up Your Operating System and Software
One of the annoyances that every network manager faces is applying software patches to keep your OS and other software up to date. A software patch is a minor update that fixes small glitches that crop up from time to time, such as minor security or performance issues. These glitches aren’t significant enough to merit a new version of the software, but they’re important enough to require fixing. Most patches correct security flaws that computer hackers have uncovered in their relentless attempts to prove that they’re smarter than security programmers.
Periodically, all the recently released patches are combined into a service pack. Although the most diligent network administrators apply all patches as they’re released, many administrators just wait for the service packs.
For all versions of Windows, you can use Windows Update to apply patches to keep your operating system and other Microsoft software up to date. You can find Windows Update in the Start menu. Windows Update automatically scans your computer’s software and creates a list of software patches and other components that you can download and install. You can also configure Windows Update to automatically notify you of updates so that you don’t have to remember to check for new patches.
For larger networks, you can set up a server that runs Microsoft’s Windows Software Update Services (WSUS) to automate software updates. WSUS, which is a built-in role on Windows Server 2012 and later, essentially lets you set up your own Windows Update site on your own network. Then, you have complete control over how software updates are delivered to the computers on your network.
Discovering Software Tools for Network Administrators
Network administrators need certain tools to get their jobs done. Administrators of big, complicated, and expensive networks need big, complicated, and expensive tools. Administrators of small networks need small tools.
Some of the tools that the administrator needs are hardware tools, such as screwdrivers, cable crimpers, and hammers. The tools that I’m talking about here, however, are software tools. Here’s a sampling of the tools you’ll need:
A diagramming tool: A diagramming tool lets you draw pictures of your network. Visio (from Microsoft) is great for drawing the types of diagrams you’ll want to make as a network administrator.
A network discovery program: For larger networks, you may want to invest in a network discovery program such as Spiceworks (www.spiceworks.com) that can automatically document your network’s structure for you. These programs scan the network carefully, looking for computers, printers, routers, and other devices. They then create a database of the network components, draw diagrams for you, and chug out helpful reports.
The network’s built-in tools: Many software tools that you need to manage a network come with the network itself. As the network administrator, read through the manuals that come with your network software to see what management tools are available. For example, Windows includes a net diag command that you can use to make sure that all the computers on a network can communicate with each other. (You can run net diag from an MS-DOS prompt.) For TCP/IP networks, you can use the TCP/IP diagnostic commands summarized in Table 1-1.
System Information: This program that comes with Windows is a useful utility for network managers.
A protocol analyzer: A protocol analyzer monitors and logs the individual packets that travel along your network. (Protocol analyzers are also called packet sniffers.) You can configure the protocol analyzer to filter specific types of packets, watch for specific types of problems, and provide statistical analysis of the captured packets. Most network administrators agree that Wireshark (www.wireshark.org) is the best protocol analyzer available. And it's free!
Network Monitor: All current versions of Windows include Network Monitor, which provides basic protocol analysis and can often help solve pesky network problems.
Displays address resolution information used by the Address Resolution Protocol (ARP)
hostname
Displays your computer's host name
ipconfig
Displays current TCP/IP settings
nbtstat
Displays the status of NetBIOS over TCP/IP connections
netstat
Displays statistics for TCP/IP
nslookup
Displays Domain Name System (DNS) information
ping
Verifies that a specified computer can be reached
route
Displays the PC's routing tables
tracert
Displays the route from your computer to a specified host
Building a Library
One of Scotty’s best lines in the original Star Trek series was when he refused to take shore leave so he could get caught up on his technical journals. “Don’t you ever relax?” asked Kirk. “I am relaxing!” Scotty replied.
To be a good network administrator, you need to read computer books. Lots of them. And you need to enjoy doing it. If you’re the type who takes computer books with you to the beach, you’ll make a great network administrator.
You need books on a variety of topics. I’m not going to recommend specific titles, but I do recommend that you get a good, comprehensive book on each of the following topics:
Network security and hacking
Wireless networking
Network cabling and hardware
Ethernet
Windows Server 2008, 2012, and 2016
Windows 7, 8, 8.1, and 10
Linux
TCP/IP
DNS
Sendmail or Microsoft Exchange Server, depending on which email server you use
In addition to books, you may also want to subscribe to some magazines to keep up with what’s happening in the networking industry. Here are a few you should probably consider, along with their web addresses:
2600 The Hacker Quarterly (a great magazine on computer hacking and security): www.2600.com
The Internet is one of the best sources of technical information for network administrators. You’ll want to stock your browser’s Favorites menu with plenty of websites that contain useful networking information. In addition, you may want to subscribe to one of the many online newsletters that deliver fresh information on a regular basis via email.
Getting Certified
Remember the scene near the end of The Wizard of Oz when the Wizard grants the Scarecrow a diploma, the Cowardly Lion a medal, and the Tin Man a testimonial?
Network certifications are kind of like that. I can picture the scene now:
The Wizard: “And as for you, my network-burdened friend, any geek with thick glasses can administer a network. Back where I come from, there are people who do nothing but configure Cisco routers all day long. And they don’t have any more brains than you do. But they do have one thing you don’t have: certification. And so, by the authority vested in me by the Universita Committeeatum E Pluribus Unum, I hereby confer upon you the coveted certification of CND.”
You: “CND?”
The Wizard: “Yes, that’s, uh, Certified Network Dummy.”
You: “The Seven Layers of the OSI Reference Model are equal to the Sum of the Layers on the Opposite Side. Oh, joy, rapture! I feel like a network administrator already!”
My point is that certification in and of itself doesn’t guarantee that you really know how to administer a network. That ability comes from real-world experience — not exam crams.
Nevertheless, certification is becoming increasingly important in today’s competitive job market. So you may want to pursue certification, not just to improve your skills, but also to improve your résumé. Certification is an expensive proposition. Each test can cost several hundred dollars, and depending on your technical skills, you may need to buy books to study or enroll in training courses before you take the tests.
You can pursue two basic types of certification: vendor-specific certification and vendor-neutral certification. The major software vendors such as Microsoft and Cisco provide certification programs for their own equipment and software. CompTIA, a nonprofit industry trade association, provides the best-known vendor-neutral certification.
The following sections describe some of the certifications offered by CompTIA, Microsoft, Novell, and Cisco.
A+ is a basic certification for an entry-level computer technician. To attain A+ certification, you have to pass two exams: one on computer hardware, the other on operating systems.
Linux+ Powered by LPI covers basic Linux skills such as installation, operations, and troubleshooting. This certification is vendor neutral, so it doesn’t depend on any particular version of Linux.
Network+ is a popular vendor-neutral networking certification. It covers four major topic areas: Media and Topologies, Protocols and Standards, Network Implementation, and Network Support.
Server+ covers network server hardware. It includes details such as installing and upgrading server hardware, installing and configuring an NOS, and so on.
Cloud+ covers building cloud infrastructure.
Security+ is for security specialists. The exam topics include general security concepts, communication security, infrastructure security, basics of cryptography, and operational/organizational security.
MTA (Microsoft Technology Associate) is a general certification in either IT Infrastructure, Database, or Developer technology.
MCSE (Microsoft Certified Solutions Expert) is a prestigious certification for networking professionals who design and implement networks. To gain this certification, you have to pass several rigorous exams. Microsoft offers separate Windows Server 2008 and Windows Server 2012 certification tracks.
MCSA (Microsoft Certified Solutions Associate) is for networking professionals who administer existing networks.
CCENT (Cisco Certified Entry Network Technician) is an entry-level certification. A CCENT should be able to install, configure, and operate Cisco equipment for branch-level networks.
CCNA (Cisco Certified Network Associate) is an entry-level apprentice certification. A CCNA should be able to install, configure, and operate Cisco equipment for small networks (under 100 nodes).
CCNP (Cisco Certified Network Professional) is a professional-level certification for Cisco equipment. A CCNP should be able to install, configure, and troubleshoot Cisco networks of virtually any size. Several variants are available for cloud, data center, routing, security, service provider, and routing.
CCDP (Cisco Certified Design Professional) is for network design professionals. The CCNA certification is a prerequisite for the CCDP.
CCDE (Cisco Certified Design Expert) is an expert-level design certification.
CCIE (Cisco Certified Internetwork Expert) is an expert-level certification, which can be had in several varieties, including routing, security, wireless, and service provider.
CCAr: (Cisco Certified Architect) is the top dog of Cisco certifications.
CCT (Cisco Certified Technician) is a certification for those who can diagnose and repair Cisco equipment.
And much more! There are many more Cisco certifications to choose from, including certification for security, voice technology, wireless networking, and more.
Gurus Need Gurus, Too
No matter how much you know about computers, plenty of people know more than you do. This rule seems to apply at every rung of the ladder of computer experience. I’m sure that a top rung exists somewhere, occupied by the world’s best computer guru. However, I’m not sitting on that rung, and neither are you. (Not even Bill Gates is sitting on that rung. In fact, Bill Gates got to where he is today by hiring people on higher rungs.)
As the local computer guru, one of your most valuable assets can be a knowledgeable friend who’s a notch or two above you on the geek scale. That way, when you run into a real stumper, you have a friend to call for advice. Here are some tips for handling your own guru:
In dealing with your own guru, don’t forget the Computer Geek’s Golden Rule: “Do unto your guru as you would have your own users do unto you.” Don’t pester your guru with simple stuff that you just haven’t spent the time to think through. If you have thought it through and can’t come up with a solution, however, give your guru a call. Most computer experts welcome the opportunity to tackle an unusual computer problem. It’s a genetic defect.
If you don’t already know someone who knows more about computers than you do, consider joining your local PC users’ group. The group may even have a subgroup that specializes in your networking software or may be devoted entirely to local folks who use the same networking software that you use. Odds are good that you’re sure to make a friend or two at a users’ group meeting. Also, you can probably convince your boss to pay any fees required to join the group.
If you can’t find a real-life guru, try to find an online guru. Check out the various computing newsgroups on the Internet. Subscribe to online newsletters that are automatically delivered to you via email.
Helpful Bluffs and Excuses
As network administrator, you just won’t be able to solve a problem sometimes, at least not immediately. You can do two things in this situation. The first is to explain that the problem is particularly difficult and that you’ll have a solution as soon as possible. The second solution is to look the user in the eyes and, with a straight face, try one of these phony explanations:
Blame it on the version of whatever software you’re using. “Oh, they fixed that with version 39.”
Blame it on cheap, imported memory chips.
Blame it on Democrats. Or Republicans. Doesn’t matter.
Blame it on oil company executives.
Blame it on global warming.
Hope that the problem wasn’t caused by stray static electricity. Those types of problems are very difficult to track down. Tell your users that not properly discharging themselves before using their computers can cause all kinds of problems.
You need more memory.
You need a bigger hard drive.
You need a faster processor.
Blame it on Jar-Jar Binks.
You can’t do that in Windows 10.
You can only do that in Windows 10.
Could be a virus.
Or sunspots.
No beer and no TV make Homer something something something… .
Deciphering the many jobs of the network administrator
The better you understand the psychology of network users, the more prepared you’ll be for the strangeness they often serve up. Toward that end, I recommend that you read the Diagnostic and Statistical Manual of Mental Disorders (also known as DSM-IV) cover to cover.