multiple internet connection at office
We have been using two separate Internet connections in our office. People will share internet connection by setting their gateways to either of these. Gateway is one of our local server through which internet is shared. So, we are using two local servers for two connections. Now problem is, if any connection is down, people have to manually change their gateways to the working connection.
How we can have multiple internet connection at office without people having to manually change their gateway settings? One of our server is windows XP and another is red hat.
Thanks in advance
EDIT
One requirement is that we need to have a server accessible via static ip
Use a router that connects to both ISPs and can handle the fail-over between ISPs when one goes down.
Use a dual-WAN router. On the low-end, the TP-LINK TL-R470T+ is around $60. On the higher end, consider the Cisco RV042.
Update: Some of the other answers suggest using a PC as a router. This is a more powerful and flexible solution. But it requires a lot more knowledge and effort on your part. If you don't have anyone available who is familiar with IP routing and NAT, it might not be the best idea. (I don't know of any easy-to-use, plug and play, PC solution.)
As Shane Madden advised, you need a router that can handle multiple Internet connections and failover (and usually load-balance) between the two connections.
One such firewall/router is pfSense. It's based on BSD's pf, is open source, and is highly stable (I have dozens in production, including load balancing/failover for several).
You only need a modestly-powered workstation (an old Pentium 4 with 512 to 1GB of RAM will be plenty) and three NICs (I'd avoid older Realteks and stick with Intel).
"One requirement is that we need to have a server accessible via static ip"
This is where things start to get pricey.
- A: Change the servers static IP if one line go down, and update DNS
- B: Use co-location at a facility with multiple ISP feeds
- C: Get dual ISP's with BGP feeds, and two routers with BGP+HSRP
A is clumsy and manual, B is everything from mediocre to expensive, C can be very expensive.
Unless you have a LARGE server farm then co-location should be the obvious choice - unless you have requirements to keep the server on the same LAN as your clients or other servers.