Hi I have a server 2003 server setup with 2 nics, one is setup with a static ip to connect directly to our san, the other connects to the lan . If I try and ping other machines from the server with both nics enabled the pings never come come back, if I disable the SAN nic I get replies......so im rather stuck at the moment on what to do as I need the SAN but also need the server to actually work and serve lan requests which at the moment is itnt.

I have LAN Nic set up as : 192.168.0.2 255.255.255.0 gateway 192.168.0.1 dns 192.168.0.2 this usually works fine, but when I enable the SAN network card that I have directly linked to the san I cannot then ping another pc (I added this so that all the SAN traffic goes into this card instead of clogging up the lan card). The san card is : 192.168.0.130 255.255.255.0 gateway left blank dns 192.168.0.2 The second card is causing havoc as soon it is disabled you can no longer ping another machine on the network from the server, all I want is a private network for the SAN to run on, so the main server card doesn't have to serve ISCSI requests AND lan traffic, but for some reason it doesnt want to play nicely with the main server NIC.

you can have only one default gateway and it is proabably configured for the SAN interface. remove the default gateway for this interface and it will be ok. If not, post the output of ipconfig /all and route print on the affected machineMCP/MCSA/MCTS/MCITP

I have only got one default gateway. thats why I put "gateway left blank" on the SAN config, the main server nic is set to gateway 192.168.0.1 I will post the routing info in a moment, I know its screwed up as I looked at it, but wasn't sure how to remedy the problem.

IPv4 Route Table =========================================================================== Interface List 0x1 ........................... MS TCP Loopback interface 0x80002 ...00 14 5e 46 13 81 ...... Broadcom NetXtreme Gigabit Ethernet 0x80003 ...00 1b 21 9c 19 44 ...... Intel(R) PRO/1000 GT Desktop Adapter #2 =========================================================================== =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.2 10 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 10 192.168.0.0 255.255.255.0 192.168.0.130 192.168.0.130 10 192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 10 192.168.0.130 255.255.255.255 127.0.0.1 127.0.0.1 10 192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2 10 192.168.0.255 255.255.255.255 192.168.0.130 192.168.0.130 10 212.96.161.238 255.255.255.255 192.168.0.1 192.168.0.2 10 224.0.0.0 240.0.0.0 192.168.0.2 192.168.0.2 10 224.0.0.0 240.0.0.0 192.168.0.130 192.168.0.130 10 255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2 1 255.255.255.255 255.255.255.255 192.168.0.130 192.168.0.130 1 Default Gateway: 192.168.0.1 =========================================================================== Persistent Routes: None Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp. B:\>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : classlinkbdc Primary Dns Suffix . . . . . . . : towerroad.com Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : towerroad.com Ethernet adapter LAN NIC: Connection-specific DNS Suffix . : towerroad.com Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet Physical Address. . . . . . . . . : 00-14-5E-46-13-81 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.0.2 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.0.1 DNS Servers . . . . . . . . . . . : 192.168.0.2 192.168.0.201 192.168.0.144 Ethernet adapter SAN NIC: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) PRO/1000 GT Desktop Adapter #2 Physical Address. . . . . . . . . : 00-1B-21-9C-19-44 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.0.130 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : DNS Servers . . . . . . . . . . . : 192.168.0.2 192.168.0.201 B:\>

It looks like you are using the same subnet 192.168.0.x on on both interfaces. If these NIC's are connected to fysicly different networks this explains why things do not work out. I would recommend creating a seperate subnet for your SAN devices. in fact you probably don't even need any routing between those subnets. For example give all LAN devices 192.168.0.x and all SAN devices 192.168.1.x Have your ip and subnetting thoroughly planned out, because changing ip's later on might not be that easy! http://support.microsoft.com/kb/164015MCP/MCSA/MCTS/MCITP

Ok thanks for your help, much appreciated, I will try putting the SAN on 192.168.1.* subnet and see if that solves the problem :)

Agree with SenneVL, separating NICs into different IP segments on a single host will avoid many unexpected issues in future, please also take look the article below: Expected Behavior of Multiple Adapters on Same Network http://support.microsoft.com/kb/175767 Thanks. Tiger Li Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.