Even typical routers won't do it. It is the way TCP/IP works,..it isn't
Windows and it isn't routers. However there is software that can deal with
certain things in certain situations.
Check out RainConnect or some of the other solutions by
www.rainfinity.com ,
but I can't say that you will find anything.
If it is a Cable or DSL Connection there are some Cable/DSL NAT devices that
have two WAN ports and can do certian types of "load balancing" between the
two links. I do not know of any exact models, but I do believe some of the
Linksys proucts can do that. But that is not what you are exactly asking for
either.
I also believe ISA Server can do this, but only in certain "Server
Publishing" stiuations. For example, if the ISA has multiple external IP#s
and it is being used to Publish an internal FTP Server on a certain external
address,...it will keep the FTP traffic on the proper IP# in both direction.
It required ISA2000 SP1 or newer. But I don't think that is a
solution,...it only works like that in certain situations.
The best thing to do is to not create a situation where it matters which
outbound path it takes.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"mymobile" <(E-Mail Removed)> wrote in message
news:E659629A-6C4D-4005-BE9F-(E-Mail Removed)...
> So does this mean that there is no way to do this using the built-in
features
> of Windows Server 2003 except if there is an aid of a certain router or
> special software?
>
> "Phillip Windell" wrote:
>
> > "mymobile" <(E-Mail Removed)> wrote in message
> > news:4234C4E7-A5FF-4850-9D2F-(E-Mail Removed)...
> > > My server is connected to two ISPs on different NICs. I have noticed
that
> > if
> > > I ping the IP of the ISP it receive the packets and sends back the
data
> > out
> > > to the other NIC. Is it possible to put a static route or something
that
> > > everytime a packet is received on the NIC, the NIC that received the
> > packet
> > > will send back the data using the NIC that received the packet.
> >
> > No. The inbound packet and the outbound packet are two entirely separate
> > communication sessions. The routes are determined independently for
each.
> >
> >
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
> >