Re: .NET Connection from WebServer to iSeries -- WEB400

× 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.

Subject: Re: .NET Connection from WebServer to iSeries
From: "Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>
Date: Wed, 26 Sep 2007 15:19:48 -0400
List-archive: <http://archive.midrange.com/web400>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: Web Enabling the AS400 / iSeries <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

Maurice,

We've worked with:

TCP/449 (port-mapper)
TCP/8476 (authentication)
TCP/8471 (data access)

Assuming you've not changed the ports on the 400 side. Port 449 is
always the one that bugs me, wish I could hard-code the ports, but I've
not found a way.

-Walden

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: .NET Connection from WebServer to iSeries , Craig Pelkie
Re: .NET Connection from WebServer to iSeries , Maurice O'Prey

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.