Question : Multi Homed Windows 2008 Server

I did a rebuild of a Windows 2003 box this weekend to 2008 server.  The server has 3 NICS in it.  Two of the NICS are teamed using the HP Network Configuration Utility on a production subnet 10.130.78.x/24  The third NIC is setup on a backup subnet 10.130.73.x/24 and no default gateway.  The problem I am having is that I can't get communication on the backup nic with any protocol from outside the subnet.  If I am on the 10.130.73.x subnet everything works.  Everything worked before the rebuild and  I have this exact same configuration on a windows 2003 server sitting right next to it and it works fine. There were no firewall/access rules changed and they are identical for both servers.  The way it works on the 2003 box is that Production traffic goes over the production NICS and the backup traffic goes to the media servers on the backup NICS.  No peristant route required or special configuration.  

I've tried putting in a persistant route on the 2008 box to no avail.  I've turned the firewall on for the public profile and set all outbound/inbound to allow all no success.  My concern is that because there is no DGW on the Backup NIC the NLA is showing it as an unidentified network and this is my problem.  I've scoured the forums, Google, Technet etc.. and not finding what I need to correct this issue.  Any help would be greatly appreciated.

Answer : Multi Homed Windows 2008 Server

When configuring a static route, you need the destination network, its mask, and the host IP of the interface that the traffic needs to go out.

So, if you have a multihomed server with 2 IPs: 10.10.10.100 and 172.16.10.100, and you want traffic to go to 192.168.10.100 (assuming that the router on the 172.16.10.0 network knows how to get to the 192.168.10.0 network), you use the following route statement:

route add 192.168.10.100 MASK 255.255.255.0 172.16.10.100 -p
Random Solutions  
 
programming4us programming4us