Your best bet is to put that one site on a separate machine. If it was
enough to saturate the T1, then it is probably working the machine's
resources pretty heavey as well. You should put it on a dedicated machine.
Then you won't have to worry about the routing issue at all and there is no
way this site could adversely effect any others if the load gets too heavey.
This is what we did with our own site. It is hosted at the ISP's location
but they have our site all by itself on a dedicated machine. We lease the
hardware from them and they maintain it and upgrade it as needed, it is
completely worry-free from our perspective. Yet we still maintain full
control of any content, components, or software that goes on the machine.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"Pete Mackey" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi! Help!?
>
> First, why...
> One of the 5 websites we host here on our server gets more traffic than
our
> T1 can hold. We cannot get rid of the T1 (contract), so a new fiber line
was
> ordered.
>
> Second, problem...
> The server has 3 Nics. 1 attaches to the network with the T1. 1 attaches
to
> a dedicated database server. 1 is available.
>
> The idea here is to use the available Nic for the fiber line. I do NOT
want
> the share the lines. I want to force traffic from the 1 website through
the
> fiber line. (note: the fiber line won't connect to network, just directly
to
> this NIC). I also need to make sure the requests from the fiber line go
back
> out through the fiber line.
>
> I know you can't use multiple default gateways on a machine, however,
> someone suggested possible using FQDN routing(?). I'm not even sure where
to
> start with this one.
>
> Any suggestions where I should start?
>
> Thanks for the help!
>
>