× 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.


  1.  Home
  2. MIDRANGE-L
  3. May 2002

RE: Ops Nav & Ops Console coexistence

Try making a separate system at IP address 127.0.0.1 (localhost)  This will
connect to your 170 via the Ops Console cable rather than TCP/IP (which is
handy - you can still use OpsNav functions after ENDTCP).

If this works OK, then that means Ops Nav/Ops Console on the PC and 170 is
fine, and it's a network problem - I suspect your cross-wired cable may be
the cause as someone else has alluded to.

Regards,
Dwayne

> I can connect to the server via Ops Console fine... however,
> when I try to use Ops Nav, the OC loses the connection and
> will not reconnect.
>
> While using Ops Nav, I can get to the server, but cannot
> Telnet to it, nor ping it, even though telnet is running.
>
> 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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.