I’m running Suse 10.3. I bought an HP Laserjet P2055DN which I connected to my pc–as well as two Windows machines running XP–through a router (Linksys Etherfast Cable/DSL Router, mod. # BEFSR41). I used the CUPS web interface (after some advice here in another thread) to get it working.
It works with the Windows PCs just fine–and always does. It worked with my linux PC at first. But a few days later, nothing I tried to print would. With some help from folks here I got it working again–changed the URL for the printer from ipp to ldp, which seemed to do the trick.
Yesterday I tried to print again for the first time in a couple of weeks–and nothing. I get the same “Network host 192.168.1.104 is busy, down, or unreachable. Will try again in 30 seconds” error message. That’s all I EVER get on my PC, but the Windows machines can print with no problem.
I’ve been getting suggestions in a thread elsewhere on the forums here, but one comment suggested a new thread in hopes of getting some help from one of the network gurus–so here I am.
Can anyone tell me how to fix this–and keep it fixed? (We sometimes unplug the printer from the router to plug a Windows laptop into it for netsurfing. Is that causing a problem?)
> Yesterday I tried to print again for the first time in a couple of
> weeks–and nothing. I get the same “Network host 192.168.1.104 is busy,
> down, or unreachable. Will try again in 30 seconds” error message.
> That’s all I EVER get on my PC, but the Windows machines can print with
> no problem.
That message looks like more a network connection problem than a printer
setup problem. Whenever you get that message from your printer, try to
connect to the jetadmin embedded web server (http://192.168.1.104) and
check if you can get the printer setup page (or just ping the
printer “ping -c 3 192.168.1.104”). If network is good and printer is O.K.,
you should get a positive reply.
Is the printer setup to use a static IP or is getting its address from any
dhcp server?
> Can anyone tell me how to fix this–and keep it fixed? (We sometimes
> unplug the printer from the router to plug a Windows laptop into it for
> netsurfing. Is that causing a problem?)
I have some hp laserjet printers at the office (ethernet connected) and also
some openSUSE 10.3 boxes running fine in the network and had not
experienced such issue after plugging/unplugging the ethernet cable :-?
When I click on that URL I get a firefox error message–the “Problem loading page” page. I always gets that.
and check if you can get the printer setup page (or just ping the
printer “ping -c 3 192.168.1.104”). If network is good and printer is O.K., you should get a positive reply.
When I ping as you suggest, I get the following response:
PING 192.168.1.104 (192.168.1.104) 56(84) bytes of data.
64 bytes from 192.168.1.104: icmp_seq=1 ttl=64 time=0.112 ms
64 bytes from 192.168.1.104: icmp_seq=2 ttl=64 time=0.100 ms
64 bytes from 192.168.1.104: icmp_seq=3 ttl=64 time=0.107 ms
— 192.168.1.104 ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.100/0.106/0.112/0.009 ms
…so it look that’s working.
Is the printer setup to use a static IP or is getting its address from any dhcp server?
>> That message looks like more a network connection problem than a
>> printer
>> setup problem. Whenever you get that message from your printer, try to
>> connect to the jetadmin embedded web server (http://192.168.1.104)
>
> When I click on that URL I get a firefox error message–the “Problem
> loading page” page. I always gets that.
That should not happen.
Look, if you cannot access into the printer web front-end, I’d expect Cups
has also problems to connect to the printer. You have to solve this first.
Can you reach the web front-end from another machine or is just the openSUSE
one which is failing?
>> and check if you can get the printer setup page (or just ping the
>> printer “ping -c 3 192.168.1.104”). If network is good and printer is
>> O.K., you should get a positive reply.
>
> When I ping as you suggest, I get the following response:
>
> PING 192.168.1.104 (192.168.1.104) 56(84) bytes of data.
> 64 bytes from 192.168.1.104: icmp_seq=1 ttl=64 time=0.112 ms
> 64 bytes from 192.168.1.104: icmp_seq=2 ttl=64 time=0.100 ms
> 64 bytes from 192.168.1.104: icmp_seq=3 ttl=64 time=0.107 ms
>
> — 192.168.1.104 ping statistics —
> 3 packets transmitted, 3 received, 0% packet loss, time 2000ms
> rtt min/avg/max/mdev = 0.100/0.106/0.112/0.009 ms
>
> …so it look that’s working.
That means “some ethernet card at 192.168.1.104” is responding to pings, but
can be a computer or another device or just the interface of your printer,
which is responding, but the printer itself can have any problem
>> Is the printer setup to use a static IP or is getting its address from
>> any dhcp server?
>
> I have no idea. How would I tell?
Ask your network administrator :-).
Another thing you can do is reviewing the settings of that printer in
another machine (windows or linux based). That way you can check if the IP
address is setup the same way.
If you read the printer manual, you will find a section on setting up the printer using the printer’s own setup buttons. It will also allow you to print a configuration page that will give you all the relevant details about networking.
Since you always need to access the printer using its ipaddress, make sure you set it up to use a fixed address.
As Camaleón says, hpjetdirect is universally supported with most operating systems and very rarely give problems.
If you print from a winxp machine, check what settings winxp is using.
After reading Camaleon’s comment, I went to my wife’s Windows PC and opened up the HP toolkit and checked all the settings to see what I could learn.
I learned that I had the IP address wrong on my PC. …1.104 instead of (the correct) …1.102.
That’s all it was. I could have sworn I had it right, but obviously not so much. Changing the IP address made all the difference. I can reach that URL and the control panel with no problem. The printer responds.
So…nothing wrong with my OS, the printer, or the network. Just user stupidity.
Anyway, thanks for the help, y’all. I appreciate it!
