Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

HP LaserJet 4100N-print queue reverts to pause

I've been trying relentlessly to get my iMac (early 2008 model) to print on an HP LaserJet 4100N. I've been able to establish the connection (via ethernet) using the IP address on the printer and configuring as Protocol LPD, HP LaserJet 4100 Series v.3010.107. All looks good, including valid connection, etc. However, when I try to print the printer queue goes into action, shows that it's "printing-copying print data-printing", but as soon as it gets to the next step "connected to printer" the job suddenly drops and reverts to pause mode. According to the information provided under printer "Options and Supplies", I have driver version 19.5. HP says that OS 10.6 comes with the necessary driver (where I started before upgrading to Mountain Lion), and that an update for Mountain Lion can be found under Apple's Software Update. But no such update is found.


My older PowerBook G4 with OS 10.6 works fine, so I'm assume it's an issue with the software/driver that's supporting Mountain Lion.


Any suggestions?

iMac, OS X Mountain Lion (10.8.2), 2008 imac A1224

Posted on Mar 15, 2013 4:54 AM

Reply
32 replies

Mar 16, 2013 9:49 AM in response to greg sahli

Funny, I was actually reading some of your posting regarding the HP 4100 series earlier this morning. So thanks for chipping in.


You'll have to forgive me as I've done so many printer set-up permutations that I can't recall exactly why I selected LPD. Could have been from posted recommendations, or that when I used LPD I was able to configure more options that resulted in what appeared to be the "correct" endpoint for the printer. I'm pretty sure I tried all of the other protocols, including HP Jetdirect(socket) and there was something funky about the outcome. But I will try again just to be sure. As for the queue name, yes, it is blank in my current configuration. So if I need to include a name, I'll try those that you suggested and see what happens. I'll report my results.


Thanks again.

Mar 16, 2013 10:17 AM in response to greg sahli

Yes, there was something funky about using HP Jetdirect(socket). When I selected it, I got an error message as follows:


Unable to verify the printer on your network.

Unable to connect to '169.254.152.33' due to an error.


The IP address in the error message is the correct address from the printer, and the Status of the ethernet connection indicates "Connected", "Ethernet is currently active and has the IP address 169.254.152.33", this according to network in system preferences. So why it can't verify is a mystery to me. As is the "error" that is causing the inability to verify.


In contrast, when using the LPD protocol I got a message that the connection and IP address was correct, and I was able to proceed with the configuration. That's why I used LPD. I will try adding some names to the queue as you suggested and will report back the outcome.

Mar 17, 2013 9:38 AM in response to greg sahli

Just wanted to add that I understand the significance of the 169 IP address as being self-assigned. But in my case, the 169 gives me a valid, active ethernet connection according to my network settings. Regardless, it's worth looking into. That is, trying to ditch the 169 and get an address that is not self-assigned, yet still valid for establishing an active ethernet connection. But I will say again, that on my laptop that's running OS 10.4, I'm using a 169 self-assigned IP address and both the network and printer connection is fine. So with OS 10.4, the self-assigned IP address does not cause any print errors. Suggesting the hang-up is related to the HP software/driver update (v.2.13) that's suppose to make their printers, including the 4100 series, compatible with Mountain Lion. At least that's my best guess. Maybe what I need to do is find someone that has Mountain Lion as their system platform, and is using an HP 4100 printer and ask them what their configuration is. If I duplicated their settings, that would be a step in the right direction.

Mar 18, 2013 4:50 AM in response to Linc Davis

Hey Linc-


I hope you don't mind my dragging you into the fire one more time. I took a look at my Terminal this morning in a continued effort to leave no stone unturned, and found this script:


LaserJet:~ Kris$


I not only appear to be logged-in to Terminal, but my name is preceeded by LaserJet, the peripheral I've been in battle with for days now (as you know). I've done repeated searches on the intenet, Apple Community, etc. for commands to log-out of Terminal and get rid of this line. And have found many derivations. But none of them seem to work. One command line that appears to work and yield the > prompt is as follows:


logout() { osascript -e 'tell application "System Events" to log out' builtin logout }


However, when I quit Terminal and re-launch, the same line appears; i.e. LaserJet:~ Kris$


Do you have any suggested command lines that can log me out of Terminal, and get rid of the LaserJet prompt? Thanks.

Mar 18, 2013 8:22 AM in response to wb4fly

The host name in the shell prompt is the value of the HOSTNAME environment variable, if set, or the result of a reverse lookup on the address of the primary network interface. You say the printer has a self-assigned address and is connected via Ethernet, so I assume your primary interface is the Wi-Fi adapter. Maybe some confusion is being caused by that setup. I suggest you do one of two things: connect the printer via USB, or connect it to your router via Ethernet so it gets a routable address, either by manual assignment or by DHCP.

Mar 18, 2013 3:42 PM in response to wb4fly

I'm with Linc - the direct-connect by ethernet is an important fact we didn't know.

Assuming you don't want to use a router, would you mind trying this:

1) on the Mac, in Network prefs, configure your Mac manually, with an IP address in the reserved Local IP address range(s) - try 192.168.3.3

