2 NIC cards on a server

[Chiefcrowe]

In windows 2008 R2 environment, i have a server that has 2 NIC cards. They both connect to the same switch but they are 2 different subnets (10.1.100 and 10.1.101). I was wondering, if i use the gateways of 10.1.100.1 and 10.1.101.1, will there be any issues?
thanks,

 

[IndyColtsFan]

What are you trying to accomplish exactly? Generally, only 1 default gateway will be used by the server (at a time). Here are a few articles:

http://technet.microsoft.com/en-us/library/bb878104.aspx

http://support.microsoft.com/default.aspx?scid=kb;en-us;157025&Product=win2000

 

[classy]

In windows 2008 R2 environment, i have a server that has 2 NIC cards. They both connect to the same switch but they are 2 different subnets (10.1.100 and 10.1.101). I was wondering, if i use the gateways of 10.1.100.1 and 10.1.101.1, will there be any issues?
thanks,

In most cases yes. Multiple gateways on a server functioning only as a server is bad unless properly setup. Indy posted how to make it work.

 

[Chiefcrowe]

Thanks for the replies. So, generally one should use the same gateway for the 2 subnets?
they both are on the same switch and can communicate with each other fine and so far i have not seen any issues. This network (both subnets) is internal only and cannot be accessed from the outside (without a vpn).
I was asked to use a different subnet because of a new San device added to our area.

 

[seepy83]

You most likely don't need to define a Default Gateway for the SAN subnet. The default gateway is used when the host doesn't know where to send the packet (i.e. it's trying to send to a device on another network/subnet and needs to use a routing device (default gateway) to get the packets there).

 

[imagoon]

Don't define gateways on the SAN network. There is rarely a reason to do so (on the clients at least.) The SAN itself might have a gateway setting (and may support one for each network) but that is typically for SAN to SAN replication. Also... They should be completely isolated. There is no reason to even support a VPN connection to them The SAN will have a management port(s). Those should be connected to an accessible service network. The iSCSI networks should not be. In most cases you will be using specialized ethernet settings that will not survive well in the regular network and you have to consider security because someone can access "raw disk" if they can connect to the targets.

 

[Emulex]

you need to define a gateway for a san network but you should never need to use it. even vcenter asks for one but it doesn't make any sense.

 

[imagoon]

you need to define a gateway for a san network but you should never need to use it. even vcenter asks for one but it doesn't make any sense.

All of my vcenter servers, esxi hosts and windows boxes on SANs do not have gateway addresses on the san networks. It never asked nor required it anywhere.