Re: Ops Nav & Ops Console coexistence -- 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: Ops Nav & Ops Console coexistence
From: James Rich <james@xxxxxxxxxxx>
Date: Wed, 15 May 2002 16:20:32 -0600 (MDT)
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>

On Wed, 15 May 2002, John Gregory Katz wrote:

> I've connected my W2K laptop running Client Access 5.1 to the server
> operating on v5.1, over an ethernet cabling hub.  The 400 is connected to
> the hub via a cross-wired cat-5 cable.  PC is connected via a straight wired
> cable.

Why are you using a cross wired cable?  This may work if you put the cable
into the uplink port of the hub, but it is very bad practice.  Put in a
standard straight wired cable and remove one potential problem.

James Rich
james@eaerich.com

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.