RE: Ops Console problem solved!!!!

["Kirk Goins" <kirkg@xxxxxxxxxxxxxx>]

There is a REGISTER hack to change the base address that OPS CONSOLE uses. 
Here's a note I made for myself.

Client's internal IP network is use the 192.168.0.x range of IPs. OPS NAV 
defaults to 192.168.0.2 and wants to reserve that WHOLE RANGE for itself. by 
that I mean all the 192.168.0.x addresses. To change the range of IP addresses 
it uses you need to hack the register

In 2000 its at
HKEY_LOCAL_MACHINE
        SOFTWARE\
        IBM\Client Access\
        CurrentVersion\
        AS400 Operations Console
        \LCS\
        system name that you created

Change the IP from 192.168.0.2 to the range you want. Then re-run the OPS NAV 
cfg so it picks up the new range.


__________________________________________________
Kirk Goins
IBM Certified iSeries Technical Solutions Expert
IBM Certified Designing IBM e-Business Solutions
Pacific Information Systems - An IBM Premier Business Partner
503-674-2985           kirkg@pacinfosys.com


-----Original Message-----
From: vhamberg@attbi.com [mailto:vhamberg@attbi.com]
Sent: Friday, August 09, 2002 4:09 PM
To: midrange-l@midrange.com
Subject: Ops Console problem solved!!!!


Well, this is an obscure one, but it makes sense once
you find out what's going on.

The answer is, Ops Console uses network address
192.168.0.0 subnet mask 255.255.255.0, and this CANNOT
be changed. Our intranet had the same setup. When you
use a direct cable, it is like another network card, and
you cannot have 2 network cards with the same network
address/subnet combination.

It always worked with my boss's laptop because that was
not on our net. He also remembered (from 3 years ago)
that we should have disconnected the net-attached
computer to get a console.

I have changed our net to 192.168.1.0 (255.255.255.0)
and it works great. Fortunately, we have fewer than 10
PCs to worry about - took only an afternoon to get it
right, changing fixed addresses on AS/400s and other
servers, etc.

So, Al, you might be able to use it after all   ;-)

This answer came from Lee Sutton, who posted it on
comp.sys.ibm.as400.misc. A coworker found it there.
There's a response from a Darryl Johns at IBM: "Talk
about unintended consequences!" I bet NONE of the
developers of this sat behind a LinkSys DSL gateway and
has to face this. Everything at IBM is probably class A
(10.0.0.0). Of course, LinkSys defaults to 192.168.1.1
(255.255.255.0) and someone from here had changed it. Oy!
Oy!

Sorry, I'm ranting a bit. Please disregard, somewhat,
these latter comments.

Vern - happy at last - I have a console! I use it for 2
boxes - just swap cables.
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.