Configuring 2 NICs on a W2K8R2 server for different networks..?
JohnnyBiggles
Member Posts: 273
I tried to design a network for a SQL server to have 2 network connections: One would be to a web server on 192.168.100.x and the other would be to communicate with another SQL server on 192.168.200.x. Is this as easy as having 2 NICs with respective IP addresses and gateways to each separate network? {for example, NIC1 would be IP: 192.168.100.10/GW: 192.168.100.1 and NIC2 would be IP: 192.168.200.10/GW: 192.168.200.1} I keep getting the following warning before trying to save the adapter settings once the first one has been configured:
"Multiple default gateways are intended to provide redundancy to a single network (such as an intranet or the Internet). They will not function properly when the gateways are on two separate, disjoint networks (such as one on your intranet and one on the Internet). Do you want to save this configuration? [Yes/No]"
It sort of makes sense but is there routing involved that I have to configure on this server in order to direct traffic to the appropriate NIC?
"Multiple default gateways are intended to provide redundancy to a single network (such as an intranet or the Internet). They will not function properly when the gateways are on two separate, disjoint networks (such as one on your intranet and one on the Internet). Do you want to save this configuration? [Yes/No]"
It sort of makes sense but is there routing involved that I have to configure on this server in order to direct traffic to the appropriate NIC?
Comments
-
cruwl
Member Posts: 341 ■■□□□□□□□□
you only want 1 gateway. so only put a gateway on the adapter that actually has a gateway. The other adapter doesnt need the gateway if its only talking to the web server. -
JohnnyBiggles
Member Posts: 273
That's the thing... both the web server the SQl server talks to and the other SQL DB server it talks to are on different subnets from each interface, so wouldn't there need to be 2 gateways set?you only want 1 gateway. so only put a gateway on the adapter that actually has a gateway. The other adapter doesnt need the gateway if its only talking to the web server. -
sratakhin
Member Posts: 818
You should only configure one gateway on a NIC that is connected to the Internet. Then, add a static route to the remote network on the other NIC.
-
cruwl
Member Posts: 341 ■■□□□□□□□□
Looking at your diagram you have a total of 3 subnets. The IP scheme you give has 2, with each of the 2 nics on the same segment as the servers they are trying to get to correct? so you wouldnt and shouldnt need gateways or static routes.
-
JohnnyBiggles
Member Posts: 273
There are actually four subnets in that diagram. And no, each server is on a different subnet, or, at least connected to a different interface of the firewall, where the firewall interface is the gateway for each network.Looking at your diagram you have a total of 3 subnets. The IP scheme you give has 2, with each of the 2 nics on the same segment as the servers they are trying to get to correct? so you wouldnt and shouldnt need gateways or static routes. -
JohnnyBiggles
Member Posts: 273
This is what I ended up doing. So far, it seems to work properly.You should only configure one gateway on a NIC that is connected to the Internet. Then, add a static route to the remote network on the other NIC.
