Re: Getting a HP Jetdirect to work through routers -- MIDRANGE-L


roger,

the problem may be with the timeouts in the jetdirect config.  try this:

in jetadmin, go into modify and change the tcp/ip idle timeout to 3500, then go
into properties for the printer and under the advanced tab, hit the setup button
and change the timeout to end a print job to 2 minutes, 30 seconds.

also, on the device config change the inactivity timer (INACTTMR) to *SEC15.

hope this helps

dan turkeltaub
technology manager
keeney manufacturing
dturk@upt.com






"Paul Tykodi" <paul@intermate-us.com> on 08/16/2001 10:21:58 AM

Please respond to midrange-l@midrange.com

To:   midrange-l@midrange.com
cc:   rvicker@vicker.com (bcc: Dan Turkeltaub/UPT)

Subject:  Re: Getting a HP Jetdirect to work through routers




Hi Roger,

>From your description of the problem (LPR works - PJL Driver does not), I
can make a guess that the problem with the PJL driver is that the requested
reponses from the printer are not making it back from the remote printer
through the network to the IBM host. When this occurs, OS/400 based *LAN
printer device descriptions using the PJL driver will hang and no data is
printed.

If you are running V4R5 or V5R1, you can change the IBM System Driver
Program value from its current setting SYSDRVPGM(*HPPJLDRV)to
SYSDRVPGM(*IBMSNMPDRV). The use of Simple Network Management Protocol (SNMP)
to manage a printer is outlined in RFC 1759 and is fully TCP/IP compliant.
There is a much better chance that required SNMP responses will be able to
negotiate the routers and be returned to the IBM host than the PJL
responses. The *LAN device description SNMP driver was introduced into
OS/400 starting at V4R5. It has been made available via PTF to V4R4 and V4R3
users as well. The required PTF's are documented in the Software Knowledge
Base (under the category Print) on the web site
http://www.as400service.ibm.com.

Best Regards,

/Paul
--
Paul Tykodi
Director of Technical Services
LCI-Intermate US, Inc.

p: 603.431.0606 x115
f: 603.436.6432
paul@intermate-us.com
www.intermate.com

>Date: Wed, 15 Aug 2001 13:37:09 -0500
>From: "Roger Vicker, CCP" <rvicker@vicker.com>
>Organization: Vicker Programming Systems
>To: midrange-l@midrange.com
>Subject: Re: Getting a HP Jetdirect to work through routers
>Reply-To: midrange-l@midrange.com
>
>Paul,
>
>The *DFTROUTE is 10.0.0.254 since that is the router that is on the same
lan as
>the AS/400. The 10.2.0.254 router is on the remote lan as seen from the
AS/400
>end of things.
>
>Alistair,
>
>The printer is defined as a lan printer by:
>
>CRTDEVPRT DEVD(WDPR10971)
>          DEVCLS(*LAN)
>          TYPE(3812)
>          MODEL(1)
>          LANATTACH(*IP)
>          PORT(9100)
>          FONT(11)
>          TRANSFORM(*YES)
>          MFRTYPMDL(*HP4000)
>          RMTLOCNAME('10.2.1.97')
>          SYSDRVPGM(*HPPJLDRV)
>         TEXT('FWD Data Collections Laser')
>
>It can not be DEVCLS(*RMT) since it is not connected to a remote
workstation
>controller.
>
>As part of trying to figure this out I did try using a remote outq and it
>worked. However I need the functions of CRTDEVPRT. I've also tried adding a
name
>to the host table and using that in the DEVD and OUTQD with no difference.
>
>Paul Tykodi wrote:
>
> Dear Roger,
>
> You might want to execute the command CFGTCP on your IBM host and then
> choose option 2 Work with TCP/IP Routes. You should see something that
looks
> like the following when you press enter:
>
>                             Work with TCP/IP Routes
>                                                              System:
> S102G6VM
>  Type options, press Enter.
>    1=Add   2=Change   4=Remove   5=Display
>
>       Route            Subnet           Next             Preferred
>  Opt  Destination      Mask             Hop              Interface
>
>       *DFTROUTE        *NONE            10.10.5.1        *NONE
>
> In your case the *DFTROUTE value should point towards the Cisco router at
IP
> Address 10.2.0.254. The OS/400 value *DFTROUTE is used to tell an IBM
> iSeries or AS/400 server where to send all requests to contact IP
addresses
> that are not visible to the server on its local segment. You can add other
> routing entries that specify certain address ranges and a different IP
> address as the next hop as necessary.
>
> HTH
>
> /Paul
> --
> Paul Tykodi
> Director of Technical Services
> LCI-Intermate US, Inc.
>
> p: 603.431.0606 x115
> f: 603.436.6432
> paul@intermate-us.com
> www.intermate.com
>
> >Date: Wed, 15 Aug 2001 08:42:45 -0500
> >From: "Roger Vicker, CCP" <rvicker@vicker.com>
> >Organization: Vicker Programming Systems
> >To: Midrange List <MIDRANGE-L@midrange.com>
> >Subject: Getting a HP Jetdirect to work through routers
> >Reply-To: midrange-l@midrange.com
> >
> >Hello,
> >
> >I am having trouble getting some HP Jetdirect servers to work with an
> >AS/400 through routers. The AS/400 is working with Jetdirects on its
> >local network (CRTDEVPRT *HPT) but when I use the same process through
> >routers the writer times out after about 3 minutes and the spool file
> >never changes from RDY. Sprint claims that they didn't block any ports
> >in the routers.
> >
> >The layout is:
> >
> >AS/400 @ 10.0.0.1 mask 255.255.0.0 on an otherwise Novel network
> >Cisco router @ 10.0.0.254
> >Frame Relay by Sprint
> >Cisco router @ 10.2.0.254
> >Local peer to peer (Windows xxxx) network 10.2.#.# mask 255.255.0.0
> >but with a WINS server @ 10.2.1.57
> >The AS/400 has the WINS tab pointed to the local WINS server.
> >
> >CAE and file server works OK. Local PCs can use the Jetdirects. The
> >AS/400 can ping the Jetdirects by address and the CRTDEVPRT uses the
> >address, not a host name.
> >
> >Where do I look next?
> >
> >Roger Vicker, CCP
> >
> >--
> >*** Vicker Programming and Service *** Have bits will byte ***
> >www.vicker.com ***
> >A mule dressed in a tuxedo is still a mule.
>

--
*** Vicker Programming and Service *** Have bits will byte ***
www.vicker.com
***
A mule dressed in a tuxedo is still a mule.

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com