Glenn,

look at this solution ; ( tested and worked very fine )

1^st ISP                          2^nd ISP                         3^rd ISP

 DSL                             DSL                             DSL

   |                                     |                                   |

   |                                     |                                   |

   --------------------|          |         |-------------------

                                 |          |         |

                            HUB ( not switch )

                                         |

Any Router that support OSPF to make load balancing to these 3 links

                                         |

                                         |

                         Your internal network

Note :

1- The collecting links device should be hub , not switch ( to avoid STP )

2- configure the OSPF on the router to include the three links in the same area, so it will load balancing any request to any link, and no link will be dedicated

---

From: "Thor (Hammer of God)" <thor@xxxxxxxxxxxxxxx>
Reply-To: isalist@xxxxxxxxxxxxx
To: "isalist@xxxxxxxxxxxxx" <isalist@xxxxxxxxxxxxx>
Subject: [isalist] Re: Proxy problems
Date: Mon, 17 Jul 2006 19:14:06 -0700

Yes, you could do something like this:

    ISP1     ISP2
     WAN1     WAN2
      |        |
[NetGear FVX 538 Box1]
          |
     LanFromBox1          ISP3
         WAN1             WAN2
           |               |
         [NetGear FVX 538 Box 2]
                      |
                   Int LAN



ISP1 and ISP2 go into NetGear Box 1.  You would want that guy to be in ?Fail-Over? mode.  Use DDNS just on 2 providers for inbound.  LAN from NetGear Box 1 goes into WAN1 on Netgear Box 2, with ISP3 going into WAN2.  This guy would be in ?Load-Balancing? mode.  All published services come from WAN1 on Box 2, which are already redundant because of Netgear Box 1.  Multiple HTTP requests would be LB between the combo of ISP1+ISP2 as ?one leg? with ISP3.   All internal users go to NetGear Box 2 for access.

Only drawback (if it really is a ?drawback?) is that there is no LB on the ISP1+ISP2 leg coming into WAN1 on the Netgear Box 2.  But that?s  OK- you just set the ?main? connection on Netgear Box 1 to the fastest ISP.  

The boxes are only $350 a piece ? and you can get the model one under the 538 (338?) even cheaper if you don?t need P2P VPN capabilities in-box.  That?s actually a pretty cool topology for under $700 in hardware.  You know, I?ve got an extra FVX538- I think I?ll order another DSL and do just that.  ;)

T




On 7/17/06 6:38 PM, "Glenn P. JOHNSTON" <glenn.johnston@xxxxxxxxxxx> spoketh to all:

Ok, I know what the first question the customer is going to ask, can they be cascaded ? combining 3 lines in 2 steps ?

I suppose they can, but are there any draw backs that jump to mind ?

---

From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Thor (Hammer of God)
Sent: Tuesday, 18 July 2006 11:35
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] Re: Proxy problems

Right- should have said that...  The Netgear FVX538 provides 2 WAN connections, not 3.  

t


On 7/17/06 6:25 PM, "Greg Mulholland" <gmulholland@xxxxxxxxxxxx> spoketh to all:

Havent seen a 3-way  (maybe before i die! ) but there is a nice little netgear floating around that  apparantly does a good job. I'll wait for thor to chime in with the details, I  looked at it and it seemed to do most of what i wanted. Might be a  start

Greg

----- Original Message -----  
 
From:  Glenn P. JOHNSTON <mailto:glenn.johnston@xxxxxxxxxxx>   
 
To: isalist@xxxxxxxxxxxxx  
 
Sent: Tuesday, July 18, 2006 11:15   AM
 
Subject: [isalist] Re: Proxy   problems
 

 
A little off topic, but I'm  sure that  someone on this list will have done this   before.

 
 
A customer wants to combine 2   or preferably 3 ADSL2 lines together for the added bandwidth &  more  importantly the reliability factor.

 
 
They can get 3 ADSL services   from 3 different telco's, which supposedly use different equipment at  the  local exchange.

 
 
What's the best way to bind   them together.

 
 
