Re: Can't connect via TCP -- MIDRANGE-L

× 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: Can't connect via TCP
From: "Leif Svalgaard" <leif@xxxxxxxx>
Date: Sun, 14 Oct 2001 11:42:36 -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/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-Unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

From: Leif Svalgaard <leif@leif.org>
> Everything looks normal (or rather: as it was
> before, as it is not clear was NORMAL when
> it comes to voodoo).

Well, just noticed that the "collision" light on my little
3Com "Home Connect" Router is on solidly.
Turning Off/on doesn't make a difference.
Is it the AS/400 that is keeping the line busy
for no good reason?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Can't connect via TCP , Jim Franz

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.