Chris,

  I have observed the behaviour you have described - "the initial connect
request through the REQUIRED_INTERFACE" - with the rest of the data going
out of the client through its primary interface, instead of the backup
interface.

  The only way we have been able to overcome this problem, from the client
side, is to set a static route on the client. However, this would not
correct the problem of the data coming into the server on its primary
interface. That would have to be corrected by your networking folks.

    Bryan

Bryan Bahnmiller
Agilent Technologies
Colorado Springs, CO 

> ***** I think it will still work *****
> Correct me if I am wrong, but the server will send a 
> connection request
> through the host interface specified in the file.  However, once the
> connection request has been send it turns it back over to the OS to
> determine the fastest route.  I just tested it and for the 
> clients that
> don't have a connect to the same subnet as the media servers 
> is works just
> like in the book...to them it is the fastest route since they 
> don't know any
> other.  They connect and send their traffic through that 
> interface.  For the
> clients that have a direct connect to the backup subnet, they 
> will get the
> initial connect request through the REQUIRED_INTERFACE  host 
> and then switch
> to the subnet with the direct connection since it is faster.  
> Does anyone
> see gotcha's with this?
> 
> Larry, unfortunately fixing the routing issue would involve 
> my network group
> and they don't view it as a high enough priority to fix.  
> Unfortunately,
> with all they are working right now I  would have to agree 
> with them.  Does
> my logic above make sense or am I completely messed up?
> 
> Thanks everyone so far for the input, it helps alot!
> Chris