×
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.
Check the host table. Make sure it has the netserver name and correct IP address.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
Sent: Tuesday, March 18, 2014 10:46 AM
To: Midrange Systems Technical Discussion
Subject: Testing Netserver on a remote DR system test
All,
Doing a test of a DR system remotely via Sonicwall VPN. I'm trying to
start Netserver on the remote system and having issues.
The desktop I'm doing this from has 2 connections defined in System i
Navigator. 192.168.0.1 which is the local live System i and 192.168.100.38
which is the remote DR standup system.
First it told me the name was already in use on the network (both netserver
names were the same). So I renamed the DR system one and tried starting
it. Get error 13 in qsysopr that says "The retrieved host IP address of
192.168.0.1 is invalid." Why is it trying to use the /local/ System i IP
address under the connection for the /remote/ DR system?
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.
midrange.com