2) For the printer, set a manual IP address in the same local subnet - try 192.168.3.4.


3) Now on the Mac in Print & Scan/fax prefs, add the printer using IP > HP Jetdirect and entering the printer's IP address of 192.168.3.4 and nothing in the queue name space (jetdirect protocol uses port number rather than queue name and OS X automatically uses the right port - 9100). Select printer model, if it doesn't do so automatically.

Try printing.

Mar 18, 2013 4:00 PM in response to greg sahli

In addition to what Linc Davis and greg sahli are commenting...


Disable DHCP addressing with this printer configuration, and assign a static address from whatever address block you're using. Various HP printers don't deal with that well, and the LaserJet 4100 is a pretty old box.


169.254.0.0/16 addresses shouldn't show up in normal network operations, save when clients are acquiring a DHCP address.


If you have a DHCP server configured from some box (your WiFi router?) then make sure the printer and any other static-addressed hosts are outside of the address pool being passed out by the DHCP server.

Mar 20, 2013 5:00 AM in response to MrHoffman

This is in response to Linc, Greg, and MrHoffman. Thanks to all.


Apologizes; I thought I had mentioned the set-up earlier in this thread.


1. Yes, the printer is hardwire connected directly to the computer via an ethernet cable, and there is no router (WiFi or otherwise).


2. I'm using airport and base station for wireless internet access. There is no Wi-Fi adaptor to serve as the primary interface in this set-up. However, the base station is connected to a Vonage router for phone service, and the Vonage router is connected to a TimeWarner router (my internet provider). But again, the printer is not physically connected to this set-up. The network DHCP IP address for the WiFi set-up is 192.168.15.5. Although this address was not set manually, it appears to be self-assigned and static becasue if I execute a request to "Renew DHCP Lease" the same DHCP IP address shows up. If I re-boot the Vonage and TimeWarner routers it may assign a new WiFi IP address. But the relevance of that action to solving the printer problem is unclear to me.


3. I will definitely try all the different printer configurations and IP addresses that have been suggested and report back.


4. I'm also curious about the outcome if I disable airport and my internet connection as a diagnostic test. Then configure the printer as the only network interface and see what happens. My rationale for this goes back to an earlier comment I made in this thread that the LaserJet printer works fine with my PowerBook G4 running OS 10.4. In this set-up, there is no intenet connection, and a self-assigned 169.xxx.x.x DHCP IP address presents no problem. With no WiFi interface in this set-up, any possible "confusion" goes out the window.


Now for the second issue I'm dealing with; the shelll prompt on Terminal is showing the "value of the HOSTNAME environment variable" as "LaserJet:~ Kris$".


I. I did not set this value.


II. From Linc, this may be "the result of a reverse lookup on the address of the primary network interface". If so, that would be the hardwire ethernet connection to the LaserJet printer.


III. I've been trying a plethora of commands to extract this shell prompt from Terminal, but no joy.


IV. I suspect this is related to the printer issue?


V. I'd like to extact this shell prompt from Terminal. If anyone has any suggestions re line commands I could try, please advise.


I realize I've opened-up the fire hose full bore here, so for now I'll just focus on the configuration of the IP addresses and see what happens. But if anyong suspects that the Teminal shell prompt "LaserJet:~ Kris$" is relevant and causing a hang-up for my achieving a printer connection, please chime in. If it is, I need to deal with that first. If not, I can deal with it later.


Thanks again for all the comments and suggestion. Cheers.

Mar 23, 2013 2:55 AM in response to Linc Davis

All sorts of outcomes, depending on the command. For example, one suggested command to log out the current user from Terminal that I got from http://superuser.com is as follows:


There is no "nice" way to log the current user out from Terminal in OS X. The 'messy' way of doing it is to kill that user's

loginwindow
process. It will rudely kill all processes (programs) running under your username.

Doing this is a two-step process.

  1. In terminal, run this:

    ps -Ajc | grep loginwindow

  2. Then, run

    sudo kill <pid>

    Where

    <pid>
    is the first number (second column) from the output from the above command.

When I executed this command, the screen flashed grey and logged me out of any current windows that were open (e.g. Apple Support), but left me with the same bash interactive login shell greeting as shown below:


Last login: Sat Mar 23 05:11:05 on ttys000

LaserJet:~ Kris$ ps -Ajc | grep loginwin

Last login: Sat Mar 23 05:13:04 on console

LaserJet:~ Kris$


So the command did in fact kill all programs running under my username, but did not log me out of Terminal. At least as far as I can tell from my limited understanding. I recently got a book on programming OS X Snow Leopard (Trent and McCormack), focusing on a chapter called "The Bash Terminal" and includes a section on configuring bash. It should be helpful as I'm totally new to using the bash shell (as you can tell). I now undestand what the bash shell can be used for, both interactively and script. That's a start. But as for configuring bash to change the interactive login shell greeting, which appears to be defaulting to LaserJet:~Kris$, I'm still in the dark.

HP LaserJet 4100N-print queue reverts to pause

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.