Hmm. The host table on the DR box is identical to the local box. Neither
one has the Netserver name.
I think I need to talk to the DR people.
On Tue, Mar 18, 2014 at 2:11 PM, Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>wrote:
Check the host table. Make sure it has the netserver name and correct IP
Director of Information Services
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
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 is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives