Two internet connections in 1 PC
- Thread starter arialph
- Start date
- Status
D
DelJo63
using multiple NICs is possible, but usually done on servers to do load balancing.
your implementation *may* not be possible, binding one application to a specific NIC.
this article describe multihoming implementation on XP.
use your browser FIND to locate the occurance of multihome
IF the application can be configured to use a proxy connection, *maybe* that
might work, but frankly I doubt that approach.
your implementation *may* not be possible, binding one application to a specific NIC.
this article describe multihoming implementation on XP.
use your browser FIND to locate the occurance of multihome
IF the application can be configured to use a proxy connection, *maybe* that
might work, but frankly I doubt that approach.
D
DelJo63
multihome processing
The following is a summary of the network traffic behavior when a computer running Windows XP or Windows Server 2003 is connected to both a wired and wireless network (hereafter referred to as a multihomed computer):
(MS KB article here)
•
For traffic initiated by other computers that are neighbors of the multihomed computer, the traffic flows over the network adapter attached to the common subnet. For example, if a neighboring computer on the Ethernet-based subnet of the multihomed computer initiates traffic, the traffic flows over the Ethernet network adapter.
•
For traffic initiated by other remote computers (located beyond the locally attached subnets), the traffic flows over the network adapter corresponding to the destination IP address chosen by the initiating computer. For example, a multihomed Windows XP-based computer will register the IP addresses for both wired and wireless network adapters in the Domain Name System (DNS) using DNS dynamic update. When another computer queries for the name of the multihomed computer, it will get both of the multihomed computer's IP addresses in random order. The DNS client resolver in Windows XP chooses the first IP address in the list returned by the DNS server.
•
For traffic initiated by the multihomed computer for neighboring destinations, the traffic flows over the network adapter attached to the common subnet. For example, if a neighboring computer is on the Ethernet-based subnet of the multihomed computer, the traffic flows over the Ethernet network adapter.
•
For traffic initiated by the multihomed computer for remote destinations, the traffic flows over the network adapter associated with the currently chosen default route in the IP routing table, unless there are additional routes to the remote destination.
Assuming that the multihomed computer is running mostly client applications and accessing servers on remote subnets, most of the traffic of the multihomed computer is in the last category (traffic initiated by the multihomed computer for remote destinations).
The following is a summary of the network traffic behavior when a computer running Windows XP or Windows Server 2003 is connected to both a wired and wireless network (hereafter referred to as a multihomed computer):
(MS KB article here)
•
For traffic initiated by other computers that are neighbors of the multihomed computer, the traffic flows over the network adapter attached to the common subnet. For example, if a neighboring computer on the Ethernet-based subnet of the multihomed computer initiates traffic, the traffic flows over the Ethernet network adapter.
•
For traffic initiated by other remote computers (located beyond the locally attached subnets), the traffic flows over the network adapter corresponding to the destination IP address chosen by the initiating computer. For example, a multihomed Windows XP-based computer will register the IP addresses for both wired and wireless network adapters in the Domain Name System (DNS) using DNS dynamic update. When another computer queries for the name of the multihomed computer, it will get both of the multihomed computer's IP addresses in random order. The DNS client resolver in Windows XP chooses the first IP address in the list returned by the DNS server.
•
For traffic initiated by the multihomed computer for neighboring destinations, the traffic flows over the network adapter attached to the common subnet. For example, if a neighboring computer is on the Ethernet-based subnet of the multihomed computer, the traffic flows over the Ethernet network adapter.
•
For traffic initiated by the multihomed computer for remote destinations, the traffic flows over the network adapter associated with the currently chosen default route in the IP routing table, unless there are additional routes to the remote destination.
Assuming that the multihomed computer is running mostly client applications and accessing servers on remote subnets, most of the traffic of the multihomed computer is in the last category (traffic initiated by the multihomed computer for remote destinations).
Samstoned
Posts: 1,009 +0
I'm think'n vpn router config
if app is already to setup for speciic address
like media player that should work
you may need a managed switch/router
if not setup to config a address may need a managed 3rd party softs to allocate wan gateway
this is where the managed switch softwares comes in
use your firewall software to check ip workflow
I have a free snooper that checks and outpost firewall logs traffic
anyone got other Ideas lets toss'm around
ps :I'd like to have a setup like that
or T3 that would be great
if app is already to setup for speciic address
like media player that should work
you may need a managed switch/router
if not setup to config a address may need a managed 3rd party softs to allocate wan gateway
this is where the managed switch softwares comes in
use your firewall software to check ip workflow
I have a free snooper that checks and outpost firewall logs traffic
anyone got other Ideas lets toss'm around
ps :I'd like to have a setup like that
or T3 that would be great
- Status
