RE: AS-400 TCP3436 Error when printing remotely

[<franz400@xxxxxxxxxxxx>]

The Zebra (at least all the ones I've seen) require some print server or attachment (have not seen one with it's own ethernet port). Mine attach to a HP Jet Direct box, with fixed ip (no dhcp). Have had lots of problems when not a true HP Jet Direct but a cheap knockoff.
Also the sleep mode Paul mentioned sounds good. 
jim


---- "Bollinger wrote: 
> They are remote writes and we go directly to the printers IP noth through a server or printer definition.
> I will look into the timeouts.  
>
> I appreciate any and all suggestions as we've had all the network staff and IBM programmers up at night trying to figure this out for the past month.
> Thanks,
> Kristine
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of
> franz400@xxxxxxxxxxxx
> Sent: Wednesday, February 27, 2008 11:04 AM
> To: Midrange Systems Technical Discussion
> Subject: Re: AS-400 TCP3436 Error when printing remotely
>
>
> Are these defined as *lan printers? or remote writers?
> Are you talking directly to the printers, or thu a print server product on pc/network
> or Client Access printer definition, or something like Jet Direct hardware box the printer is connected to?
> Would check the network timeout value on the printer itself. IBM Knowledge Base used to (and may still have) docs on recommended values for various configurations. Make sure both printer & system are consistent and using recommended values. I have had similar issues when network setup is inconsistent on remote side. 
> Jim Franz
>
> ---- "Bollinger wrote: 
> > Hello All!
> >
> > We have an IBM AS400 in Minnesota and a remote office in Hong Kong that we are printing to.  It seems that every night (their day) we can ping their printer but the AS400 cannot print to it and gets stuck in send mode.
> > Now we have 4 printers out there and it doesn't happen to them all, it is usually just one a night.  At around 6am it will begin working again.
> >
> > We get the following error:
> > TCP3436
> > Message . . . . :   No response from remote host system within open time-out. 
> >
> > I'm wondering if anybody has a solution to this?  It doesn't seem to be network given we can print to the other printers out there.  If we try toggling off and on the device it still won't work.
> >
> > Thanks,
> > Kristine Bollinger
> > The Bergquist Company
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ----- Original Message ----- 
> > From: <Bonnie_Lokenvitz@xxxxxxxxxxxxxx>
> > To: <midrange-l@xxxxxxxxxxxx>
> > Sent: Tuesday, March 09, 2004 7:18 AM
> > Subject: Remote Printer - What do I ask Network guy to check on his side?
> >
> >
> > > Still at V4R5 and still operator-less.
> > >
> > > We have several Intermec 3400's setup as remote writers.
> > > CRTOUTQ with connection type *IP and the IP address.  Added another
> > > yesterday.
> > >
> > > The As/400 print stays in send mode and this error appears in QSPL  job:
> > >
> > > TCP3436
> > > Message . . . . :   No response from remote host system within open
> > > time-out.
> > > Cause . . . . . :   An open request was sent to a remote host system, but
> > > that
> > >   host system did not respond to the request before the open time-out
> > > expired.
> > >   This may be due to the fact that the TCP/IP services are not currently
> > >
> > >   available on the remote host system.
> > >
> > >
> > > The network admin says he can ping it so there's no problem.  VFYTCPCNN
> > > from AS/400 also works.  Where else should we be looking?
> > >
> > > Thanks much,
> > > Bonnie Lokenvitz
> > > Engineered Polymers
> > >
> > >
> > > _______________________________________________
> > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > > Before posting, please take a moment to review the archives
> > > at http://archive.midrange.com/midrange-l.
> > -- 
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.