That's exactly what I thought - I just couldn't think of a reason why Lync would be different than any other application.
So, right now there are in effect two interior connections, which also seems problematic. I think I'll start the process of setting up the second NIC in the DMZ, giving it the DG, and setting the routes up manually for the NIC on the server subnet. That seems the cleanest way to me. Thanks, Kurt On Wed, Feb 27, 2013 at 5:08 PM, Michael B. Smith <mich...@smithcons.com> wrote: > Having multiple DGs is wrong. There can only be one default. > > Windows behavior is non-deterministic when you have specified multiple > default gateways. > > Almost certainly, the interior one needs to be eliminated and replaced by > either a routing table or a set of manual routes. > > -----Original Message----- > From: Kurt Buff [mailto:kurt.b...@gmail.com] > Sent: Wednesday, February 27, 2013 7:56 PM > To: NT System Admin Issues > Subject: Lync issue - something I don't quite understand... > > All, > > We've got a Lync 2010 infrastructure set up, but it's doing one little thing > that I'm not liking. > > The server has two NICs - each in a different subnet. One is in the same > subnet as the rest of our servers. The other is in a subnet that sits between > our L3 switch and our firewall - it's not a DMZ. > > I didn't set this up, but I was told that the intention was to set up the > second connection in the DMZ at the appropriate time for external access - > that hasn't happened yet, and I wasn't involved in the install, and know > little to nothing about Lync. > > The behavior I'm seeing is that I cannot ping the interface that's on the > server subnet at all, including from machines on that subnet (I can't RDP to > that IP address either). The name of the Lync server resolves to an IP > address, and which one you get depends on the state of DNS - you might get > back the one for the server subnet, or you might get back the other address. > I can ping the other address just fine. > > So, where I'm going with this is: Both NICs have default gateways assigned, > and in my experience, that's a largish mistake - only one interface should > have a DG. I suspect this is causing some other problems that we are seeing > as well > > However, the fellow who set this up swears that if I remove the DG from > either NIC, Lync will break. > > So, do any of you here know enough about Lync to say if having only one DG > will break it? > > Thanks, > > Kurt > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ > <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
