That's the problem under 2008R2 - I can't set SkipAsSource on an existing address with netsh, and you've pointed out that I can't do it with Powershell either (well, not directly - I can wrap netsh in it.)
My tests indicate that I will have to remove the affected IP addresses, then add them back in with netsh using the SkipAsSource parameter.. I'm going to have to wait until the weekend, when the likelihood of various processes sending emails via SMTP is much lower, and I can remove the addresses manually, possibly reboot the box, then add the addresses back in with netsh using SkipAsSource during that process. Oh, BTW, and somewhat OT for this list - I forgot to ask again last time - what is the newest version of PS that's safe to load with Exchange 2010 on a 2008R2 box, both fully patched? I presume it's not 5, but will 3 or 4 be safe? Kurt On Fri, Jun 24, 2016 at 10:36 AM, Michael B. Smith <[email protected]> wrote: > Did you remember to set them ALL? All TRUE except for the one you want as > FALSE and set it to FALSE? > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Kurt Buff > Sent: Thursday, June 23, 2016 8:43 PM > To: ntsysadm > Subject: Re: [NTSysADM] 2008 R2 and SkipAsSource > > Sorry for the late response - just finished putting the Enterprise Agreement > to bed... > > Here's the page I'm working from, and its subsequent links: > https://blogs.technet.microsoft.com/rmilne/2012/02/08/fine-grained-control-when-registering-multiple-ip-addresses-on-a-network-card/ > > This article specifically uses SkipAsSource for controlling IP address > registrations on a computer with a single NIC and multiple IP addresses. > > I will also work with the EMS for set-receiveconnector and set-sendconnector, > but I want the DNS confusion to ends as well - I'm also looking to do with > with a couple of other server servers in our environment - notably our web > server(s). > > Kurt > > > > On Sun, Jun 19, 2016 at 3:44 PM, Michael B. Smith <[email protected]> > wrote: >> The NetTCPIP module isn't available on any OS before Server 2012, regardless >> of what version of WMF/PowerShell you install. >> >> I don't understand what you mean by "of course the host name is also showing >> up on these IP addresses". If you don't want them to register in DNS, you >> can do that in the GUI. That's not what SkipAsSource is about. >> >> If you are referring to the message header spit out by each transport, you >> change that with Exchange Management Shell. Set-ReceiveConnector and >> Set-SendConnector. >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Kurt Buff >> Sent: Saturday, June 18, 2016 5:30 PM >> To: ntsysadm >> Subject: [NTSysADM] 2008 R2 and SkipAsSource >> >> All, >> >> I've got an Exchange 2010 server running on 2008 R2 with multiple hub >> transports - but this isn't about Exchange as such. >> >> I've separated the extra SMTP transports onto different IP addresses, but of >> course the host name is also showing up on these IP addresses, and I'd like >> to put a stop to that, as it's causing some confusion. >> >> I've tried to use netsh to set SkipAsSource for the addresses used by the >> extra SMTP transports, and it's not working, including manually removing the >> addresses and re-adding them with netsh with the requisite options to set >> SkipAsSource. >> >> I've tried to apply https://support.microsoft.com/en-us/kb/2386184 >> (x64 version, to match the OS), but during installation it says that >> it isn't applicable and exits. When I search for that hotfix >> (get-hotfix) it doesn't show. The box is fully patched (except for this >> month's patches, which are coming next week). >> >> The machine has PowerShell v2 on it, which doesn't support setting >> SkipAsSource. >> >> So, two questions: >> >> o- What am I missing to configure SkipAsSource on this machine? >> >> o- What is the latest version of PowerShell that's safe to install with >> Exchange 2010, and would that work to set SkipAsSource? >> >> Thanks, >> >> Kurt >> >> > >
