"Julien" <(E-Mail Removed)> wrote in message
news:89F90284-84E5-4049-8F96-(E-Mail Removed)...
> Sorry, I answered too quickly and I mut have msitaken your answer with
> another one somebody made me on another forum. Whatever.
>
> So to be clear for you there's absolutely no way to loadbalanced Home user
> lines directly from windows server ? I got to use specific network
> equipement
> to do that ?
Windows can do "Dead Gateway Detection" which is a very "crude" form of
Fail-Over (not load balancing)
128978 - Dead Gateway Detection in TCP/IP for Windows NT
http://support.microsoft.com/default...b;EN-US;128978
171564 - TCP/IP Dead Gateway Detection Algorithm Updated for Windows NT
http://support.microsoft.com/default...b;EN-US;171564
> That seems strange as long as that problematic seems quite common , but i
> cant find anything on the web about such a solution so I begin to believe
> you
> actually ...
It has been that way for years (about 10 years actually). So it is old news
to those of us that have been with Windows for a long time. The generic
TCP/IP Protocol, by itself, alone, just is not capable of such things.
Therefore it has to be over come with "software" at a higher lever in the
OSI model,..perhaps ever completely above the OSI model (hard to pin down
exactly where it all has to happen at). But anyway, Windows as an OS just
doesn't do it.
In routers,..that is "real" routers,...not home-user/consumer boxes that are
falsely called routers,...this would be done with Dynamic Routing Protocols
(like IGRP). Dynamic Routing Protocols are idealy suited to do this and it
is more or less what they do naturally anyway.
When "home user" line technologies were invented, meaning DSL and CableTV
Internet, they introduced new methodologies into how lines work. These
"home-user" boxes,...and even now some of the middle-range devices (like the
$400-$500 boxes from Cisco, Sonicwall, Watchgaurd) have the ability to do
this wilt two lines that are not even from the same ISP. IT is done with
some proprietary or semi-proprietary methods that do not involve Dynamic
Routing Protocols. Some companies may even be producing high-end Firewall
appliances that do this as well.
However because the two lines are seen on the Internet by two different IP#s
it only works outbound as far as I know. But the commercial lines (like
T1s) this can be done in both directions because the Destination via both
"paths" is identified by the same IP# and the Dynamic Routing Protocols make
it all happen.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------