Followup on my problem - it's solved, and here's what the problems(s)
were and the solution(s)
Turns out that not only did both NICs have a DG, but the one that was
supposed to be present in the server subnet was in a switch port that
was tagged in a completely unrelated VLAN. No connectivity on
Oh, yeah - I also deselected Register with DNS on the NIC in the DMZ.
Kurt
On Fri, Mar 15, 2013 at 11:31 AM, Kurt Buff kurt.b...@gmail.com wrote:
Followup on my problem - it's solved, and here's what the problems(s)
were and the solution(s)
Turns out that not only did both NICs have a DG,
Ah wouldn't have been easier to just trash and start over, but congrats on
finding and fixing most of the issues. When you get the backups working
correctly you will at least know the correct way to set up Lync. Jon
Date: Fri, 15 Mar 2013 11:33:42 -0700
Subject: Re: Lync issue - something I
of the issues. When you get the backups working
correctly you will at least know the correct way to set up Lync.
Jon
Date: Fri, 15 Mar 2013 11:33:42 -0700
Subject: Re: Lync issue - something I don't quite understand...
From: kurt.b...@gmail.com
To: ntsysadmin@lyris.sunbelt-software.com
Oh, yeah
You got to love management that does not look before they leap!NOT! Jon
Date: Fri, 15 Mar 2013 18:05:01 -0700
Subject: Re: Lync issue - something I don't quite understand...
From: kurt.b...@gmail.com
To: ntsysadmin@lyris.sunbelt-software.com
Unfortunately starting over wasn't
System Admin Issues
Subject: Re: Lync issue - something I don't quite understand...
Thanks.
I'll try it again.
Kurt
On Wed, Feb 27, 2013 at 6:10 PM, Sean Martin seanmarti...@gmail.com wrote:
I haven't had any issues using the following syntax:
netsh interface ipv4 add route network/bitmask NIC
typos.
-Bonnie
-Original Message-
From: Kurt Buff [mailto:kurt.b...@gmail.com]
Sent: Wednesday, February 27, 2013 6:56 PM
To: NT System Admin Issues
Subject: Re: Lync issue - something I don't quite understand...
Thanks.
I'll try it again.
Kurt
On Wed, Feb 27, 2013 at 6:10 PM
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
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
In addition to what Michael already stated, disable DNS registration on the
NIC you don't want registering in DNS. Get used to managing static routes.
- Sean
On Wed, Feb 27, 2013 at 4:08 PM, Michael B. Smith mich...@smithcons.comwrote:
Having multiple DGs is wrong. There can only be one
Good idea on the DNS setting on the NIC. Thanks for that. I'll do that
for the one with the DG when I switch it to the DMZ.
I've managed many static routes (including on UAG 2010), so that's not
a problem.
But, I've noticed that Win2k8 R2 didn't seem to like it when I added
them via netsh - I
I haven't had any issues using the following syntax:
netsh interface ipv4 add route network/bitmask NIC name gateway IP
- Sean
On Wed, Feb 27, 2013 at 4:33 PM, Kurt Buff kurt.b...@gmail.com wrote:
Good idea on the DNS setting on the NIC. Thanks for that. I'll do that
for the one with the DG
Thanks.
I'll try it again.
Kurt
On Wed, Feb 27, 2013 at 6:10 PM, Sean Martin seanmarti...@gmail.com wrote:
I haven't had any issues using the following syntax:
netsh interface ipv4 add route network/bitmask NIC name gateway IP
- Sean
On Wed, Feb 27, 2013 at 4:33 PM, Kurt Buff
13 matches
Mail list logo
