laserjet 4000tn no network connection, but jetdirect not at fault.

[jbraly]

I have a lap of about 22 computers that has an HP laserjet 4000tn
connected to them all via CAT5.

The printer has worked smoothly for many years, but I fear it may be on
it's last leg.

It no longer gets an ethernet connection. So, like any good tech, I
found another 4000tn on campus that works just fine, pulled out its
jetdirect card and popped it in the broke on. No go.

SO I take the "broke card" and pop it in the known-working 4000tn and
it works fine.

So, it isnt the card...

Where would I start looking mext? Im happy to buy a new printer since
this one has lasted so long, but if there is something simple I am not
seeing, please let me know.
thanks in advance!
JAzz Mann

 

[Bennett Price]

If you're using DHCP in the lab, try setting the printer to a static
address.

 

[jbraly]

it is static... i turned it off for about the 5th time today and turned
it back on and now it works... wierd.

 

[Fred McKenzie]

it is static... i turned it off for about the 5th time today and turned
it back on and now it works... wierd.

JB-

It would seem like a good idea to go into the printer and reseat the
memory modules, in case one has a bit of corrosion.

You have already reseated the JetDirect card. Any other plug-in card or
mother board might also benefit from being re-seated.

One thing that is frequently overlooked is that the Ethernet cable. That
printer might have an intermittent cord connecting the JetDirect card to
the network. Next time, try swapping the cord with another "known good"
one, preferably not as old as the original!

Fred

 

[jbraly]

wasnt the cable, i retested with many cat5 cables with the same
results.
but i will try to reseat the mem modules.
thanks!

 

[wee-meng lee]

maybe some fast unix workstation is using the same IP address as the
printer.
i've seen it happen quite often in a lab environment. if it duplicates the
router/gateway IP address, the whole n/w becomes wonky.

when it happens again, to check it, remove the n/w cable to the printer and
try to ping its IP address. if there is a ping response, do an "arp" to
find the MAC address. if it's a managed switch, there's usually a function
to search which port the MAC address is last seen on.

otherwise start pulling out n/w cables at the switch end until the ping
response stops. put back the cable if the pinging still continues. the
last cable pulled out that stops the ping response is either the one
connected to your own pc or the culprit.

rgds
weemeng

 

[Benjamin]

Have you tried to reset the printer?

 

[jbraly]

reseated the memory yesterday, no issues since.
Even still, im getting some quotes on a 4350 workgroup printer... just
in case...

 

[Fred McKenzie]

reseated the memory yesterday, no issues since.
Even still, im getting some quotes on a 4350 workgroup printer... just
in case...

JB-

Where I used to work, each Ethernet outlet was fed from a separate card in
a centrally-located rack of equipment. Sometimes the card would have a
problem that made it look like the device it fed was defective. Replacing
the card, or sometimes just un-plugging and re-plugging, would clear the
problem for months.

Fred