13 replies
by ebob
Each NIC absolutely needs it's own network (IP) address. They can be on the same network/subnet, but I don't see how you can manage different types of traffic on each NIC.
If the services with which you want to communicate are on different subnets, then your task is easier. And obviously the address of each NIC is necessarily different and traffic management is made simpler.
by mc428
by chris hirst
by mc428
by krish_72
by mc428
If talking about TCP/ip protocol, you MUST set a different ip address for each ni card, (or different subnets, one for each nic)
The only way (i know) to deliver packets from one nic and not by the other, is by ip address, port or subnet.
The cardin the same subnet as the server, will be only use to logon to the server and access all computers on that network, and the other card will access all computers on the other network. No matter if both nic cards are connected to the same hub, the subnets will be isolated, due to the fact that they belong to different scopes.
In order to "Talk" between the 2 networks , you must set up a router or "enable ip forwarding " under tcp ip properties.
Hope it helps!
by mc428
by wannadrunk®
I never had any experience with the different NIC brand to form the Load Balancing, Fault Tolerant or FastEther Channel.
I am using 2 Intel NICs, same model e.g. Pro10/100 NICs plus drivers/software provided by Intel installed and setup the Team Adapter.
by mc428
by mc428
by mc428
by mc428
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending