Any Way to Lock TCP Traffic to One Router
- From: "Will" <westes-usc@xxxxxxxxxxxxxx>
- Date: Tue, 26 Sep 2006 22:13:33 -0700
Say I have the following machines and network:
- Computer A is on Class C 10.10.10.0
- Computer B is on Class C 10.10.20.0
- The two networks are joined by two routers, for fault tolerance.
Router 1 might use 10.10.10.1 and 10.10.20.1 for its interfaces, and Router
2 might use 10.10.10.2 and 10.10.20.2 for its interfaces.
- Computer A and Computer B are Windows 2000 or 2003 computers that each are
configured to use the two routers with equal metrics. Computer A would be
configured with equal metric routes to 10.10.10.1 and 10.10.10.2. Computer
B would be configured with equal metric routes to 10.10.20.1 and 10.10.20.2.
Given the above configuration, is there any way to lock a TCP connection
between Computer A and Computer B to a single router? In other words, is
there any way to have the receiving end of a TCP connection use the same
router for the return traffic that was used to send to that computer? I
don't want fragments of connections going through different network paths.
I'm hoping that either by default Microsoft is routing the return path to
the return traffic to the same router used to send, or that alternately this
behavior can be configured.
--
Will
.
- Follow-Ups:
- Re: Any Way to Lock TCP Traffic to One Router
- From: NetEng
- Re: Any Way to Lock TCP Traffic to One Router
- Prev by Date: changing IP subnet from class c to a
- Next by Date: SMB / CIFS slow versys NFS
- Previous by thread: changing IP subnet from class c to a
- Next by thread: Re: Any Way to Lock TCP Traffic to One Router
- Index(es):
Relevant Pages
|
