Re: Ending all TCP connections on a port -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Ending all TCP connections on a port
From: Bryan Dietz <bdietz400@xxxxxxxxx>
Date: Fri, 26 Jun 2020 15:13:16 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

you could end the service that is associated with that port.

WRKSRVTBLE for list of well know ports

80 - "normal" http
23 - telnet (see below)
22 - ssh

be careful to not pull the rug out from underneath yourself.

Bryan

James H. H. Lampert wrote on 6/26/2020 12:55 PM:

We've had cases, on customer boxes, where a Tomcat stop-and-restart fails because of dangling connections.

I've been looking at ENDTCPCNN, but it appears to only work on one specific connection, Does anybody know of anything that can wipe out *all* connections for a given port, in one swell foop?

--
JHHL

Follow-Ups:

Re: Ending all TCP connections on a port , James H. H. Lampert

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