HP Laserjet 5000N goes offline after wireless network installed

[LurfysMa]

We have an HP LaserJet 5000N attached to a cat5 cable on a p2p LAN. We
have two PCs connected to the LAN both by cat5 cables. One is a
workstation and the other is a laptop. Both are HP and 5 years old
running Windows 2000.

The router is part of the cable modem that came with the Comcast
broadband service. This setup has been working perfectly for several
years.

A week ago, I hired a tech from a local computer support company to
install a wireless network. He brought a Buffalo Air Station Wireless
G Router and Access Point. That installation seemed go well.

My laptop, a 5 year old HP Omnibook 6000, does not have wireless built
in so the tech brought a Netgear 108Mbps Wirepess PC card. That
installation seemed to go smoothly as well and I was able to access
the internet from anywhere in the house.

I don;t think this is relevant, but we also have a Canon S830D ink jet
photo printer. It had been attached to the workstation via a USB
cable. I bought a D-Link wireless USB print server (DPR-1260). The
tech installed that as well and I was able to print from the laptop.

Shortly after the tech left, we started having problems with the 5000N
printer. As far as I know, it was not touched. It is still attached to
the LAN via cat5 cable. We can both print to it just as before, but if
it goes into PowerSave, it won't wake up like it used to. If I turn it
off and back on again, it wakes up and prints just fine until it goes
into PowerSave again.

I can't see how that could be related to the wireless network
installation, but it started happening right after that. I have a call
into the tech, but have not heard back yet.

Can it be related?

Any other explanation?

I suppsoe I can disable PowerSave -- at least for now.

Thanks for any hints or suggestions.

--

 

[JohnF]

We have an HP LaserJet 5000N attached to a cat5 cable on a p2p LAN. We
have two PCs connected to the LAN both by cat5 cables. One is a
workstation and the other is a laptop. Both are HP and 5 years old
running Windows 2000........
A week ago, I hired a tech from a local computer support company to
install a wireless network. He brought a Buffalo Air Station Wireless
G Router and Access Point.
Shortly after the tech left, we started having problems with the 5000N
printer.

A couple of things:

1. Are all devices getting there IP assignments from the same DHCP server?
It may be alright if the Buffalo Router/Access Point is hanging off the
Comcast Router, but all computers/printers must be getting IP asignments
from the Buffalo router.

2. I generally give the printer(s) a fixed IP assignment, withing the range
if the mask, but outside the DHCP range.

I guess what I'm saying is that your network is having problems with IP
address conflicts and/or changes.

John

 

[LurfysMa]

We have an HP LaserJet 5000N attached to a cat5 cable on a p2p LAN. We
have two PCs connected to the LAN both by cat5 cables. One is a
workstation and the other is a laptop. Both are HP and 5 years old
running Windows 2000.

The router is part of the cable modem that came with the Comcast
broadband service. This setup has been working perfectly for several
years.

A week ago, I hired a tech from a local computer support company to
install a wireless network. He brought a Buffalo Air Station Wireless
G Router and Access Point. That installation seemed go well.

My laptop, a 5 year old HP Omnibook 6000, does not have wireless built
in so the tech brought a Netgear 108Mbps Wirepess PC card. That
installation seemed to go smoothly as well and I was able to access
the internet from anywhere in the house.

I don;t think this is relevant, but we also have a Canon S830D ink jet
photo printer. It had been attached to the workstation via a USB
cable. I bought a D-Link wireless USB print server (DPR-1260). The
tech installed that as well and I was able to print from the laptop.

Shortly after the tech left, we started having problems with the 5000N
printer. As far as I know, it was not touched. It is still attached to
the LAN via cat5 cable. We can both print to it just as before, but if
it goes into PowerSave, it won't wake up like it used to. If I turn it
off and back on again, it wakes up and prints just fine until it goes
into PowerSave again.

I can't see how that could be related to the wireless network
installation, but it started happening right after that. I have a call
into the tech, but have not heard back yet.

Can it be related?

Any other explanation?

I suppsoe I can disable PowerSave -- at least for now.

Thanks for any hints or suggestions.

As it turns out, it has nothing to do with the Powersave setting.

I changed the Powersave setting to "Off". The problem still occurs.

If the printer sits idle for a period of time, then it cannot receive
print jobs without being powered off and back on again. I am not sure
how long it is before this happens, but I think it's at least 30
minutes.

That was what the Powersave was set to, which is why I thought it was
related.

If I press the Go button, it flashes a message about a job for a
second, but nothing prints.

Can anyone suggest what may be causing this?

--

 

[JohnF]

If the printer sits idle for a period of time, then it cannot receive
print jobs without being powered off and back on again. I am not sure
how long it is before this happens, but I think it's at least 30
minutes.

Perhaps when it's idle, the IP address assignment is released. The power-up
proceess forces IP address renewal.

 

[=?ISO-8859-1?Q?M=F6n=A7ig=F1or_=DFoddoM?=]

Perhaps when it's idle, the IP address assignment is released. The power-up
proceess forces IP address renewal.

That's a good point. Have you assigned the printer's IP staticly on the
router, as well as on the printer's NIC? After the printer does one of
it's powersaves, see if you can ping it from a PC.

 

[LurfysMa]

A couple of things:

1. Are all devices getting there IP assignments from the same DHCP server?
It may be alright if the Buffalo Router/Access Point is hanging off the
Comcast Router, but all computers/printers must be getting IP asignments
from the Buffalo router.

2. I generally give the printer(s) a fixed IP assignment, withing the range
if the mask, but outside the DHCP range.

I guess what I'm saying is that your network is having problems with IP
address conflicts and/or changes.

I don't know enough about network protocols to understand what you are
saying, but it sounds like something has changed with the network. I
am trying to get the tech back who installed the wireless network.

What puzzles me is that the printer is not connected to the wireless
network. It's cabled directly to the Comcast router just like it has
always been. I am wondering if he changed some settings in the Comcast
router?

--

 

[LurfysMa]

Perhaps when it's idle, the IP address assignment is released. The power-up
proceess forces IP address renewal.

Do you know how I can change it back so that the IP address is not
released?

--

 

[LurfysMa]

That's a good point. Have you assigned the printer's IP staticly on the
router, as well as on the printer's NIC?

I don't know. The last time we had it serviced, which was awhile ago,
I'm pretty sure that tech said it needed to be a static IP address.

What's puzzling is that I'm quite sure that this tech (who installed
the wireless network) didn't touch the printer. It was cabled directly
to the Comcast router and it still is.

So if anything has changed, it has to be the Comcast router.

After the printer does one of
it's powersaves, see if you can ping it from a PC.

As I said, it has nothing to do with the powersave. I did try a ping
(address is 10.1.10.130) right after power on and when it is not
responding. Just after power on, I get a reply in 1ms all 4 times.
After a wait period, all 4 time out -- no reply.



--

 

[LurfysMa]

Perhaps when it's idle, the IP address assignment is released. The power-up
proceess forces IP address renewal.

I did a little more testing.

Pinging the printer does not prevent it from going offline ort losing
its address or whatever it is that it's doing. I tried pinging the
printer every few minutes. After about 30 minutes, it stopped
responding.

I then tried printing a page every few minutes. Again, after about 30

--