|
I added a route to the specific subnet of our bank. It seemed to work fine. Thanks. Thanks, Mark Mark D. Walter Senior Programmer/Analyst CCX, Inc. mwalter@xxxxxxxxxx http://www.ccxinc.com mwalter@hanoverwire. com To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> Sent by: cc: midrange-l-bounces@m Subject: RE: IP Issue idrange.com 05/11/2004 12:56 PM Please respond to Midrange Systems Technical Discussion Chris, Thanks for the reply. If I specify the preferred interface as our .2 interface, will that effect the domino SMTP server .151 from getting to the net? Thanks, Mark Mark D. Walter Senior Programmer/Analyst CCX, Inc. mwalter@xxxxxxxxxx http://www.ccxinc.com Chris Bipes <chris.bipes@cross-c To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> heck.com> cc: Sent by: Subject: RE: IP Issue midrange-l-bounces@m idrange.com 05/11/2004 12:01 PM Please respond to Midrange Systems Technical Discussion Define your route to the bank or the internet to use the interface you want. Then all outbound connections thru that route will use the same outbound IP. This will not affect inbound connections. For Example: ADDTCPRTE RTEDEST(*DFTROUTE) SUBNETMASK(*NONE) NEXTHOP('192.168.1.1') BINDIFC('192.168.1.2') Chris Bipes -----Original Message----- mwalter@xxxxxxxxxxxxxxx Hello all, I am having an issue with IP addresses. We have 3 interfaces defined for our single ethernet line. One is the regular interface for telnet and other stuff. It's internal IP is 192.168.0.2. We have two more for our two Domino Servers. .151 and .152 of our private network. I have static mappings defined in our Pix firewall that map the .2 address to xxx.xxx.xxx.102, and the .151 address to xxx.xxx.xxx.100. We connect to our bank via FTP. It allows the 102 public address into it's firewall. Suddenly, for no apparent reason, their firewall is seeing the 100 address. The firewall config still looks correct. Any idea why the iSeries is using the 151 address for FTP? Am I missing something here? Not even sure where to assign an interface to a TCP application. _______________________________________________ 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. _______________________________________________ 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.
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.
midrange.com
