Force nsf to use tcp instead of udp? -- MIDRANGE-L

Subject: Force nsf to use tcp instead of udp?
From: Gerald Kern <jp2558@xxxxxxxxx>
Date: Fri, 25 May 2012 14:03:21 -0400
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>

I've been asked to set up an export on NSF. When the server tries to access
it it says to the effect that the iSeries doesn't support NSF version 3
over TCP, and it looks like (via netstat) that nsf is running under UDP.

In the service table, NSF has the port defined for both TCP and UDP.

So the question is how can I force NSF to use TCP instead of UDP?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Force nsf to use tcp instead of udp? , rob
Re: Force nsf to use tcp instead of udp? , Scott Klement

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.