Re: firewall ports Client Access udp or tcp -- MIDRANGE-L

Subject: Re: firewall ports Client Access udp or tcp
From: Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 21 Apr 2004 09:22:05 -0500
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>

Execute WRKSRVTBLE and check it out. Most of the as-* services are tcp, some are also spx, a very few are also udp. There's an option F6 to print the list - do so and show it to your network person.

HTH
Vern

At 08:05 AM 4/21/2004, you wrote:

should be just TCP, if I recall
----- Original Message -----
From: "Jim Franz" <franz400@xxxxxxxxxxxx>
To: <MIDRANGE-L@xxxxxxxxxxxx>
Sent: Wednesday, April 21, 2004 8:57 AM
Subject: firewall ports Client Access udp or tcp


> Does anyone know if the list of ports in apar 12227
> for Client Access are tcp, udp, or both.
> Firewall tech needs to know.
> Anything known not in this apar?
> Need to remote access (telnet) & remote manage(config & ptfs) a system.
> jim

As an Amazon Associate we earn from qualifying purchases.

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.