RE: Remote Site Cannot Connect -- MIDRANGE-L

Subject: RE: Remote Site Cannot Connect
From: Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>
Date: Mon, 5 Mar 2012 21:42:01 +0000
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

iSeries Access telnet client needs four ports open for a standard out of the box configuration:
1. port mapper, 449
2. Sign-On, 8476 or SSL 9476
3. Telnet, 23 or SSL 992
4. Central, 8470 or SSL 9470

Now you can alleviate the port mapper by specifying STANDARD in the Connection to the System under "Where to lookup remote port"

http://www.mcpressonline.com/security/ibm-i-os400-i5os/iseries-access-through-a-firewall.html

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Remote Site Cannot Connect , Jerry C. Adams
RE: Remote Site Cannot Connect , Jerry C. Adams

This mailing list archive is Copyright 1997-2025 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.