Yes I understand that now, actually understood it a long time ago to but my brain must have thought it wasn't worth remembering. Here's what I find strange in my situation. I've removed the un-necessary DNS and Gateway address's on the ISCSI NIC. Made sure the binding is set to the correct NIC. My DNS servers can resolve the problem server just fine. My clients that use those DNS servers can't resolve the problem server. So I start digging around and there's no Host A record on either of my DC's for the problem server. Well no wonder my clients have problems. But how are my DC's able to resolve in the first place and why isn't there a record?
________________________________ From: Ken Schaefer [mailto:k...@adopenstatic.com] Sent: Monday, March 01, 2010 9:41 AM To: NT System Admin Issues Subject: RE: gateway metric question It has nothing to do with virtual or Win2k8. It has everything to do with understanding basic IP routing. You should have one default gateway only. That's the whole point of a *default* gateway -> everything that doesn't have a defined route (either a subnet local to an adapter, or a defined route to a specific gateway) gets sent to the default gateway. Windows is just doing some intelligent stuff in the background to attempt to hide this basic fact from you. The solution to your problem (on all Windows OSes): a) Single default gateway b) On all other adapters where you have subnets you need to reach that are not link-local: define static route) Cheers Ken From: N Parr [mailto:npar...@mortonind.com] Sent: Monday, 1 March 2010 9:59 PM To: NT System Admin Issues Subject: RE: gateway metric question You may be on to something there. Although I don't know why this server would want to be a pain about it. I have one other server that does have all the DNS and Gateway info in the ISCSI adapter settings and it's been working fine for months. Maybe because it's 2003 and physical and the PITA one is 2008 and Virtual. ________________________________ From: Brian Desmond [mailto:br...@briandesmond.com] Sent: Sunday, February 28, 2010 1:32 PM To: NT System Admin Issues Subject: RE: gateway metric question Sounds like a binding order issue to me. Make sure you don't have DNS or WINS configured on the iSCSI NIC and that it's not configured to register in DNS also. Thanks, Brian Desmond br...@briandesmond.com <mailto:br...@briandesmond.com> c - 312.731.3132 From: N Parr [mailto:npar...@mortonind.com] Sent: Thursday, February 25, 2010 11: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> 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/> ~