There will be inbound VPN  &  SMTP so the public DNS entries will have to cater for the  multiple public  IP's, but that easy stuff.

 
 
I found multiple   hardware & software solutions on the WEB, but nobody I know who   has actually used any and can tell me the un documented holes, or the  one that  just work, and those that really work  well.

 
 
Has anyone done this   ?

 
 
Any suggestions   ?

 
 
 

---

From: isalist-bounce@xxxxxxxxxxxxx  [mailto:isalist-bounce@xxxxxxxxxxxxx]  On Behalf Of Greg  Mulholland
Sent: Tuesday, 18 July  2006 09:19
To:  isalist@xxxxxxxxxxxxx
Subject:  [isalist] Re: Proxy  problems

 
 
Please let us know! in fact email John he will be  excited  to know.

 
 
Greg

 

----- Original Message -----  
 
From:  D PIETRUSZKA  USWRN INTERLINK INFRA  ASST MGR <mailto:DPietruszka@xxxxxx>   
 
To: isalist@xxxxxxxxxxxxx  
 
Sent: Tuesday, July 18, 2006 6:01   AM
 
Subject: [isalist] Re: Proxy   problems
 

 
 

Ok, ok don?t cry,  you can finish with that  poor customer.

Anyway, my proxy  starts working without any  apparent reason. I restarted the firewall as Jim  told me and  nothing, and about an hour latter I discover it was working   again.

I?ll see if this  happen  again.



 

Regards

Diego  R.  Pietruszka



    

 

---

From: isalist-bounce@xxxxxxxxxxxxx   [mailto:isalist-bounce@xxxxxxxxxxxxx]  On  Behalf Of John T (Lists)
Sent: Monday, July 17,  2006 3:01  PM
To: isalist@xxxxxxxxxxxxx
Subject:  [isalist] Re: Proxy  problems



Oh, excuse me  sir. Let me drop everything  including the work I am doing for a client that  was robbed and I am  trying to get them back all up and running to attend to  your problem  that you expect free instant help  on.



Gees, what did  you do take lessons from  Andrew?



 

John   T

eServices For   You



"Seek, and ye  shall  find!"



 

-----Original  Message-----
From:   isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx]  On Behalf Of D PIETRUSZKA USWRN  INTERLINK INFRA ASST  MGR
Sent: Monday, July 17, 2006 11:19  AM
To:  isalist@xxxxxxxxxxxxx
Subject: [isalist] Re: Proxy   problems



Helloooooo is  anybody at  home!



 

Regards

Diego  R.  Pietruszka



    

 

---

From:  isalist-bounce@xxxxxxxxxxxxx  [mailto:isalist-bounce@xxxxxxxxxxxxx]  On Behalf Of D PIETRUSZKA USWRN  INTERLINK INFRA ASST  MGR
Sent: Monday, July 17, 2006 12:50  PM
To:  isalist@xxxxxxxxxxxxx
Subject: [isalist] Proxy   problems



Hi  ISAList



I?m having this issue and I have  no idea  why, I will appreciate if somebody knows what is going   on.

We have a website https://vwa.msc.us  <https://vwa.msc.us/>  that is published on   12.32.217.149.

From outside everything work  fine, but from  inside I?m receiving the following  error:


 
  Network Access Message: The  page cannot  be  displayed  

 
    

 
  Technical Information (for Support personnel)   
 

• Error  Code: 504 Proxy Timeout. The  connection timed out. (10060)     
• IP  Address: 204.251.15.190  
• Date:  7/17/2006 4:42:49 PM  
• Server:  njisa17.interlink-intranet.net  
• Source:  proxy  
  

If I ping the website, its  resolving fine to  12.32.x.x but the error is showing another IP.   

If from my proxy server   (njisa17) I ping the website, the address returned it is also  correct.  

So, where is ISA keeping that  wrong  IP?????



Thanks for all your   answers.





Regards

Diego  R.  Pietruszka

MIS - Assistant   Manager

MSC (USA)  - Interlink Transport  Technologies