RE: Operations Console (was I5 systems in production)

[rob@xxxxxxxxx]

Glad to hear that.  We had that issue.  Our internal range is in the 10. 
Our DMZ is in the 192.  So, our Op's console PC would talk to most 
machines just fine.  But not to items in the DMZ until we did the hack. 
Then we upgraded the machines to i5 and HMC and dropped Op's Console.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Jeff Crosby" <jlcrosby@xxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
11/29/2004 11:30 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: Operations Console (was I5 systems in production)






> I can't find it at the moment, but I thought with the current 
> version(s) of OPS Console you could set the IP address range 
> being used. I have in the past working with the support 
> center done a REGISTRY HACK to set the IP address being used. 
> Try searching the registry using the REGEDIT for 192.168.0 
> and see what you find. 

As an FYI:

I talked to the guy who is helping me (or am I helping him?) with the
install and configure of ops console.  He used the registry hack as 
detailed
in another post and changed the IP address to 192.168.2.0 on the i5 in 
their
office.  Everything worked fine.

-- 
Jeff Crosby
Dilgard Frozen Foods, Inc.
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531

The opinions expressed are my own and not necessarily the opinion of my
company.  Unless I say so.



--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.