Customer called with a error of 79.00. I was told by tech support that it could be anything. We started out by increasing the memory. no change. We replaced the formatter and it solved it. Three weeks went by and now it's back. Any insight greatly appreciated!!
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Hp 8000/error 79 1
- Thread starter mandoruby
- Start date
-
1
- #2
From HP:
Initial troubleshooting to verify printer functionality
The first step with any HP LaserJet troubleshooting is to isolate the printer from the network and any software applications that may be causing the problem. The reason for testing the printer in this "stand alone" mode is to verify it is working properly.
To test the printer, perform the following:
Turn the printer off and unplug any parallel cable from the formatter.
Unplug the network cable from the HP Jetdirect card and then remove the card from the formatter.
Power the printer on.
After the printer reaches a Ready status, print the following test pages:
Configuration page or Test print (list of installed options)
Event Log (list of most recent printer events to aid with troubleshooting)
Menu Map (lists Printer settings)
Analyze the results of these tests
If the printer was not able to successfully print the internal pages above, the problem has been isolated to the printer. The troubleshooting should now be concentrated on the printer itself. If needed contact HP support or a local service provider for further assistance.
Printer functionality has been proven
If the printer can successfully print the internal pages, printer functionality has been established and further network/application troubleshooting will be necessary to determine the cause of the communication issue.
To properly troubleshoot the issue it may be necessary have access to any or all of the following information to help narrow down the cause. It may be necessary to get a systems administrator involved, in many companies they are the only individuals with access to all of this information along with the network access/administrator privileges that may potentially be needed.
NOTE: This information will also be very useful if it is necessary to call HP support for further assistance.
Operating system installed including service pack version (if applicable)
Affected application and version, along with any modifications or patches to the application
Driver used (PCL6, PCL5e, or PS). Verify correct drivers for the printer model is being used.
Driver installation method (local driver install vs. point-and-print install)
Port used, for example Microsoft(R) Standard TCP/IP port versus Hewlett-Packard TCP/IP port
HP Jetdirect firmware version, listed on the EIO page
Printer firmware version, listed on the Configuration/Test page
Protocols enabled (TCP/IP, IPX/SPX, and AppleTalk). Listed on the EIO page
Physical location of printer and general environment
Location of printer on network, for example is it on the same segment as the server
NOTE: It is possible to have multiple issues at the same time, that is both network and application problems simultaneously or they may be related. Because of this, the next step in the troubleshooting process is to attempt to prove basic network communication functionality.
Performing basic network communication functionality
If the Idle Timeout setting has been modified from the default setting (reduced) this can cause network communications issues. This should be checked before proceeding with the network troubleshooting. It can be checked and modified if necessary two ways:
From the control panel of the printer. This setting is located in the I/O menu.
By bringing up the Embedded Web Server (EWS) of the Jetdirect card in a web browser. This setting is located on the Network Settings, TCP/IP tab of the EWS. The value for this setting should be at least 120 seconds.
Now, try to Ping the printer over the network. Ping can be used in HP Jetdirect print servers to test if it they are "seen" on the network. If these tests fail, this usually indicates a hardware connection or configuration problem (for example, a hub, router, switch, patch panel or cable problem). To use the Ping command, do the following:
Bring up a command prompt window and type the ping ipaddress of the printer. For example, if the TCP/IP address of the HP Jetdirect card is 192.168.192.191, go to a command prompt, and type ping 192.168.192.191 and then press the Enter key on the keyboard.
If a ping reply is received a network handshake occurred and this proves network communication. Proceed to the next section to test communication using the embedded Web server (EWS) (if supported, depends on printer model).
If the Ping test is successful and neither the printer nor HP Jetdirect card has EWS functionality, then proceed to test basic printer driver functionality section.
If the Ping tests fail, this usually indicates a hardware connection or configuration problem (for example, a hub, router, switch, patch panel or cable problem). The troubleshooting should be concentrated in these areas.
Testing for communication functionality using the EWS
The EWS can be used to test communication to the printer or the printer's HP Jetdirect card. On printers such as an HP Color LaserJet 8550 that do not have EWS functionality built into the printer communication to the EWS, the HP Jetdirect card can be tested. On a printer such as the HP LaserJet 9000 that has a built in EWS, the communication will be tested with the EWS on the printer. Either method will verify communication functionality to the printer.
NOTE: The EWS requires that Java(TM) Virtual Machine be installed. The user will be prompted to install it when trying to access the printer using the EWS. If it is not installed, the EWS will not work.
If the printer or HP Jetdirect card has an EWS, the next step is to attempt communication with the EWS. It is important to understand that some HP Jetdirect cards have their own EWS and some printers do as well. Click here for detailed information on the specific HP Jetdirect cards and Firmware versions that are required to enable EWS functionality in the HP Jetdirect card ( All of the newer cards (EIO HP Jetdirect cards) do have EWS functionality built in. The following printers have EWS functionality built in:
HP LaserJet 9000 printers, including 9000 MFP
HP LaserJet 4100 printers, including 4100 MFP
HP LaserJet 5100 printers
HP LaserJet 8150 (limited functionality)
HP Color LaserJet 4550 printers
HP Color LaserJet 4600 printers
HP Color LaserJet 5500 printers
NOTE: Some Proxy servers can cause problems trying to communicate with the EWS. This can be fixed by adding the IP address of the printer to the exceptions box in Internet Explorer. This bypasses the proxy server. This setting is located by clicking Start, Settings, Control Panel, Internet Options, and Connections. In proxy settings in ie you can bypass the server by adding the IP address into
exceptions.
Accessing the printer using the EWS
To access the printer using the EWS, do the following:
Open a Web browser and type the IP Address of the printer like the following example:
Press Enter on the keyboard or click the Go button in the Web browser.
The EWS will be displayed in the Web browser. For more information on how to configure and use the EWS, click here to view the EWS User Guide.
NOTE: Adobe(R) Acrobat(R) Reader is required to view the EWS User Guide. Click here to download Adobe Acrobat Reader if it is not already installed on your system.
Communicating with an optional HP Jetdirect internal print server
If the printer contains an optional HP Jetdirect 10/100TX print server, check to see that the print server was able to link to the network:
Check the link-speed indicators (10 or 100) on the print server. If both are off, the print server failed to link to the network.
Check the Jetdirect configuration page, which was printed when the steps under "To print a configuration page" were performed. The message "LOSS OF CARRIER ERROR" indicates that the print server failed to link to the network.
If the print server failed to link, verify that all cables are correctly connected. If all cables are correctly connected and the print server still fails to link, turn the printer off and then on. After READY appears on the control panel, verify that the print server has connected. If the printer server did not connect, follow the steps below to reconfigure the print server:
Remove the HP Jetdirect 10/100TX print server. For testing purposes try setting the Jetdirect card for 10 Mbps (megabits per second) and half-duplex.
Use jumpers P1, P2, and P3 to manually configure the print server for either 10 or 100 Mbps (megabits per second) link speed, and Full- or Half-duplex operation according to the table below:
NOTE: The following instructions are for a 600 series or older Jetdirect card. The newer 610 and 615 series Jetdirect cards do not have jumpers; to make the following changes to these cards use the EWS.
Print server operation
Jumper P1
Jumper P2
Jumper P3
Autonegotiation Enabled
AUTO
--
--
100 Half-duplex
(not AUTO)
100
H
100 Full-duplex
(not AUTO)
100
(not H)
10 Half-duplex
(not AUTO)
(not 100)
H
10 Full-duplex
(not AUTO)
(not 100)
(not H)
Reinstall the print server.
Verify that the configuration of the connecting network device (such as a 10/100TX network switch) matches. For example, to set the print server for 100TX Full-duplex operation, the port on the network switch must also be set for 100TX Full-duplex operation.
Testing basic printer driver communication functionality
Before testing driver communication, verify that the latest drivers from the Web ( have been installed for the printer having the issue.
Check the driver versions for the installed drivers by going into the driver properties and clinking the About tab (see Figures 2 and 3) against the latest versions on the Web. After doing this, go through all the Driver settings to make sure the drivers are properly configured for the options installed in the printer.
NOTE: Many issues are resolved simply by updating to the latest drivers.
To test basic printer driver functionality perform the following:
NOTE: Before testing with the PostScript (PS)(R) driver make sure that the PS ERROR HANDLING is turned ON at the control panel of the printer.
Verify the latest drivers from the Web are installed.
Print a test page from each of the latest HP drivers.
If any of these tests fail, install the nearest equivalent Microsoft provided driver, this typically comes inbox with operating system.
If the test page does print successfully, print driver communication functionality has been established. The next step is to test basic application/driver functionality, see the next section.
Testing basic application and driver functionality
Before testing basic application and driver functionality try disabling SNMP status in the driver for testing purposes
Creating a spool (SPL) file
NOTE: To correctly capture spool (SPL) files the parallel cable being used must be IEEE1284 compliant. Also, for Type C parallel connections the cable cannot be more than 10 meters (approx 32 feet) in length and for Type B connections the maximum cable length is 3 meters (approx 9 feet).
To capture a spool file perform the following within the driver. This requires spooling through Microsoft Windows NT 4.0, Windows 2000, or Windows XP.
When using the PS driver it will be necessary to make another driver modification before capturing the spool (SPL) file.
If running Microsoft® Windows 2000 or XP, go to Printing Preferences, Advanced Printing Features, Document Options = Disable Advanced Printing Features.
If running Windows NT 4.0, go to Document Defaults, Advanced, and Document Options = Disable Advanced Printing Features.
This is necessary when capturing the spool (SPL) file, without this feature disabled the information in the file is in the EMF format, which would be unusable. To capture the spool (SPL) files perform the following:
Go to the Properties of the target printer driver.
Select the Scheduling (Windows NT 4.0) or Advanced (Windows 2000 and Windows XP) tab.
Check Keep Documents After They Have Printed. Once the driver has spooled the print job, these associated SPL files will be stored at the computer that did the spooling in the following directory: "WINNT\System32\spool\printers"
NOTE: This information will also be very useful if it is necessary to call HP support for further assistance.
Test a print to file and SPL (spool) file
Once captured the print-to-file and/or the SPL (spool) file, these files can be tested via another communication path or to another printer. With a parallel cable attached to the machine containing the print-to-file and/or SPL file, copying the file directly to the printer can be performed. By performing this troubleshooting procedure, the network is bypassed and any issues that may be related to it.
There are three basic ways to do this. The following is the preferred order:
Copy the file down to the printer directly.
Open a DOS session within Windows.
At the prompt, type COPY filepath\filename LPT1
While connected to the network, obtain the IP address of the printer and utilize the FTP command to get the file to the printer in order to bypass a large portion of the Windows spooling component.
NOTE: Click here for additional information and command strings for FTP (
While connected to the network, obtain the IP address of the printer and utilize the LPR command to get the file to the printer in order to bypass a large portion of the Windows spooling component. For this to work, "Simple TCP/IP services" must be installed in the operating system. To use the LPR command to send a file to the printer, do the following:
Open a DOS session within Windows.
At the command prompt, type LPR -Sipaddress -PRAW filepath\filename
SPL files and print to file test results
The results of sending the file directly to the printer are crucial to understanding the functionality of the network/application communication. If the print-to-file and/or SPL file successfully print, the printer/driver functionality and basic communication has been proven. If the problem still persists after performing all of the troubleshooting outlined in this document, then contact HP support or a local service provider for further assistance.
Initial troubleshooting to verify printer functionality
The first step with any HP LaserJet troubleshooting is to isolate the printer from the network and any software applications that may be causing the problem. The reason for testing the printer in this "stand alone" mode is to verify it is working properly.
To test the printer, perform the following:
Turn the printer off and unplug any parallel cable from the formatter.
Unplug the network cable from the HP Jetdirect card and then remove the card from the formatter.
Power the printer on.
After the printer reaches a Ready status, print the following test pages:
Configuration page or Test print (list of installed options)
Event Log (list of most recent printer events to aid with troubleshooting)
Menu Map (lists Printer settings)
Analyze the results of these tests
If the printer was not able to successfully print the internal pages above, the problem has been isolated to the printer. The troubleshooting should now be concentrated on the printer itself. If needed contact HP support or a local service provider for further assistance.
Printer functionality has been proven
If the printer can successfully print the internal pages, printer functionality has been established and further network/application troubleshooting will be necessary to determine the cause of the communication issue.
To properly troubleshoot the issue it may be necessary have access to any or all of the following information to help narrow down the cause. It may be necessary to get a systems administrator involved, in many companies they are the only individuals with access to all of this information along with the network access/administrator privileges that may potentially be needed.
NOTE: This information will also be very useful if it is necessary to call HP support for further assistance.
Operating system installed including service pack version (if applicable)
Affected application and version, along with any modifications or patches to the application
Driver used (PCL6, PCL5e, or PS). Verify correct drivers for the printer model is being used.
Driver installation method (local driver install vs. point-and-print install)
Port used, for example Microsoft(R) Standard TCP/IP port versus Hewlett-Packard TCP/IP port
HP Jetdirect firmware version, listed on the EIO page
Printer firmware version, listed on the Configuration/Test page
Protocols enabled (TCP/IP, IPX/SPX, and AppleTalk). Listed on the EIO page
Physical location of printer and general environment
Location of printer on network, for example is it on the same segment as the server
NOTE: It is possible to have multiple issues at the same time, that is both network and application problems simultaneously or they may be related. Because of this, the next step in the troubleshooting process is to attempt to prove basic network communication functionality.
Performing basic network communication functionality
If the Idle Timeout setting has been modified from the default setting (reduced) this can cause network communications issues. This should be checked before proceeding with the network troubleshooting. It can be checked and modified if necessary two ways:
From the control panel of the printer. This setting is located in the I/O menu.
By bringing up the Embedded Web Server (EWS) of the Jetdirect card in a web browser. This setting is located on the Network Settings, TCP/IP tab of the EWS. The value for this setting should be at least 120 seconds.
Now, try to Ping the printer over the network. Ping can be used in HP Jetdirect print servers to test if it they are "seen" on the network. If these tests fail, this usually indicates a hardware connection or configuration problem (for example, a hub, router, switch, patch panel or cable problem). To use the Ping command, do the following:
Bring up a command prompt window and type the ping ipaddress of the printer. For example, if the TCP/IP address of the HP Jetdirect card is 192.168.192.191, go to a command prompt, and type ping 192.168.192.191 and then press the Enter key on the keyboard.
If a ping reply is received a network handshake occurred and this proves network communication. Proceed to the next section to test communication using the embedded Web server (EWS) (if supported, depends on printer model).
If the Ping test is successful and neither the printer nor HP Jetdirect card has EWS functionality, then proceed to test basic printer driver functionality section.
If the Ping tests fail, this usually indicates a hardware connection or configuration problem (for example, a hub, router, switch, patch panel or cable problem). The troubleshooting should be concentrated in these areas.
Testing for communication functionality using the EWS
The EWS can be used to test communication to the printer or the printer's HP Jetdirect card. On printers such as an HP Color LaserJet 8550 that do not have EWS functionality built into the printer communication to the EWS, the HP Jetdirect card can be tested. On a printer such as the HP LaserJet 9000 that has a built in EWS, the communication will be tested with the EWS on the printer. Either method will verify communication functionality to the printer.
NOTE: The EWS requires that Java(TM) Virtual Machine be installed. The user will be prompted to install it when trying to access the printer using the EWS. If it is not installed, the EWS will not work.
If the printer or HP Jetdirect card has an EWS, the next step is to attempt communication with the EWS. It is important to understand that some HP Jetdirect cards have their own EWS and some printers do as well. Click here for detailed information on the specific HP Jetdirect cards and Firmware versions that are required to enable EWS functionality in the HP Jetdirect card ( All of the newer cards (EIO HP Jetdirect cards) do have EWS functionality built in. The following printers have EWS functionality built in:
HP LaserJet 9000 printers, including 9000 MFP
HP LaserJet 4100 printers, including 4100 MFP
HP LaserJet 5100 printers
HP LaserJet 8150 (limited functionality)
HP Color LaserJet 4550 printers
HP Color LaserJet 4600 printers
HP Color LaserJet 5500 printers
NOTE: Some Proxy servers can cause problems trying to communicate with the EWS. This can be fixed by adding the IP address of the printer to the exceptions box in Internet Explorer. This bypasses the proxy server. This setting is located by clicking Start, Settings, Control Panel, Internet Options, and Connections. In proxy settings in ie you can bypass the server by adding the IP address into
exceptions.
Accessing the printer using the EWS
To access the printer using the EWS, do the following:
Open a Web browser and type the IP Address of the printer like the following example:
Press Enter on the keyboard or click the Go button in the Web browser.
The EWS will be displayed in the Web browser. For more information on how to configure and use the EWS, click here to view the EWS User Guide.
NOTE: Adobe(R) Acrobat(R) Reader is required to view the EWS User Guide. Click here to download Adobe Acrobat Reader if it is not already installed on your system.
Communicating with an optional HP Jetdirect internal print server
If the printer contains an optional HP Jetdirect 10/100TX print server, check to see that the print server was able to link to the network:
Check the link-speed indicators (10 or 100) on the print server. If both are off, the print server failed to link to the network.
Check the Jetdirect configuration page, which was printed when the steps under "To print a configuration page" were performed. The message "LOSS OF CARRIER ERROR" indicates that the print server failed to link to the network.
If the print server failed to link, verify that all cables are correctly connected. If all cables are correctly connected and the print server still fails to link, turn the printer off and then on. After READY appears on the control panel, verify that the print server has connected. If the printer server did not connect, follow the steps below to reconfigure the print server:
Remove the HP Jetdirect 10/100TX print server. For testing purposes try setting the Jetdirect card for 10 Mbps (megabits per second) and half-duplex.
Use jumpers P1, P2, and P3 to manually configure the print server for either 10 or 100 Mbps (megabits per second) link speed, and Full- or Half-duplex operation according to the table below:
NOTE: The following instructions are for a 600 series or older Jetdirect card. The newer 610 and 615 series Jetdirect cards do not have jumpers; to make the following changes to these cards use the EWS.
Print server operation
Jumper P1
Jumper P2
Jumper P3
Autonegotiation Enabled
AUTO
--
--
100 Half-duplex
(not AUTO)
100
H
100 Full-duplex
(not AUTO)
100
(not H)
10 Half-duplex
(not AUTO)
(not 100)
H
10 Full-duplex
(not AUTO)
(not 100)
(not H)
Reinstall the print server.
Verify that the configuration of the connecting network device (such as a 10/100TX network switch) matches. For example, to set the print server for 100TX Full-duplex operation, the port on the network switch must also be set for 100TX Full-duplex operation.
Testing basic printer driver communication functionality
Before testing driver communication, verify that the latest drivers from the Web ( have been installed for the printer having the issue.
Check the driver versions for the installed drivers by going into the driver properties and clinking the About tab (see Figures 2 and 3) against the latest versions on the Web. After doing this, go through all the Driver settings to make sure the drivers are properly configured for the options installed in the printer.
NOTE: Many issues are resolved simply by updating to the latest drivers.
To test basic printer driver functionality perform the following:
NOTE: Before testing with the PostScript (PS)(R) driver make sure that the PS ERROR HANDLING is turned ON at the control panel of the printer.
Verify the latest drivers from the Web are installed.
Print a test page from each of the latest HP drivers.
If any of these tests fail, install the nearest equivalent Microsoft provided driver, this typically comes inbox with operating system.
If the test page does print successfully, print driver communication functionality has been established. The next step is to test basic application/driver functionality, see the next section.
Testing basic application and driver functionality
Before testing basic application and driver functionality try disabling SNMP status in the driver for testing purposes
Creating a spool (SPL) file
NOTE: To correctly capture spool (SPL) files the parallel cable being used must be IEEE1284 compliant. Also, for Type C parallel connections the cable cannot be more than 10 meters (approx 32 feet) in length and for Type B connections the maximum cable length is 3 meters (approx 9 feet).
To capture a spool file perform the following within the driver. This requires spooling through Microsoft Windows NT 4.0, Windows 2000, or Windows XP.
When using the PS driver it will be necessary to make another driver modification before capturing the spool (SPL) file.
If running Microsoft® Windows 2000 or XP, go to Printing Preferences, Advanced Printing Features, Document Options = Disable Advanced Printing Features.
If running Windows NT 4.0, go to Document Defaults, Advanced, and Document Options = Disable Advanced Printing Features.
This is necessary when capturing the spool (SPL) file, without this feature disabled the information in the file is in the EMF format, which would be unusable. To capture the spool (SPL) files perform the following:
Go to the Properties of the target printer driver.
Select the Scheduling (Windows NT 4.0) or Advanced (Windows 2000 and Windows XP) tab.
Check Keep Documents After They Have Printed. Once the driver has spooled the print job, these associated SPL files will be stored at the computer that did the spooling in the following directory: "WINNT\System32\spool\printers"
NOTE: This information will also be very useful if it is necessary to call HP support for further assistance.
Test a print to file and SPL (spool) file
Once captured the print-to-file and/or the SPL (spool) file, these files can be tested via another communication path or to another printer. With a parallel cable attached to the machine containing the print-to-file and/or SPL file, copying the file directly to the printer can be performed. By performing this troubleshooting procedure, the network is bypassed and any issues that may be related to it.
There are three basic ways to do this. The following is the preferred order:
Copy the file down to the printer directly.
Open a DOS session within Windows.
At the prompt, type COPY filepath\filename LPT1
While connected to the network, obtain the IP address of the printer and utilize the FTP command to get the file to the printer in order to bypass a large portion of the Windows spooling component.
NOTE: Click here for additional information and command strings for FTP (
While connected to the network, obtain the IP address of the printer and utilize the LPR command to get the file to the printer in order to bypass a large portion of the Windows spooling component. For this to work, "Simple TCP/IP services" must be installed in the operating system. To use the LPR command to send a file to the printer, do the following:
Open a DOS session within Windows.
At the command prompt, type LPR -Sipaddress -PRAW filepath\filename
SPL files and print to file test results
The results of sending the file directly to the printer are crucial to understanding the functionality of the network/application communication. If the print-to-file and/or SPL file successfully print, the printer/driver functionality and basic communication has been proven. If the problem still persists after performing all of the troubleshooting outlined in this document, then contact HP support or a local service provider for further assistance.
- Thread starter
- #3
- Status
Similar threads
- Locked
- Question
- Locked
- Question
