JetDirect Drops off Network

[oneworld]

I have a JetDirect 300x external and it is attached to an HP 1300. For some reason the print server drops off the network. It holds all of its setting but you can not ping the IP address.

If we cold boot the jetdirect then the device seems to work fine but then a few days go by and the same problem happens.

Has anyone seen this before? Is the printer going into sleep mode and not coming on line or could it be a problem with the jetdirect? Is there any type of idle setting that I am missing on the jetdirect?

Help please...this one is driving me crazy.


Joe - a.k.a. Oneworld

 

[Michael52x]

Most likely it is the DHCP settings on the NIC that poicks up a different last digit in the IP. You will want a static IP.
You can use HP WebJet Admin to update the NIC's firmware, and to change the config method.
Or, do a config page every day, and make the changes in the driver.


"Impatience will reward you with dissatisfaction" RMS Cosmics'97

 

[oneworld]

Thank you for the post. Unfortunately, it is static and it does keep its configuration settings.

Joe - a.k.a. Oneworld

 

[gbaughma]

Here's some things to try:

1) Different network cable.
2) Remove/Re-seat (with the power off, obviously) the JetDirect card.
3) Different port on your switch or hub that the JetDirect is plugged into.
4) Try "locking down" the speed of the device; if it is running at 100-base speed on the network, lock it down to 10-base.
5) Re-route the cable; make sure it is not running over flourescent lights, along side of power cords, televisions, monitors, anything that can generate RF.
6) Try plugging the printer into a different outlet. There could be electrical noise on that A/C line that is causing issues.

... I have tried, and used, every one of these in the past to solve similar issues with both printers and computers.



Just my 2¢
-There once was a man from Peru
Who wanted to write a Haiku
but...

--Greg

http://parallel.tzo.com

 

[jjtbt]

I have the same problem with a LaserJet 1200 attached to a JetDirect 175x...did you find a solution yet?

 

[w33mhz]

I have had this happen several times you are better off just knuckling under and getting a new JetDirect box. Sometimes you can update the firmware on them and sometimes will fix the problem.