Re: Custom OBDC Subsystem servicing jobs from wrong IP. -- MIDRANGE-L

× 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.

One thing I notice,

The specific IP address to route to the custom subsystem were entered
as individual IPs.

The subnet mask was left at the default of 255.255.255.0, does that
need to be 255.255.255.255?

-Charles

On Tue, Sep 1, 2009 at 10:08 AM, Charles Wilt<charles.wilt@xxxxxxxxx> wrote:

All,

We set up a specific subsystem to service ODBC/JDBC/ect jobs from a
particular set of IP address as describe in the following Centerfield
Newsletter:
http://www.centerfieldtechnology.com/publications/archive/August%202005%20Newsletter.pdf

Part of the process is to use iNav to specify the IP addresses whose
connections will be routed to the new custom subsystem.

Everything has been working fine for months.

Today we noticed that the QZDASOINIT jobs in that subsystem are
servicing a connection from an IP address other than the ones
specified for the subsystem.

I've doubled checked that the custom subsystem still has just the
original two IP address specified, so why is a connection from this
other IP address going to the custom subsystem instead of the default
QUSRWRK susbsystem?

I though perhaps when the connection first came in, the QUSRWRK jobs
were not available, so the connections went to the custom subsystem
jobs. However, after ending the two connected jobs, I got two new
connections in from the problem server still going to the custom
subsystem. I know the QUSRWRK subsystem jobs are there and I've got
lots of other connections going to them properly.

Does anybody have a clue as to what's going on?

Thanks!
Charles Wilt

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.