You really should have just the one default gateway. Configure static routes to reach VLANs on other interfaces.
Cheers Ken From: N Parr [mailto:npar...@mortonind.com] Sent: Friday, 26 February 2010 1:45 AM To: NT System Admin Issues Subject: RE: gateway metric question Yes they are on on the same segment and there's no need to route. That being said all my VLANS including the ISCSI VLANs are routable between each other. I have a few pc's on dissimilar VLANS that weren't able to resolve the file server, when I added the gateway address to the ISCSI NIC they could then resolve the server name on the LAN Side. ________________________________ From: Richard Stovall [mailto:rich...@gmail.com] Sent: Thursday, February 25, 2010 10:51 AM To: NT System Admin Issues Subject: Re: gateway metric question Are all the iSCSI nodes on the same broadcast segment? If there's no need to route to a different segment, then you don't need a gateway on that NIC. Where did you read that about iSCSI client connectivity suffering without a gateway? None of our iSCSI clients or targets have gateways configured and I've never seen any issues because of it. Hope this helps, RS On Thu, Feb 25, 2010 at 11:36 AM, N Parr <npar...@mortonind.com<mailto:npar...@mortonind.com>> wrote: 2008 server with a LAN pointing NIC and an ISCSI pointing NIC on separate VLANS. Windows give you an warning if you have a gateway address set for both. But from what I understand it's a bad thing as far as client connectivity if you don't have the gateway entered on the ISCSI NIC. So should I bother setting a higher metric on the LAN facing nic or just let windows figure it out? The ISCSI connector is using IP's and forced out over the ISCSI NIC so DNS doesn't come in to play there. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
