|
Neil
Regards Vern
Vern,
I guess with a direct connection you're stuck with 192.168.0.x
If you run any software that enables SOCKS on your PC (the PC accesses the Internet through a firewall, such as Microsoft® Proxy Client, Hummingbird® SOCKS Client, NEC SOCKS 5, or others), you cannot route the subnet for 192.168.0.0 to the firewall. Operations Console uses addresses in the range of 192.168.0.0 to 192.168.0.255. Incorrect routing causes Operations Console to fail. Check your SOCKS configuration and make sure that the entry is: Direct 192.168.0.0 255.255.255.0
This may not help then if you are using direct connect cable and not a LAN console:
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/ic2924/index.htm?info/rzajr/rzajrchgnetvals.htm
PS - This V5R3 change for Ops Console may be of interest:
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/ic2924/index.htm?info/rzajr/rzajrconsoletakeoverandrecover.htm
...Neil
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.