7 Jun
2010
7 Jun
'10
3:23 a.m.
I tried to attach a LaserJet III to a JetDirect EX Plus. The printer
looks like it's ok. It can print a test page from the control panel
just fine. I haven't tried to attach it to a computer parallel port
yet, so I haven't ruled out the parallel port on the printer and cable
yet.
I installed the HP TCP/IP driver for vista. It finds the JetDirect box
just fine. I can see in the router logs that the JetDirect asks for
and receives an IP Address. Vista lets me create a printer using the
TCP/IP "port". When I go to print a test page, nothing happens. It
just says "error" in the printer window. I can see the network light
flashing on the JetDirect. But nothing happens.
Can anyone suggest something else to try?
brian
7 Jun
7 Jun
4:05 a.m.
Brian Lanning wrote:
I tried to attach a LaserJet III to a JetDirect EX
Plus. The printer
looks like it's ok. It can print a test page from the control panel
just fine. I haven't tried to attach it to a computer parallel port
yet, so I haven't ruled out the parallel port on the printer and cable
yet.
That would definitely be something to try. You'll want to make sure the
printer/port/cable is ok prior to doing anything else. Be careful and
cognizant of the cable choices you make.
I installed the HP TCP/IP driver for vista.
I would stay away from proprietary solutions for the actual print driver
portion of it. For managing the print server, that's one thing. But
for general printing, use standard "lpr" based print services. It's
built into Windows. Don't use the proprietary software created ports,
just use lpr, standard port number(windows will default correctly), and
if the print server has more than one port, make sure to specify the
"queue name" -- some servers use S0, S1, S2 for serial port 1, serial
port 2. or P1, P2 etc for parallel ports 1 & 2, and so on. Be aware
that these queue names matter so that when the PS receives a job, it
knows which port to send it out on.
I can see in the router logs that the JetDirect asks
for
and receives an IP Address.
DHCP is a PITA. Set your print server to a static IP. There's no need
on 99% of networks for a moving printer IP. (I don't care if you can
set it on the DHCP server). Just set it to a static IP, and exclude the
address from the DHCP server pool if necessary.
Can anyone suggest something else to try?
In Vista, add a local printer. (definitely NOT a network printer, trust
me on this) Create new port. Type of port "standard tcp/ip port" Device
type TCP/IP. IP address. PORT NAME --- this is the field I mentioned
above, make sure it contains the correct port name (check print server
manual for the correct naming convention). I don't have a print server
here now, so just make sure you pick the exact model of printer and
manufacturer, etc. Laser Jet III's are/were extremely popular and they
have perfect driver support.
brian
Hope this helps
Keith
8:34 a.m.
-----Oorspronkelijk bericht-----
Van: cctalk-bounces at classiccmp.org
[mailto:cctalk-bounces at classiccmp.org] Namens Keith
Verzonden: maandag 7 juni 2010 6:05
Aan: General Discussion: On-Topic and Off-Topic Posts
Onderwerp: Re: JetDirect problems
Brian Lanning wrote:
The portnumber for HP printservers is 9100
And you could try to reach the Jetdirect with a browser on it's IP-address
(Java must be enabled)
If you can reach the Jetdirect switch everything except TCP/IP off so no
netbios/IPX etc..
Just TCP/IP and yes a static IP-address is preferred.
If you know the hostname of the printer you could try to connect without
filling in the IP-address.
-Rik
I tried to attach a LaserJet III to a JetDirect
EX Plus.
The printer
looks like it's ok. It can print a test page
from the
control panel
just fine. I haven't tried to attach it to a
computer
parallel port
yet, so I haven't ruled out the parallel port
on the
printer and cable
yet.
That would definitely be something to try. You'll want to
make sure the printer/port/cable is ok prior to doing
anything else. Be careful and cognizant of the cable choices
you make.
I installed the HP TCP/IP driver for vista.
I would stay away from proprietary solutions for the actual
print driver portion of it. For managing the print server,
that's one thing. But for general printing, use standard
"lpr" based print services. It's built into Windows. Don't
use the proprietary software created ports, just use lpr,
standard port number(windows will default correctly), and if
the print server has more than one port, make sure to specify
the "queue name" -- some servers use S0, S1, S2 for serial
port 1, serial port 2. or P1, P2 etc for parallel ports 1 &
2, and so on. Be aware that these queue names matter so that
when the PS receives a job, it knows which port to send it out on.
I can see in the router logs that the JetDirect
asks for
and receives an IP Address.
DHCP is a PITA. Set your print server to a static IP.
There's no need on 99% of networks for a moving printer IP.
(I don't care if you can set it on the DHCP server). Just
set it to a static IP, and exclude the address from the DHCP
server pool if necessary.
Can anyone suggest something else to try?
In Vista, add a local printer. (definitely NOT a network
printer, trust me on this) Create new port. Type of port
"standard tcp/ip port" Device type TCP/IP. IP address. PORT
NAME --- this is the field I mentioned above, make sure it
contains the correct port name (check print server manual for
the correct naming convention). I don't have a print server
here now, so just make sure you pick the exact model of
printer and manufacturer, etc. Laser Jet III's are/were
extremely popular and they have perfect driver support.
brian
Hope this helps
Keith
12:01 p.m.
You guys are awesome. I'll try all this tonight.
One last thing... Any way to stop the classic laser printer light
dimming pronlem? It makes the lights in my computer room flicker.
On Mon, Jun 7, 2010 at 3:34 AM, Rik Bos <hp-fix at xs4all.nl> wrote:
-----Oorspronkelijk bericht-----
Van: cctalk-bounces at classiccmp.org
[mailto:cctalk-bounces at classiccmp.org] Namens Keith
Verzonden: maandag 7 juni 2010 6:05
Aan: General Discussion: On-Topic and Off-Topic Posts
Onderwerp: Re: JetDirect problems
Brian Lanning wrote:
The portnumber for HP printservers is 9100
And you could try to reach the Jetdirect with a browser on it's IP-address
(Java must be enabled)
If you can reach the Jetdirect switch everything except TCP/IP off so no
netbios/IPX etc..
Just TCP/IP and yes a static IP-address is preferred.
If you know the hostname of the printer you could try to connect without
filling in the IP-address.
-Rik
I tried to attach a LaserJet III to a JetDirect
EX Plus.
The printer
looks like it's ok. ?It can print a test page
from the
control panel
just fine. ?I haven't tried to attach it to a
computer
parallel port
yet, so I haven't ruled out the parallel port
on the
printer and cable
yet.
That would definitely be something to try. ?You'll want to
make sure the printer/port/cable is ok prior to doing
anything else. ?Be careful and cognizant of the cable choices
you make.
I installed the HP TCP/IP driver for vista.
I would stay away from proprietary solutions for the actual
print driver portion of it. ?For managing the print server,
that's one thing. ?But for general printing, use standard
"lpr" based print services. ?It's built into Windows. ?Don't
use the proprietary software created ports, just use lpr,
standard port number(windows will default correctly), and if
the print server has more than one port, make sure to specify
the "queue name" -- some servers use S0, S1, S2 for serial
port 1, serial port 2. or P1, P2 etc for parallel ports 1 &
2, and so on. ?Be aware that these queue names matter so that
when the PS receives a job, it knows which port to send it out on.
?>I can see in the router logs that the JetDirect asks for
and receives an IP Address.
DHCP is a PITA. ?Set your print server to a static IP.
There's no need on 99% of networks for a moving printer IP.
(I don't care if you can set it on the DHCP server). ?Just
set it to a static IP, and exclude the address from the DHCP
server pool if necessary.
Can anyone suggest something else to try?
In Vista, add a local printer. (definitely NOT a network
printer, trust me on this) ?Create new port. Type of port
"standard tcp/ip port" Device type TCP/IP. IP address. PORT
NAME --- this is the field I mentioned above, make sure it
contains the correct port name (check print server manual for
the correct naming convention). ?I don't have a print server
here now, so just make sure you pick the exact model of
printer and manufacturer, etc. ?Laser Jet III's are/were
extremely popular and they have perfect driver support.
brian
Hope this helps
Keith 
12:50 p.m.
You guys are awesome. I'll try all this tonight.
One last thing... Any way to stop the classic laser printer light
dimming pronlem? It makes the lights in my computer room flicker.
That's a feature. It runs the lightbulbs at lower power so they last longer.
(ducks and runs)
--
------------------------------------ personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser at floodgap.com
-- yankee hotel foxtrot. yankee hotel foxtrot. yankee hotel foxtrot. konec. ---
1:20 p.m.
On Monday, June 07, 2010, Brian Lanning wrote:
You guys are awesome. I'll try all this tonight.
One last thing... Any way to stop the classic laser printer light
dimming pronlem? It makes the lights in my computer room flicker.
Easy. Just run a new circuit from your panel for the printer. A 12AWG
(20 amp) circuit is recommended.
Or am I the only one that thinks "run another power circuit" is trivial?
:)
Pat
--
Purdue University Research Computing --- http://www.rcac.purdue.edu/
The Computer Refuge --- http://computer-refuge.org
1:56 p.m.
Patrick Finnegan wrote:
It would be if I had sheet rock walls. The fact that I have
plaster-and-lath makes it a bit more "interesting".
Peace... Sridhar
You guys are
awesome. I'll try all this tonight.
One last thing... Any way to stop the classic laser printer light
dimming pronlem? It makes the lights in my computer room flicker.
Easy. Just run a new circuit from your panel for the printer. A 12AWG
(20 amp) circuit is recommended.
Or am I the only one that thinks "run another power circuit" is trivial?
:) 
1:57 p.m.
--- On Mon, 6/7/10, Patrick Finnegan <pat at computer-refuge.org> wrote:
Yeah. That's what I had to do. My HP LaserJet 5si would dim the lights, and if I had
too much stuff on (which was most of the time), it would blow the breaker. For a while, I
would shut off all the monitors, the TV (if on), and the lights, hit print, and shut off
the monitor I had been using. That worked most of the time, but sometimes it would still
trip. If I had the SGI on, I really couldn't use the printer.
Actually, I cheated a bit. The printer is against an interior wall. On the other side of
that wall, is an electrical outlet, and another circuit. I simply cut a hole in the wall,
and ran a short piece of Romex over to the other outlet, and mounted a new outlet on the
printer side of the wall. So, now I have an outlet in my computer room that's on the
other circuit - the one from the spare room. Since the spare room isn't packed to the
gills with electronics, everything works fine.
-Ian
One last
thing... Any way to stop the classic laser
printer light
dimming pronlem? It makes the lights in my
computer room flicker.
Easy. Just run a new circuit from your panel for the
printer. A 12AWG
(20 amp) circuit is recommended.
2:24 p.m.
On Mon, Jun 7, 2010 at 8:20 AM, Patrick Finnegan
<pat at computer-refuge.org> wrote:
Easy. ?Just run a new circuit from your panel for the
printer. ?A 12AWG
(20 amp) circuit is recommended.
Or am I the only one that thinks "run another power circuit" is trivial?
:)
I put a 100amp subpanel in my garage for the wood shop. That's
actually on the other side of the wall from the computer room. I
could easily run a circuit off of that. I'm sure that would make my
wife roll her eyes. lol
At some point, I may relocate the computer room to the basement. If
that happens, I'll have the lights and computers on different circuits
anyway. I guess for now I can just leave it off. This is really just
meant as a backup printer anyway.
brian
6:48 p.m.
You guys are awesome. I'll try all this tonight.
One last thing... Any way to stop the classic laser printer light
dimming pronlem? It makes the lights in my computer room flicker.
YEs, sort out your mains wiring before something catches fire...
A clssic lasr printer cotnains a fairly powerful tungsten halogen bulb to
heat the fuser roller. This turns on and off to keep the fuser at the
right temperatuire. The rest of the laser printer is quite low power,
actually.
My guess is that the lamps dim when the fuser heater turns on. In whih
case there ais a main votlage drop somewhere. Possibly a bad connection
or dodgy wiring. Check it!.
-tony
9:16 p.m.
Brian Lanning <brianlanning at gmail.com> wrote:
You guys are awesome. I'll try all this tonight.
One last thing... Any way to stop the classic laser printer light
dimming pronlem? It makes the lights in my computer room flicker.
You have a problem with that? It's one of the endearing features of
my LaserJet Series II. The "computer room" is on a string that seems
to also have lights and outlets in the bathroom and kitchen.
...
Speaking of JetDirects, a couple or three months ago I was looking at
the XIO JetDirect cards that fit in the Series II/III. The Netware
and TCP/IP cards are the same hardware, the only difference is the
EPROM and its firmware.
Now, suppose you want to change a MAC address on a card.
You might think there'd be a small PROM on the card to hold the MAC
address, but there isn't, the MAC address is in the EPROM with the
firmware. OK, so you need to find the MAC address in the EPROM (I
found it in the last 32 bytes in the image: 0x1ffe0-0x1ffe5 in the
Netware image, 0x3ffe0-0x3ffe5 in the TCP/IP image), change it to the
desired value, burn an EPROM, put the EPROM in the socket on the card,
reinstall, and turn the printer back on.
That doesn't do it, that gets you "42 ERROR" and "69 SERVICE" on
the
LaserJet front panel.
Turns out the MAC address is checksummed: that next byte (..ffe6) is
expected to be the complement of the 8-bit checksum of the six bytes
of MAC address, and if it isn't the XIO JetDirect card's firmware
fails its selftest. Recalculate that for your new address, and change
it in your new EPROM image too, and it works.
-Frank McConnell
5329
days inactive
5329
days old
10 comments
9 participants
participants (9)
-
ard＠p850ug1.demon.co.uk -
brianlanning＠gmail.com -
fmc＠reanimators.org -
hp-fix＠xs4all.nl -
ian_primus＠yahoo.com -
keithvz＠verizon.net -
pat＠computer-refuge.org -
ploopster＠gmail.com -
spectre＠floodgap.com