RE: Ports needed for a Remote Outq -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

We have a situation similar to this client. We find that the outq frequently 
loses contact w/ the network. Is there any way of debugging the communications 
values or other extents to determine what the problem(s) are?

-----Original Message-----
From: Graap, Ken [mailto:keg@xxxxxxxxxxxxx]
Sent: Tuesday, May 24, 2005 3:44 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Ports needed for a Remote Outq

Common LPD port, which is started via the STRTCPSVR SERVER(*LPD) command:

Remote           Remote  Local                   
Address           Port    Port  Idle Time  State 

*                     *    515  003:39:38  Listen

Kenneth

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of pnelson@xxxxxxxxxx
Sent: Tuesday, May 24, 2005 11:36 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Ports needed for a Remote Outq

I've got a client who has a customer wishing to send a spool file via
remote outq (400 to 400). They have different networks. Which ports does
each side need to open on the firewalls and/or the 400's?

Thanks
--

Paul Nelson
Arbor Solutions, Inc.
 708-670-6978  Cell
pnelson@xxxxxxxxxx

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.