RE: Selecting an ethernet line

["Andy Nolen-Parkhouse" <aparkhouse@xxxxxxxxx>]

Albert,

I don't know about the requirement for restarting TCP/IP, it doesn't
strike me as reasonable, but that doesn't mean it would not help.

I'm assuming that you have removed your old default route.

This should only work for connections initiated from the iSeries.
Connections initiated from the network should go to the IP address
specified in your DNS.  Would your network application have a problem
communicating to an IP address other than that specified in the DNS?

If all else fails, You could try ensuring that you only have the two
default routes bound to the different interfaces and then bounce TCP/IP
when you have the opportunity.  It doesn't make sense that this should be
required however.

Regards,
Andy


> bounces@xxxxxxxxxxxx] On Behalf Of York, Albert
> Subject: RE: Selecting an ethernet line
> 
> Andy,
> 
> I figured out how to create routes for each line. However, the AS/400
> seems
> to be ignoring the DUPRTEPTY parameter. It always selects the line in
> the
> order that I create the routes. I can tell this because I have an
> application that works on one line but not the other. I suspect the
> problem
> is caused by a missing firewall rule somewhere on the LAN.
> 
> If I inactivate the first interface the application works fine. If I
> create
> the route for the second interface first the application works fine.
> The
> result is always the same regardless of the value of DUPRTEPTY.
> 
> Do I  have to restart TCP/IP before it uses that value?
> 
> Thanks,
> 
> Albert