Jetdirect 170x (J3258B) and XP Home

  • Thread starter Thread starter Don
  • Start date Start date
D

Don

Just added a notebook with Windows XP Home to my home network, which
uses an HP Jetdirect 170X (model J3258B) to connect an HP LaserJet
IIIP to the network. The setup works fine with the Windows 98SE
computers on the network, but attempts to print from the XP notebook
fail. The printer installs (both using the HP Network Printer Install
Wizard and installing a local TCP/IP printer), and I'm able to ping
the JetDirect's IP address from the XP notebook. However, every
attempt to print receives a "document failed to print" error. If
anybody's had any success in getting the J3258B version of the 170X
working in XP, would you be so kind as to point me in the right
direction?

TIA!

Don
 
Check your Printer's Advanc eSetting. Make sure BiDirectional
Communication is disabled. Give that a try and see.

Dewaine
 
Thanks, but no luck there - it's actually on the Port Settings page,
and "Enable Bidirectional" unselected and is greyed out.

Thanks for the reply!
 
On 27 Nov 2003 12:38:11 -0800, (e-mail address removed) (Don) wrote:

|Just added a notebook with Windows XP Home to my home network, which
|uses an HP Jetdirect 170X (model J3258B) to connect an HP LaserJet
|IIIP to the network. The setup works fine with the Windows 98SE
|computers on the network, but attempts to print from the XP notebook
|fail. The printer installs (both using the HP Network Printer Install
|Wizard and installing a local TCP/IP printer), and I'm able to ping
|the JetDirect's IP address from the XP notebook. However, every
|attempt to print receives a "document failed to print" error. If
|anybody's had any success in getting the J3258B version of the 170X
|working in XP, would you be so kind as to point me in the right
|direction?

I use the 170x on a predominately xp network successfully and without
incident(until I added a linksys wireless access point and router, but
that's another story - a dhcp issue). The part I thought that was
tricky in setting up the box to access the print server was that the
jet direct port is configures as local and not network on the first
dialog box. You create the jet direct port and everything else
follows, IIRC.

all the best
 
Did you try connecting to the built in webserver and check the configuration
settings of the Jetdirect?

We use a number of similar units with Win2K, WinNT and WinXP with no
problems.
 
Back
Top