Printing 101
 

The print troubleshooting in Boeing environment is a daunting task.  Printer and printing issues involve complex systems, and numerous system components. Isolating issues can become confusing.

The Boeing customers use several different methods to print.

Windows Network printing

Mainframe Printing (Front end is windows and back end is mainframe)

Unix Printing (direct and indirect printing)

Every problem should be analyzed at it's own merit. In order to troubleshoot an issue we need to Isolate the problem ( Is this a printer issue? Is this a document printing issue? Is this a network/connectivity issue? Is this a font issue? Is this an application issue?) and determine if the issue is documented in BOSS.

Our Mission

Isolate the Problem. Here is your opportunity to narrow down the problem to a root cause.

Procedure to Troubleshoot

Step 1: Defining the Problem

• The most critical, yet most often ignored phase
• Tools required for this phase are
  • a pad of paper,
  • a pen (or pencil), and
  • good listening skills

Step 2: Isolating the Cause

Points of failure

• Narrow the problem down to the likely root cause

• Problem isolating is more of an art form than an exact science

• You are looking for the cause of the problem, not its symptoms

Typical point of failures in network printing are Printer, User/Workstation and Print queue.

In the absence of clear symptoms use the following logical order of troubleshooting: Printer --> Print Queue --> Workstation/User

Printer                           Print Queue                       PC/User

Step 3: Plan the Repair

• Start from the simplest possible solution and work toward more complex solutions
• Keep track of what steps you took and their results
• Alter plan as necessary as you go
• Repair the defect

Step 4: Documenting the Outcome

Send mail to mat.chaduhry@boeing.com with questions or comments about this web site.
Last modified: 10/23/05