Re: [WinMac] LaserJet 4 question

Bruce Johnson(johnson[at]Pharmacy.Arizona.EDU)
Fri, 10 Sep 1999 13:27:03 -0500

Victor Forberger wrote:
>
> I hope I'm just being stupid, but I can't seem to get a LaserJet 4M with
> a JetDirect card to connect to a 10baseT network.

> If this helps, the display says, "18 AUX IO NT RDY," largely because I
> believe the IP address is invalid ("0.0.0.0"). Unfortunately, I cannot
> seem to change anything via the front panel controls. I make changes
> (such as turning on other network protocols), but nothing seems to
> stick.

This is an internal card? There's a front panel dance you have to do on
a LJ 4 to completely reset everything; hold the Shift and Menu buttons
down until RESET=MENU appears. This may take ten seconds or longer.
Press + or - until RESET= ALL I/O appears, then ENTER to select it, then
ONLINE to actually do the reset.

The default IP address on a jet direct is 192.0.0.1, (tcp-ese for 'this
host') not 0.0.0.0

Jet driects can get horribly confused at times, and resetting them is
the only way out.

Then you can configure the card via JetAdmin. Another hint. If the reset
Jet Direct doesn't show up in the list of available cards to configure,
try telling JetAdmin to 'Rebuild Database and Refresh' from the Refresh
Devices menu. This may take a few tries.

We have about 15 JetDirects around, so we've had a fair bit of
experience with these.

Another quirk of JetDirects is that in TCP/IP mode they seem to not
advertise themselves to the router very often; the upshot is that if the
only protocol they're running is IP, they tend to age off the routers
and/or switches routing tables unless their address is given a long
expiration date or made permanent in the routing tables.

If you can deal with the added packet traffic, switching on IPX (even if
you don't use it) prevents that; I suspect that Appletalk would do the
same.

Just a hint if you have a Jet direct that keeps 'disappearing'...we had
one on another subnet on another part of campus, the router in between
didn't pass IPX traffic, so the thing would stop responding after a
while. The only solution we had then was to powercycle the JetDirect. We
went through three before we came to the reluctant conclusion that it
wasn't the JetDirects, but the network they were on.

Very frustrating, made worse when we switched all our printers to a new
subnet in our building and they _all_ started doing that. We went NUTS
trying to figure it out.

However, for all that we've sworn _at_ 'em, when they're working they're
damn well bulletproof. Now that we know their quirks we haven't had a
lick of trouble with one of them.

-- 
Bruce Johnson
University of Arizona
College of Pharmacy
Information Technology Group


*                    Windows-MacOS Cooperation List                 *

This archive was generated by hypermail 2.0b2 on Fri Sep 10 1999 - 11:35:24 PDT