Previous | Table of Contents | Next |
The underpinning of a file and print client is, of course, the vendor-supplied client you load on the workstation. (Typically, the server vendor supplies you with a setup program, which then automatically loads and configures the client on your workstation. Its really easy.) The first troubleshooting step for file and print is to verify that the client is the correct version. Youll have to check with the vendor for the latest scoop on this, but notice that I say correct, not latest. Its enough to know that two given workstations (one of which is broken) have identical versions of the client.
How do clients work? Even though the clients may look simple, they are, of course, complex internally. Lets look at the NetWare client as an example. In order to make your file sharing and print sharing effortless for you, here are some of the things the client must deal with:
Troubleshooting these pieces and parts on an individual basis is more trouble than its worthjust realize that the client is more complex than it seems.
An interesting note is that the DOS version of the NetWare client used to load all these capabilities separately, to allow you to pick and choose which ones you wanted (and thus saving memory). The modules were called VLMs, or Virtual Loadable Modules.
File and print client software is complex enough that its pretty vulnerable to domino-effect problems from other workstation software. Verifying good workstation configurations is also really important for file and print troubleshooting.
This section covers the major types of problems you can encounter on file and print systems:
If you surveyed the entire country and asked administrators which network problem they found most aggravating, my bet is that one of the top answers would be network print problems. Therefore, we as troubleshooters want to fix those problems, pronto.
Unfortunately, many delayed resolutions to printer problems are due to insufficient printer documentation. When Cassie and friends refer to the broken printer as Cassies printer, that means something to them, but to you as a network troubleshooter, it means zero (unless its followed by Oh yeah, thats the finance-10 printer on the PENELOPE server).Having a table of departments and printers works sometimes, but I find it more convenient when the printer installer slaps a label on it with server/directory/queue name information. That way, you can ask the user, particularly at a remote location, Whats the printer label say? and be able to immediately start looking in the right place.
Lets take a look at what network printing usually entails. You connect to a network printer queue by browsing servers or the directory services tree, and you install drivers appropriate to that printer. So far, this is just like installing a printer that lives on your PCs LPT1 port, right? The only difference is that youre specifying some spooky network location rather than a local port.
What happens when you try to print? To answer that, lets run through these steps:
With five potential points of failure (more, in some cases), its no wonder that print problems can be a big deal. Thankfully, most printer problems can be handled by divide-and-conquer techniques and the Sesame Street method. That is, youll want to determine whether other users can connect to the printer, as well as whether the user who reported the problem can print to another printer. Lucky for you, Im going to divide and conquer this entire process for you by breaking it down into five easy troubleshooting steps.
Previous | Table of Contents | Next |