Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Kurt Buff]

First time I've run into that problem. It's definitely going to stick in my
brain.

Kurt

On Fri, Jul 28, 2017 at 10:17 AM, Andrew S. Baker <asbz...@gmail.com> wrote:

> I didn't think to ask about WAN accelerators, but they are suspect in WAN
> related Microsoft networking...
>
> Regards,
>
>  *ASB*
>  *http://XeeMe.com/AndrewBaker <http://xeeme.com/AndrewBaker>*
>
>  *Providing Expert Technology Consulting Services for the SMB market…*
>
> * GPG: *860D 40A1 4DA5 3AE1 B052 8F9F 07A1 F9D6 A549 8842
>
>
>
> On Thu, Jul 27, 2017 at 6:53 PM, Kurt Buff <kurt.b...@gmail.com> wrote:
>
>> It turns out that our Riverbed WAN accelerators were the problem.
>>
>> Don't know why that would be, but while working with MSFT support, I
>> turned off the optimization for the Riverbed at each end, and it went
>> through with nary a hiccup.
>>
>> This worked without a flaw, creating one Replication Group, and then
>> creating many Replicated Folders under that RG, between two servers, and
>> it's supposed to be one-way replication, which I'll test tomorrow. It also
>> sets up the connection schedule, using the local time for the receiving
>> computer
>>
>> However, I might not have gotten the connection schedule correct, because
>> when I check the schedule in the GUI, it's set up for full speed
>> replication 24x7, when it should be 512kbits/sec during the receiving
>> computer's business hours. I'm going to let that cook overnight to see if
>> that updates itself.
>>
>> This was a fun project, modulo the frustration with getting the script
>> past the errors induced by the Riverbeds.
>>
>> I'm not real proud of the script, as it does no error checking, no
>> prompting for user input, etc., but it got the job done. I've stripped out
>> the comments and write-host stuff for the sake of brevity, and wanted to
>> share it with y'all. Hope someone finds it useful.
>>
>> Kurt
>>
>> Tab-Delimited CSV, with header and one entry
>>
>> --Begin NewDFSr.csv--
>> GroupNameSourceComputerFolderNameSourcePrimaryMember
>> SourceContentPathSourceStagingPathQuotaInMBDestinationComputer
>> DestinationContentPathDestinationReadOnly
>> US2AU-Engineeringusfs01pTC-39.3TRUE
>> K:\Engineering\TestCandidates\Folder1\CurrentVersions10240
>> aufs01pE:\Engineering\TestCandidates\Folder1\CurrentVersionsTRUE
>> --End NewDFSR.csv--
>>
>> --Begin Script--
>> $NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
>> $NewGroupName = "US2AU-Engineering"
>> New-DfsReplicationGroup -GroupName $NewGroupName
>> Add-DfsrMember -GroupName $NewGroupName -ComputerName usfs01p, aufs01p
>> Add-DfsrConnection -GroupName $NewGroupName -SourceComputerName
>> $SourceComputer -DestinationComputerName $DestinationComputer
>>
>> Foreach ($Line in $NewDFSR)
>>{
>> $SourceComputer = $Line.SourceComputer
>> $FolderName = $Line.FolderName
>> $SourceContentPath = $Line.SourceContentPath
>> $SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
>> $SourcePrimaryMember = [System.Convert]::ToBoolean($L
>> ine.SourcePrimaryMember)
>> $DestinationComputer = $Line.DestinationComputer
>> $DestinationContentPath = $Line.DestinationContentPath
>> $DestinationReadOnly = [System.Convert]::ToBoolean($L
>> ine.DestinationReadOnly)
>> New-DfsReplicatedFolder -GroupName $NewGroupName -FolderName
>> $FolderName
>> Set-DfsrMembership -GroupName $NewGroupName -FolderName $FolderName
>> -ComputerName $SourceComputer -ContentPath $SourceContentPath
>> -PrimaryMember $SourcePrimaryMember -StagingPathQuotaInMB
>> $SourceStagingPathQuotaInMB -Force
>> Set-DfsrMembership -GroupName $NewGroupName -FolderName $FolderName
>> -ComputerName $DestinationComputer -ContentPath $DestinationContentPath
>> -ReadOnly $DestinationReadOnly -Force
>> }
>>
>> Set-DfsrConnectionSchedule -GroupName $NewGroupName -SourceComputerName
>> $SourceComputer -DestinationComputerName $DestinationComputer -Day
>> 1,2,3,4,5 -BandwidthDetail "f
>> fffffffffffffffffff"
>> Update-DfsrConfigurationFromAD -ComputerName
>> $SourceComputer,$DestinationComputer
>> --End Script--
>>
>>
>>
>> On Mon, Jul 24, 2017 at 3:30 PM, Michael B. Smith <mich...@smithcons.com>
>> wrote:
>&

Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Andrew S. Baker]

I didn't think to ask about WAN accelerators, but they are suspect in WAN
related Microsoft networking...

Regards,

 *ASB*
 *http://XeeMe.com/AndrewBaker <http://xeeme.com/AndrewBaker>*

 *Providing Expert Technology Consulting Services for the SMB market…*

* GPG: *860D 40A1 4DA5 3AE1 B052 8F9F 07A1 F9D6 A549 8842



On Thu, Jul 27, 2017 at 6:53 PM, Kurt Buff <kurt.b...@gmail.com> wrote:

> It turns out that our Riverbed WAN accelerators were the problem.
>
> Don't know why that would be, but while working with MSFT support, I
> turned off the optimization for the Riverbed at each end, and it went
> through with nary a hiccup.
>
> This worked without a flaw, creating one Replication Group, and then
> creating many Replicated Folders under that RG, between two servers, and
> it's supposed to be one-way replication, which I'll test tomorrow. It also
> sets up the connection schedule, using the local time for the receiving
> computer
>
> However, I might not have gotten the connection schedule correct, because
> when I check the schedule in the GUI, it's set up for full speed
> replication 24x7, when it should be 512kbits/sec during the receiving
> computer's business hours. I'm going to let that cook overnight to see if
> that updates itself.
>
> This was a fun project, modulo the frustration with getting the script
> past the errors induced by the Riverbeds.
>
> I'm not real proud of the script, as it does no error checking, no
> prompting for user input, etc., but it got the job done. I've stripped out
> the comments and write-host stuff for the sake of brevity, and wanted to
> share it with y'all. Hope someone finds it useful.
>
> Kurt
>
> Tab-Delimited CSV, with header and one entry
>
> --Begin NewDFSr.csv--
> GroupNameSourceComputerFolderNameSourcePrimaryMember
> SourceContentPathSourceStagingPathQuotaInMBDestinationComputer
> DestinationContentPathDestinationReadOnly
> US2AU-Engineeringusfs01pTC-39.3TRUE
> K:\Engineering\TestCandidates\Folder1\CurrentVersions10240
> aufs01pE:\Engineering\TestCandidates\Folder1\CurrentVersionsTRUE
> --End NewDFSR.csv--
>
> --Begin Script--
> $NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
> $NewGroupName = "US2AU-Engineering"
> New-DfsReplicationGroup -GroupName $NewGroupName
> Add-DfsrMember -GroupName $NewGroupName -ComputerName usfs01p, aufs01p
> Add-DfsrConnection -GroupName $NewGroupName -SourceComputerName
> $SourceComputer -DestinationComputerName $DestinationComputer
>
> Foreach ($Line in $NewDFSR)
>{
> $SourceComputer = $Line.SourceComputer
> $FolderName = $Line.FolderName
> $SourceContentPath = $Line.SourceContentPath
> $SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
> $SourcePrimaryMember = [System.Convert]::ToBoolean($
> Line.SourcePrimaryMember)
> $DestinationComputer = $Line.DestinationComputer
> $DestinationContentPath = $Line.DestinationContentPath
> $DestinationReadOnly = [System.Convert]::ToBoolean($
> Line.DestinationReadOnly)
> New-DfsReplicatedFolder -GroupName $NewGroupName -FolderName
> $FolderName
> Set-DfsrMembership -GroupName $NewGroupName -FolderName $FolderName
> -ComputerName $SourceComputer -ContentPath $SourceContentPath
> -PrimaryMember $SourcePrimaryMember -StagingPathQuotaInMB
> $SourceStagingPathQuotaInMB -Force
> Set-DfsrMembership -GroupName $NewGroupName -FolderName $FolderName
> -ComputerName $DestinationComputer -ContentPath $DestinationContentPath
> -ReadOnly $DestinationReadOnly -Force
> }
>
> Set-DfsrConnectionSchedule -GroupName $NewGroupName -SourceComputerName
> $SourceComputer -DestinationComputerName $DestinationComputer -Day
> 1,2,3,4,5 -BandwidthDetail "ff
> ff"
> Update-DfsrConfigurationFromAD -ComputerName $SourceComputer,$
> DestinationComputer
> --End Script--
>
>
>
> On Mon, Jul 24, 2017 at 3:30 PM, Michael B. Smith <mich...@smithcons.com>
> wrote:
>
>> And do you have errors in the DFS specific event logs?
>>
>>
>>
>> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.myitf
>> orum.com] *On Behalf Of *Michael B. Smith
>> *Sent:* Monday, July 24, 2017 6:22 PM
>> *To:* ntsysadm@lists.myitforum.com
>> *Subject:* RE: [NTSysADM] RPC not available on remote machine while
>> doing DFSR config
>>
>>
>>
>> 609 ms? Wow.
>>
>>
>>
>> I suspect that is a hint. Let’s do a bit more:
>>
>>
>>
>>  

RE: Huzzah! Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Melvin Backus]

If you're going to be a comic you should definitely strive to be a big one. The 
little ones don't make any money. J

--
There are 10 kinds of people in the world...
 those who understand binary and those who don't.

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Michael B. Smith
Sent: Friday, July 28, 2017 7:20 AM
To: ntsysadm@lists.myitforum.com
Subject: RE: Huzzah! Re: [NTSysADM] RPC not available on remote machine while 
doing DFSR config

Hey now!

:)

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Webster
Sent: Friday, July 28, 2017 6:22 AM
To: ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com>; ntsysadm
Subject: Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine while 
doing DFSR config

Comic Sans 72 point font of knowledge

webster

Get Outlook for iOS<https://aka.ms/o0ukef>

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
<listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>> on 
behalf of Kurt Buff <kurt.b...@gmail.com<mailto:kurt.b...@gmail.com>>
Sent: Thursday, July 27, 2017 7:52:07 PM
To: ntsysadm
Subject: Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine while 
doing DFSR config

Another thing I didn't know. You, sir, are a veritable font of knowledge.

I guess we're either lucky or good, or both. We have Exchange 2010
servers (CAS server and DB server in the US, and single machine with
CAS/DB in AU) in these two offices as well, and haven't seen any
problems between them

Kurt

On Thu, Jul 27, 2017 at 5:38 PM, Michael B. Smith 
<mich...@smithcons.com<mailto:mich...@smithcons.com>> wrote:
> I think there is a pretty good chance that I would've suggested you try 
> bypassing them.  :-)
>
> I know that they can break Exchange if not properly precisely configured.
>
> -Original Message-
> From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
> [mailto:listsad...@lists.myitforum.com] On Behalf Of Kurt Buff
> Sent: Thursday, July 27, 2017 8:18 PM
> To: ntsysadm
> Subject: Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine while 
> doing DFSR config
>
> If you had known, would you have figured it out? :)
>
> I'm sure I'll remember this for quite a while, though.
>
> And thank you very much for your help, BTW - as always, much appreciated.
>
> Kurt
>
> On Thu, Jul 27, 2017 at 4:02 PM, Michael B. Smith 
> <mich...@smithcons.com<mailto:mich...@smithcons.com>> wrote:
>>
>> Well, I never would've figured that out! I didn't even know you had WAN 
>> accelerators. J
>>
>>
>>
>> I'm glad you got it resolved!
>
>

RE: Huzzah! Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Michael B. Smith]

Hey now!

:)

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Webster
Sent: Friday, July 28, 2017 6:22 AM
To: ntsysadm@lists.myitforum.com; ntsysadm
Subject: Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine while 
doing DFSR config

Comic Sans 72 point font of knowledge

webster

Get Outlook for iOS<https://aka.ms/o0ukef>

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
<listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>> on 
behalf of Kurt Buff <kurt.b...@gmail.com<mailto:kurt.b...@gmail.com>>
Sent: Thursday, July 27, 2017 7:52:07 PM
To: ntsysadm
Subject: Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine while 
doing DFSR config

Another thing I didn't know. You, sir, are a veritable font of knowledge.

I guess we're either lucky or good, or both. We have Exchange 2010
servers (CAS server and DB server in the US, and single machine with
CAS/DB in AU) in these two offices as well, and haven't seen any
problems between them

Kurt

On Thu, Jul 27, 2017 at 5:38 PM, Michael B. Smith 
<mich...@smithcons.com<mailto:mich...@smithcons.com>> wrote:
> I think there is a pretty good chance that I would've suggested you try 
> bypassing them.  :-)
>
> I know that they can break Exchange if not properly precisely configured.
>
> -Original Message-
> From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
> [mailto:listsad...@lists.myitforum.com] On Behalf Of Kurt Buff
> Sent: Thursday, July 27, 2017 8:18 PM
> To: ntsysadm
> Subject: Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine while 
> doing DFSR config
>
> If you had known, would you have figured it out? :)
>
> I'm sure I'll remember this for quite a while, though.
>
> And thank you very much for your help, BTW - as always, much appreciated.
>
> Kurt
>
> On Thu, Jul 27, 2017 at 4:02 PM, Michael B. Smith 
> <mich...@smithcons.com<mailto:mich...@smithcons.com>> wrote:
>>
>> Well, I never would've figured that out! I didn't even know you had WAN 
>> accelerators. J
>>
>>
>>
>> I'm glad you got it resolved!
>
>

Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Webster]

Comic Sans 72 point font of knowledge

webster

Get Outlook for iOS<https://aka.ms/o0ukef>

From: listsad...@lists.myitforum.com <listsad...@lists.myitforum.com> on behalf 
of Kurt Buff <kurt.b...@gmail.com>
Sent: Thursday, July 27, 2017 7:52:07 PM
To: ntsysadm
Subject: Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine while 
doing DFSR config

Another thing I didn't know. You, sir, are a veritable font of knowledge.

I guess we're either lucky or good, or both. We have Exchange 2010
servers (CAS server and DB server in the US, and single machine with
CAS/DB in AU) in these two offices as well, and haven't seen any
problems between them

Kurt

On Thu, Jul 27, 2017 at 5:38 PM, Michael B. Smith <mich...@smithcons.com> wrote:
> I think there is a pretty good chance that I would've suggested you try 
> bypassing them.  :-)
>
> I know that they can break Exchange if not properly precisely configured.
>
> -Original Message-
> From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] 
> On Behalf Of Kurt Buff
> Sent: Thursday, July 27, 2017 8:18 PM
> To: ntsysadm
> Subject: Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine while 
> doing DFSR config
>
> If you had known, would you have figured it out? :)
>
> I'm sure I'll remember this for quite a while, though.
>
> And thank you very much for your help, BTW - as always, much appreciated.
>
> Kurt
>
> On Thu, Jul 27, 2017 at 4:02 PM, Michael B. Smith <mich...@smithcons.com> 
> wrote:
>>
>> Well, I never would’ve figured that out! I didn’t even know you had WAN 
>> accelerators. J
>>
>>
>>
>> I’m glad you got it resolved!
>
>

Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Kurt Buff]

I wish...

On Thu, Jul 27, 2017 at 6:32 PM, J- P <jnat...@hotmail.com> wrote:

> just make sure you back charge Riverbed for the PSS ticket [image: ]
>
>
>
> Jean-Paul Natola
>
>
>
> --
> *From:* listsad...@lists.myitforum.com <listsad...@lists.myitforum.com>
> on behalf of Kurt Buff <kurt.b...@gmail.com>
> *Sent:* Thursday, July 27, 2017 8:52 PM
> *To:* ntsysadm
> *Subject:* Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine
> while doing DFSR config
>
> Another thing I didn't know. You, sir, are a veritable font of knowledge.
>
> I guess we're either lucky or good, or both. We have Exchange 2010
> servers (CAS server and DB server in the US, and single machine with
> CAS/DB in AU) in these two offices as well, and haven't seen any
> problems between them
>
> Kurt
>
>
> On Thu, Jul 27, 2017 at 5:38 PM, Michael B. Smith <mich...@smithcons.com>
> wrote:
> > I think there is a pretty good chance that I would've suggested you try
> bypassing them.  :-)
> >
> > I know that they can break Exchange if not properly precisely configured.
> >
> > -Original Message-
> > From: listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com <listsad...@lists.myitforum.com>] On Behalf Of Kurt Buff
> > Sent: Thursday, July 27, 2017 8:18 PM
> > To: ntsysadm
> > Subject: Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine
> while doing DFSR config
> >
> > If you had known, would you have figured it out? :)
> >
> > I'm sure I'll remember this for quite a while, though.
> >
> > And thank you very much for your help, BTW - as always, much appreciated.
> >
> > Kurt
> >
> > On Thu, Jul 27, 2017 at 4:02 PM, Michael B. Smith <mich...@smithcons.com>
> wrote:
> >>
> >> Well, I never would’ve figured that out! I didn’t even know you had WAN
> accelerators. J
> >>
> >>
> >>
> >> I’m glad you got it resolved!
> >
> >
>
>
>

Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[J- P]

just make sure you back charge Riverbed for the PSS ticket 



Jean-Paul Natola




From: listsad...@lists.myitforum.com <listsad...@lists.myitforum.com> on behalf 
of Kurt Buff <kurt.b...@gmail.com>
Sent: Thursday, July 27, 2017 8:52 PM
To: ntsysadm
Subject: Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine while 
doing DFSR config

Another thing I didn't know. You, sir, are a veritable font of knowledge.

I guess we're either lucky or good, or both. We have Exchange 2010
servers (CAS server and DB server in the US, and single machine with
CAS/DB in AU) in these two offices as well, and haven't seen any
problems between them

Kurt

On Thu, Jul 27, 2017 at 5:38 PM, Michael B. Smith <mich...@smithcons.com> wrote:
> I think there is a pretty good chance that I would've suggested you try 
> bypassing them.  :-)
>
> I know that they can break Exchange if not properly precisely configured.
>
> -Original Message-
> From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] 
> On Behalf Of Kurt Buff
> Sent: Thursday, July 27, 2017 8:18 PM
> To: ntsysadm
> Subject: Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine while 
> doing DFSR config
>
> If you had known, would you have figured it out? :)
>
> I'm sure I'll remember this for quite a while, though.
>
> And thank you very much for your help, BTW - as always, much appreciated.
>
> Kurt
>
> On Thu, Jul 27, 2017 at 4:02 PM, Michael B. Smith <mich...@smithcons.com> 
> wrote:
>>
>> Well, I never would’ve figured that out! I didn’t even know you had WAN 
>> accelerators. J
>>
>>
>>
>> I’m glad you got it resolved!
>
>

Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Kurt Buff]

Another thing I didn't know. You, sir, are a veritable font of knowledge.

I guess we're either lucky or good, or both. We have Exchange 2010
servers (CAS server and DB server in the US, and single machine with
CAS/DB in AU) in these two offices as well, and haven't seen any
problems between them

Kurt

On Thu, Jul 27, 2017 at 5:38 PM, Michael B. Smith <mich...@smithcons.com> wrote:
> I think there is a pretty good chance that I would've suggested you try 
> bypassing them.  :-)
>
> I know that they can break Exchange if not properly precisely configured.
>
> -Original Message-
> From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] 
> On Behalf Of Kurt Buff
> Sent: Thursday, July 27, 2017 8:18 PM
> To: ntsysadm
> Subject: Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine while 
> doing DFSR config
>
> If you had known, would you have figured it out? :)
>
> I'm sure I'll remember this for quite a while, though.
>
> And thank you very much for your help, BTW - as always, much appreciated.
>
> Kurt
>
> On Thu, Jul 27, 2017 at 4:02 PM, Michael B. Smith <mich...@smithcons.com> 
> wrote:
>>
>> Well, I never would’ve figured that out! I didn’t even know you had WAN 
>> accelerators. J
>>
>>
>>
>> I’m glad you got it resolved!
>
>

Re: Huzzah! Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Kurt Buff]

If you had known, would you have figured it out? :)

I'm sure I'll remember this for quite a while, though.

And thank you very much for your help, BTW - as always, much appreciated.

Kurt

On Thu, Jul 27, 2017 at 4:02 PM, Michael B. Smith  wrote:
>
> Well, I never would’ve figured that out! I didn’t even know you had WAN 
> accelerators. J
>
>
>
> I’m glad you got it resolved!

RE: Huzzah! Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Michael B. Smith]

Well, I never would’ve figured that out! I didn’t even know you had WAN 
accelerators. ☺

I’m glad you got it resolved!

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Kurt Buff
Sent: Thursday, July 27, 2017 6:53 PM
To: ntsysadm
Subject: Huzzah! Re: [NTSysADM] RPC not available on remote machine while doing 
DFSR config

It turns out that our Riverbed WAN accelerators were the problem.
Don't know why that would be, but while working with MSFT support, I turned off 
the optimization for the Riverbed at each end, and it went through with nary a 
hiccup.
This worked without a flaw, creating one Replication Group, and then creating 
many Replicated Folders under that RG, between two servers, and it's supposed 
to be one-way replication, which I'll test tomorrow. It also sets up the 
connection schedule, using the local time for the receiving computer

However, I might not have gotten the connection schedule correct, because when 
I check the schedule in the GUI, it's set up for full speed replication 24x7, 
when it should be 512kbits/sec during the receiving computer's business hours. 
I'm going to let that cook overnight to see if that updates itself.
This was a fun project, modulo the frustration with getting the script past the 
errors induced by the Riverbeds.
I'm not real proud of the script, as it does no error checking, no prompting 
for user input, etc., but it got the job done. I've stripped out the comments 
and write-host stuff for the sake of brevity, and wanted to share it with 
y'all. Hope someone finds it useful.

Kurt

Tab-Delimited CSV, with header and one entry

--Begin NewDFSr.csv--
GroupNameSourceComputerFolderNameSourcePrimaryMember
SourceContentPathSourceStagingPathQuotaInMBDestinationComputer
DestinationContentPathDestinationReadOnly
US2AU-Engineeringusfs01pTC-39.3TRUE
K:\Engineering\TestCandidates\Folder1\CurrentVersions10240aufs01p
E:\Engineering\TestCandidates\Folder1\CurrentVersionsTRUE
--End NewDFSR.csv--

--Begin Script--
$NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
$NewGroupName = "US2AU-Engineering"
New-DfsReplicationGroup -GroupName $NewGroupName
Add-DfsrMember -GroupName $NewGroupName -ComputerName usfs01p, aufs01p
Add-DfsrConnection -GroupName $NewGroupName -SourceComputerName $SourceComputer 
-DestinationComputerName $DestinationComputer

Foreach ($Line in $NewDFSR)
   {
$SourceComputer = $Line.SourceComputer
$FolderName = $Line.FolderName
$SourceContentPath = $Line.SourceContentPath
$SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
$SourcePrimaryMember = 
[System.Convert]::ToBoolean($Line.SourcePrimaryMember)
$DestinationComputer = $Line.DestinationComputer
$DestinationContentPath = $Line.DestinationContentPath
$DestinationReadOnly = 
[System.Convert]::ToBoolean($Line.DestinationReadOnly)
New-DfsReplicatedFolder -GroupName $NewGroupName -FolderName $FolderName
Set-DfsrMembership -GroupName $NewGroupName -FolderName $FolderName 
-ComputerName $SourceComputer -ContentPath $SourceContentPath -PrimaryMember 
$SourcePrimaryMember -StagingPathQuotaInMB $SourceStagingPathQuotaInMB -Force
Set-DfsrMembership -GroupName $NewGroupName -FolderName $FolderName 
-ComputerName $DestinationComputer -ContentPath $DestinationContentPath 
-ReadOnly $DestinationReadOnly -Force
}

Set-DfsrConnectionSchedule -GroupName $NewGroupName -SourceComputerName 
$SourceComputer -DestinationComputerName $DestinationComputer -Day 1,2,3,4,5 
-BandwidthDetail 
""
Update-DfsrConfigurationFromAD -ComputerName 
$SourceComputer,$DestinationComputer
--End Script--


On Mon, Jul 24, 2017 at 3:30 PM, Michael B. Smith 
<mich...@smithcons.com<mailto:mich...@smithcons.com>> wrote:
And do you have errors in the DFS specific event logs?

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of Michael B. Smith
Sent: Monday, July 24, 2017 6:22 PM
To: ntsysadm@lists.myitforum.com<mailto:ntsysadm@lists.myitforum.com>
Subject: RE: [NTSysADM] RPC not available on remote machine while doing DFSR 
config

609 ms? Wow.

I suspect that is a hint. Let’s do a bit more:

   rpcping -s aufs01p –i 100 –v 3

and see what that tells us….

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Kurt Buff
Sent: Monday, July 24, 2017 5:33 PM
To: ntsysadm
Subject: Re: [NTSysADM] RPC not available on remote machine while doing DFSR 
config

I believe so:

From my workstation:
# rpcping -s aufs01p
Completed 1 calls in 609 ms
1 T/

Huzzah! Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Kurt Buff]

It turns out that our Riverbed WAN accelerators were the problem.

Don't know why that would be, but while working with MSFT support, I turned
off the optimization for the Riverbed at each end, and it went through with
nary a hiccup.

This worked without a flaw, creating one Replication Group, and then
creating many Replicated Folders under that RG, between two servers, and
it's supposed to be one-way replication, which I'll test tomorrow. It also
sets up the connection schedule, using the local time for the receiving
computer

However, I might not have gotten the connection schedule correct, because
when I check the schedule in the GUI, it's set up for full speed
replication 24x7, when it should be 512kbits/sec during the receiving
computer's business hours. I'm going to let that cook overnight to see if
that updates itself.

This was a fun project, modulo the frustration with getting the script past
the errors induced by the Riverbeds.

I'm not real proud of the script, as it does no error checking, no
prompting for user input, etc., but it got the job done. I've stripped out
the comments and write-host stuff for the sake of brevity, and wanted to
share it with y'all. Hope someone finds it useful.

Kurt

Tab-Delimited CSV, with header and one entry

--Begin NewDFSr.csv--
GroupNameSourceComputerFolderNameSourcePrimaryMember
SourceContentPathSourceStagingPathQuotaInMBDestinationComputer
DestinationContentPathDestinationReadOnly
US2AU-Engineeringusfs01pTC-39.3TRUE
K:\Engineering\TestCandidates\Folder1\CurrentVersions10240
aufs01pE:\Engineering\TestCandidates\Folder1\CurrentVersionsTRUE
--End NewDFSR.csv--

--Begin Script--
$NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
$NewGroupName = "US2AU-Engineering"
New-DfsReplicationGroup -GroupName $NewGroupName
Add-DfsrMember -GroupName $NewGroupName -ComputerName usfs01p, aufs01p
Add-DfsrConnection -GroupName $NewGroupName -SourceComputerName
$SourceComputer -DestinationComputerName $DestinationComputer

Foreach ($Line in $NewDFSR)
   {
$SourceComputer = $Line.SourceComputer
$FolderName = $Line.FolderName
$SourceContentPath = $Line.SourceContentPath
$SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
$SourcePrimaryMember =
[System.Convert]::ToBoolean($Line.SourcePrimaryMember)
$DestinationComputer = $Line.DestinationComputer
$DestinationContentPath = $Line.DestinationContentPath
$DestinationReadOnly =
[System.Convert]::ToBoolean($Line.DestinationReadOnly)
New-DfsReplicatedFolder -GroupName $NewGroupName -FolderName $FolderName
Set-DfsrMembership -GroupName $NewGroupName -FolderName $FolderName
-ComputerName $SourceComputer -ContentPath $SourceContentPath
-PrimaryMember $SourcePrimaryMember -StagingPathQuotaInMB
$SourceStagingPathQuotaInMB -Force
Set-DfsrMembership -GroupName $NewGroupName -FolderName $FolderName
-ComputerName $DestinationComputer -ContentPath $DestinationContentPath
-ReadOnly $DestinationReadOnly -Force
}

Set-DfsrConnectionSchedule -GroupName $NewGroupName -SourceComputerName
$SourceComputer -DestinationComputerName $DestinationComputer -Day
1,2,3,4,5 -BandwidthDetail
""
Update-DfsrConfigurationFromAD -ComputerName
$SourceComputer,$DestinationComputer
--End Script--



On Mon, Jul 24, 2017 at 3:30 PM, Michael B. Smith <mich...@smithcons.com>
wrote:

> And do you have errors in the DFS specific event logs?
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Michael B. Smith
> *Sent:* Monday, July 24, 2017 6:22 PM
> *To:* ntsysadm@lists.myitforum.com
> *Subject:* RE: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> 609 ms? Wow.
>
>
>
> I suspect that is a hint. Let’s do a bit more:
>
>
>
>rpcping -s aufs01p –i 100 –v 3
>
>
>
> and see what that tells us….
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com <listsad...@lists.myitforum.com>] *On Behalf Of *Kurt Buff
> *Sent:* Monday, July 24, 2017 5:33 PM
> *To:* ntsysadm
> *Subject:* Re: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> I believe so:
>
> From my workstation:
> # rpcping -s aufs01p
> Completed 1 calls in 609 ms
> 1 T/S or 609.000 ms/T
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 1:13 PM, Michael B. Smith <mich...@smithcons.com>
> wrote:
>
> Does rpcping agree?
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kurt Buff
> *Sent:* Monday, July 24, 2017 4:0

Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Kurt Buff]

A bit of followup...

I've opened a case with MSFT support - we had a couple left on our EA.

They tried reformulating the powershell as a simplified one-liner for
only one RG/RF, and it failed with the same error.

So, at the moment, somewhere in India, some Active Directory support
people are now noodling over a netmon capture.

They're supposed to get back to me tomorrow.

If I had to guess, it's a problem with network latency, and the
cmdlets don't handle it well, vs. the DFS GUI, or DFSRAdmin.

But I think you suspected that already, as did I.

Kurt


On Mon, Jul 24, 2017 at 3:30 PM, Michael B. Smith <mich...@smithcons.com> wrote:
> And do you have errors in the DFS specific event logs?
>
>
>
> From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com]
> On Behalf Of Michael B. Smith
> Sent: Monday, July 24, 2017 6:22 PM
> To: ntsysadm@lists.myitforum.com
> Subject: RE: [NTSysADM] RPC not available on remote machine while doing DFSR
> config
>
>
>
> 609 ms? Wow.
>
>
>
> I suspect that is a hint. Let’s do a bit more:
>
>
>
>rpcping -s aufs01p –i 100 –v 3
>
>
>
> and see what that tells us….
>
>
>
> From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com]
> On Behalf Of Kurt Buff
> Sent: Monday, July 24, 2017 5:33 PM
> To: ntsysadm
> Subject: Re: [NTSysADM] RPC not available on remote machine while doing DFSR
> config
>
>
>
> I believe so:
>
> From my workstation:
> # rpcping -s aufs01p
> Completed 1 calls in 609 ms
> 1 T/S or 609.000 ms/T
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 1:13 PM, Michael B. Smith <mich...@smithcons.com>
> wrote:
>
> Does rpcping agree?
>
>
>
> From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com]
> On Behalf Of Kurt Buff
> Sent: Monday, July 24, 2017 4:04 PM
>
>
> To: ntsysadm
> Subject: Re: [NTSysADM] RPC not available on remote machine while doing DFSR
> config
>
>
>
> Seems to be...
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 12:50 PM, Ed Ziots <eziot...@gmail.com> wrote:
>
> Is tcp 135 open via fw rules on remote host?
>
>
>
> On Jul 24, 2017 12:21 PM, "Kurt Buff" <kurt.b...@gmail.com> wrote:
>
> So, fixing the MTU mismatch seems not to have worked. I left the physical
> interface MTUs on both sides at 1500, and set up the MTUs for the tunnel
> interfaces at 1385, and verified that ping -f -l succeeds at 1357 and fails
> at 1358 from both sides.
>
> I even took a single set of entries from my CSV file and unrolled the loop,
> manually replacing the variables with values, including FQDNs for the
> machine names.
>
> Same failure:
>
> # Add-DfsrMember -GroupName US2AU-Engineering -ComputerName
> usfs01p.example.com, aufs01p.example.com
>
> Add-DfsrMember : Could not add the computer to the replication group.
> Computer: aufs01p.example.com Replication group: "US2AU-Engineering" The
> remote procedure call failed
> At line:1 char:1
> + Add-DfsrMember -GroupName US2AU-Engineering -ComputerName usfs01p.exampl
> ..
> + ~
> + CategoryInfo  : NotSpecified: (aufs01p.example.com:String)
> [Add-DfsrMember], DfsrException
> + FullyQualifiedErrorId :
> Add-DfsrMember.NonTerminatingOMException,Microsoft.DistributedFileSystemReplication.Commands.AddDfsrMemberCommand
>
> Additionally, I tried running the script on the DC in the AU office, and get
> the reciprocal failure (RPC failure, can't resolve the name of the US file
> server).
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 7:54 AM, Michael B. Smith <mich...@smithcons.com>
> wrote:
>
> Yep, those MTUs.  Because inconsistent RPC fragmentation can cause
> transactions to fail.
>
>
>
> From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com]
> On Behalf Of Kurt Buff
> Sent: Monday, July 24, 2017 10:44 AM
>
>
> To: ntsysadm
> Subject: Re: [NTSysADM] RPC not available on remote machine while doing DFSR
> config
>
>
>
> MTUs? As in TCP/IP Maximum Transmission Units?
>
> I will check that and post back, but why would a mismatch in MTU show up as
> this?
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 5:31 AM, Michael B. Smith <mich...@smithcons.com>
> wrote:
>
> I’m certain you can google as well as I can – but after looking at 8-10
> results… are you sure you have matching MTUs?
>
>
>
> From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com]
> On Behalf Of Kurt Buff
> Sent: Monday, July 24, 2017 1:10 AM
> To: ntsysadm
> Subject: Re: [NTS

Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Kurt Buff]

Many, but I believe they're related to the unsuccessful setup and
consequent teardown of the DFSR configuration that I've been fretting over.

Errors spotted include 6804, 6020, 6006, 5012 and 4004.

A couple of months ago, I deleted the old DFSR configurations between the
file servers, and just started the process of re-instantiating it late last
week. The old config was torn down not because of errors, but because the
build process for our software was pushing too much data across the pipe,
and giving access to the AU team to things that they shouldn't be seeing.

Is there anything in particular I should be looking for?

Kurt

On Mon, Jul 24, 2017 at 3:30 PM, Michael B. Smith <mich...@smithcons.com>
wrote:

> And do you have errors in the DFS specific event logs?
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Michael B. Smith
> *Sent:* Monday, July 24, 2017 6:22 PM
> *To:* ntsysadm@lists.myitforum.com
> *Subject:* RE: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> 609 ms? Wow.
>
>
>
> I suspect that is a hint. Let’s do a bit more:
>
>
>
>rpcping -s aufs01p –i 100 –v 3
>
>
>
> and see what that tells us….
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com <listsad...@lists.myitforum.com>] *On Behalf Of *Kurt Buff
> *Sent:* Monday, July 24, 2017 5:33 PM
> *To:* ntsysadm
> *Subject:* Re: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> I believe so:
>
> From my workstation:
> # rpcping -s aufs01p
> Completed 1 calls in 609 ms
> 1 T/S or 609.000 ms/T
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 1:13 PM, Michael B. Smith <mich...@smithcons.com>
> wrote:
>
> Does rpcping agree?
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kurt Buff
> *Sent:* Monday, July 24, 2017 4:04 PM
>
>
> *To:* ntsysadm
> *Subject:* Re: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> Seems to be...
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 12:50 PM, Ed Ziots <eziot...@gmail.com> wrote:
>
> Is tcp 135 open via fw rules on remote host?
>
>
>
> On Jul 24, 2017 12:21 PM, "Kurt Buff" <kurt.b...@gmail.com> wrote:
>
> So, fixing the MTU mismatch seems not to have worked. I left the physical
> interface MTUs on both sides at 1500, and set up the MTUs for the tunnel
> interfaces at 1385, and verified that ping -f -l succeeds at 1357 and fails
> at 1358 from both sides.
>
> I even took a single set of entries from my CSV file and unrolled the
> loop, manually replacing the variables with values, including FQDNs for the
> machine names.
>
> Same failure:
>
> # Add-DfsrMember -GroupName US2AU-Engineering -ComputerName
> usfs01p.example.com, aufs01p.example.com
>
> Add-DfsrMember : Could not add the computer to the replication group.
> Computer: aufs01p.example.com Replication group: "US2AU-Engineering" The
> remote procedure call failed
> At line:1 char:1
> + Add-DfsrMember -GroupName US2AU-Engineering -ComputerName usfs01p.exampl
> ..
> + ~
> + CategoryInfo  : NotSpecified: (aufs01p.example.com:String)
> [Add-DfsrMember], DfsrException
> + FullyQualifiedErrorId : Add-DfsrMember.NonTerminatingOMException,
> Microsoft.DistributedFileSystemReplication.Commands.AddDfsrMemberCommand
>
> Additionally, I tried running the script on the DC in the AU office, and
> get the reciprocal failure (RPC failure, can't resolve the name of the US
> file server).
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 7:54 AM, Michael B. Smith <mich...@smithcons.com>
> wrote:
>
> Yep, those MTUs.  Because inconsistent RPC fragmentation can cause
> transactions to fail.
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kurt Buff
> *Sent:* Monday, July 24, 2017 10:44 AM
>
>
> *To:* ntsysadm
> *Subject:* Re: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> MTUs? As in TCP/IP Maximum Transmission Units?
>
> I will check that and post back, but why would a mismatch in MTU show up
> as this?
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 5:31 AM, Michael B. Smith <mich...@smithcons.com>
> wrote:
>
> I’m certain you can google as well as I can – but after looking at 8-10
> results… are you sure you have matching MTUs?
>
>
>
> *From:* listsad...@lists.m

Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Kurt Buff]

Yep - going from Redmond to Brisbane is very slow at times, but usually
only about ~200ms

This looks better...

 rpcping -s aufs01p -i 100 -v 3
 RPCPing v6.0. Copyright (C) Microsoft Corporation, 2002-2006
 RPCPing set Activity ID:  {77f395c1-3be7-49e2-934a-23d7c060f208}
 Completed 74 calls in 15094 ms
 4 T/S or 203.972 ms/T

 Completed 26 calls in 5188 ms
 5 T/S or 199.538 ms/T

Kurt

On Mon, Jul 24, 2017 at 3:21 PM, Michael B. Smith <mich...@smithcons.com>
wrote:

> 609 ms? Wow.
>
>
>
> I suspect that is a hint. Let’s do a bit more:
>
>
>
>rpcping -s aufs01p –i 100 –v 3
>
>
>
> and see what that tells us….
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kurt Buff
> *Sent:* Monday, July 24, 2017 5:33 PM
> *To:* ntsysadm
> *Subject:* Re: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> I believe so:
>
> From my workstation:
> # rpcping -s aufs01p
> Completed 1 calls in 609 ms
> 1 T/S or 609.000 ms/T
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 1:13 PM, Michael B. Smith <mich...@smithcons.com>
> wrote:
>
> Does rpcping agree?
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kurt Buff
> *Sent:* Monday, July 24, 2017 4:04 PM
>
>
> *To:* ntsysadm
> *Subject:* Re: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> Seems to be...
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 12:50 PM, Ed Ziots <eziot...@gmail.com> wrote:
>
> Is tcp 135 open via fw rules on remote host?
>
>
>
> On Jul 24, 2017 12:21 PM, "Kurt Buff" <kurt.b...@gmail.com> wrote:
>
> So, fixing the MTU mismatch seems not to have worked. I left the physical
> interface MTUs on both sides at 1500, and set up the MTUs for the tunnel
> interfaces at 1385, and verified that ping -f -l succeeds at 1357 and fails
> at 1358 from both sides.
>
> I even took a single set of entries from my CSV file and unrolled the
> loop, manually replacing the variables with values, including FQDNs for the
> machine names.
>
> Same failure:
>
> # Add-DfsrMember -GroupName US2AU-Engineering -ComputerName
> usfs01p.example.com, aufs01p.example.com
>
> Add-DfsrMember : Could not add the computer to the replication group.
> Computer: aufs01p.example.com Replication group: "US2AU-Engineering" The
> remote procedure call failed
> At line:1 char:1
> + Add-DfsrMember -GroupName US2AU-Engineering -ComputerName usfs01p.exampl
> ..
> + ~
> + CategoryInfo  : NotSpecified: (aufs01p.example.com:String)
> [Add-DfsrMember], DfsrException
> + FullyQualifiedErrorId : Add-DfsrMember.NonTerminatingOMException,
> Microsoft.DistributedFileSystemReplication.Commands.AddDfsrMemberCommand
>
> Additionally, I tried running the script on the DC in the AU office, and
> get the reciprocal failure (RPC failure, can't resolve the name of the US
> file server).
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 7:54 AM, Michael B. Smith <mich...@smithcons.com>
> wrote:
>
> Yep, those MTUs.  Because inconsistent RPC fragmentation can cause
> transactions to fail.
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kurt Buff
> *Sent:* Monday, July 24, 2017 10:44 AM
>
>
> *To:* ntsysadm
> *Subject:* Re: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> MTUs? As in TCP/IP Maximum Transmission Units?
>
> I will check that and post back, but why would a mismatch in MTU show up
> as this?
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 5:31 AM, Michael B. Smith <mich...@smithcons.com>
> wrote:
>
> I’m certain you can google as well as I can – but after looking at 8-10
> results… are you sure you have matching MTUs?
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kurt Buff
> *Sent:* Monday, July 24, 2017 1:10 AM
> *To:* ntsysadm
> *Subject:* Re: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> Ignore my earlier message from this evening. I've overcome some blindness
> on my part, and have a bit more information, though I fear it's not enough.
> I used this page for what looks to be a better way to handle the errors:
> https://stackoverflow.com/questions/38419325/catching-
> full-exception-message
>
> The red highlighted error is new - but I don't know why th

RE: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Michael B. Smith]

And do you have errors in the DFS specific event logs?

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Michael B. Smith
Sent: Monday, July 24, 2017 6:22 PM
To: ntsysadm@lists.myitforum.com
Subject: RE: [NTSysADM] RPC not available on remote machine while doing DFSR 
config

609 ms? Wow.

I suspect that is a hint. Let’s do a bit more:

   rpcping -s aufs01p –i 100 –v 3

and see what that tells us….

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Kurt Buff
Sent: Monday, July 24, 2017 5:33 PM
To: ntsysadm
Subject: Re: [NTSysADM] RPC not available on remote machine while doing DFSR 
config

I believe so:

From my workstation:
# rpcping -s aufs01p
Completed 1 calls in 609 ms
1 T/S or 609.000 ms/T
Kurt

On Mon, Jul 24, 2017 at 1:13 PM, Michael B. Smith 
<mich...@smithcons.com<mailto:mich...@smithcons.com>> wrote:
Does rpcping agree?

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of Kurt Buff
Sent: Monday, July 24, 2017 4:04 PM

To: ntsysadm
Subject: Re: [NTSysADM] RPC not available on remote machine while doing DFSR 
config

Seems to be...
Kurt

On Mon, Jul 24, 2017 at 12:50 PM, Ed Ziots 
<eziot...@gmail.com<mailto:eziot...@gmail.com>> wrote:
Is tcp 135 open via fw rules on remote host?

On Jul 24, 2017 12:21 PM, "Kurt Buff" 
<kurt.b...@gmail.com<mailto:kurt.b...@gmail.com>> wrote:
So, fixing the MTU mismatch seems not to have worked. I left the physical 
interface MTUs on both sides at 1500, and set up the MTUs for the tunnel 
interfaces at 1385, and verified that ping -f -l succeeds at 1357 and fails at 
1358 from both sides.
I even took a single set of entries from my CSV file and unrolled the loop, 
manually replacing the variables with values, including FQDNs for the machine 
names.
Same failure:

# Add-DfsrMember -GroupName US2AU-Engineering -ComputerName 
usfs01p.example.com<http://usfs01p.example.com>, 
aufs01p.example.com<http://aufs01p.example.com>

Add-DfsrMember : Could not add the computer to the replication group. Computer: 
aufs01p.example.com<http://aufs01p.example.com> Replication group: 
"US2AU-Engineering" The remote procedure call failed
At line:1 char:1
+ Add-DfsrMember -GroupName US2AU-Engineering -ComputerName usfs01p.exampl ..
+ ~
+ CategoryInfo  : NotSpecified: (aufs01p.example.com:String) 
[Add-DfsrMember], DfsrException
+ FullyQualifiedErrorId : 
Add-DfsrMember.NonTerminatingOMException,Microsoft.DistributedFileSystemReplication.Commands.AddDfsrMemberCommand
Additionally, I tried running the script on the DC in the AU office, and get 
the reciprocal failure (RPC failure, can't resolve the name of the US file 
server).
Kurt

On Mon, Jul 24, 2017 at 7:54 AM, Michael B. Smith 
<mich...@smithcons.com<mailto:mich...@smithcons.com>> wrote:
Yep, those MTUs.  Because inconsistent RPC fragmentation can cause transactions 
to fail.

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of Kurt Buff
Sent: Monday, July 24, 2017 10:44 AM

To: ntsysadm
Subject: Re: [NTSysADM] RPC not available on remote machine while doing DFSR 
config

MTUs? As in TCP/IP Maximum Transmission Units?
I will check that and post back, but why would a mismatch in MTU show up as 
this?
Kurt

On Mon, Jul 24, 2017 at 5:31 AM, Michael B. Smith 
<mich...@smithcons.com<mailto:mich...@smithcons.com>> wrote:
I’m certain you can google as well as I can – but after looking at 8-10 
results… are you sure you have matching MTUs?

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of Kurt Buff
Sent: Monday, July 24, 2017 1:10 AM
To: ntsysadm
Subject: Re: [NTSysADM] RPC not available on remote machine while doing DFSR 
config

Ignore my earlier message from this evening. I've overcome some blindness on my 
part, and have a bit more information, though I fear it's not enough. I used 
this page for what looks to be a better way to handle the errors:
https://stackoverflow.com/questions/38419325/catching-full-exception-message
The red highlighted error is new - but I don't know why that's there. It's very 
strange, as both are 2012R2 servers, in the same domain, and I'm running this 
on my Win10 workstation with my DA credentials.

--Begin revised script--
$NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
New-DfsReplicationGroup -GroupName US2AU-Engineering
$GroupName = Get-DfsReplicati

RE: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Michael B. Smith]

609 ms? Wow.

I suspect that is a hint. Let’s do a bit more:

   rpcping -s aufs01p –i 100 –v 3

and see what that tells us….

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Kurt Buff
Sent: Monday, July 24, 2017 5:33 PM
To: ntsysadm
Subject: Re: [NTSysADM] RPC not available on remote machine while doing DFSR 
config

I believe so:

From my workstation:
# rpcping -s aufs01p
Completed 1 calls in 609 ms
1 T/S or 609.000 ms/T
Kurt

On Mon, Jul 24, 2017 at 1:13 PM, Michael B. Smith 
<mich...@smithcons.com<mailto:mich...@smithcons.com>> wrote:
Does rpcping agree?

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of Kurt Buff
Sent: Monday, July 24, 2017 4:04 PM

To: ntsysadm
Subject: Re: [NTSysADM] RPC not available on remote machine while doing DFSR 
config

Seems to be...

Kurt

On Mon, Jul 24, 2017 at 12:50 PM, Ed Ziots 
<eziot...@gmail.com<mailto:eziot...@gmail.com>> wrote:
Is tcp 135 open via fw rules on remote host?

On Jul 24, 2017 12:21 PM, "Kurt Buff" 
<kurt.b...@gmail.com<mailto:kurt.b...@gmail.com>> wrote:
So, fixing the MTU mismatch seems not to have worked. I left the physical 
interface MTUs on both sides at 1500, and set up the MTUs for the tunnel 
interfaces at 1385, and verified that ping -f -l succeeds at 1357 and fails at 
1358 from both sides.
I even took a single set of entries from my CSV file and unrolled the loop, 
manually replacing the variables with values, including FQDNs for the machine 
names.
Same failure:

# Add-DfsrMember -GroupName US2AU-Engineering -ComputerName 
usfs01p.example.com<http://usfs01p.example.com>, 
aufs01p.example.com<http://aufs01p.example.com>

Add-DfsrMember : Could not add the computer to the replication group. Computer: 
aufs01p.example.com<http://aufs01p.example.com> Replication group: 
"US2AU-Engineering" The remote procedure call failed
At line:1 char:1
+ Add-DfsrMember -GroupName US2AU-Engineering -ComputerName usfs01p.exampl ..
+ ~
+ CategoryInfo  : NotSpecified: (aufs01p.example.com:String) 
[Add-DfsrMember], DfsrException
+ FullyQualifiedErrorId : 
Add-DfsrMember.NonTerminatingOMException,Microsoft.DistributedFileSystemReplication.Commands.AddDfsrMemberCommand
Additionally, I tried running the script on the DC in the AU office, and get 
the reciprocal failure (RPC failure, can't resolve the name of the US file 
server).
Kurt

On Mon, Jul 24, 2017 at 7:54 AM, Michael B. Smith 
<mich...@smithcons.com<mailto:mich...@smithcons.com>> wrote:
Yep, those MTUs.  Because inconsistent RPC fragmentation can cause transactions 
to fail.

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of Kurt Buff
Sent: Monday, July 24, 2017 10:44 AM

To: ntsysadm
Subject: Re: [NTSysADM] RPC not available on remote machine while doing DFSR 
config

MTUs? As in TCP/IP Maximum Transmission Units?
I will check that and post back, but why would a mismatch in MTU show up as 
this?
Kurt

On Mon, Jul 24, 2017 at 5:31 AM, Michael B. Smith 
<mich...@smithcons.com<mailto:mich...@smithcons.com>> wrote:
I’m certain you can google as well as I can – but after looking at 8-10 
results… are you sure you have matching MTUs?

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of Kurt Buff
Sent: Monday, July 24, 2017 1:10 AM
To: ntsysadm
Subject: Re: [NTSysADM] RPC not available on remote machine while doing DFSR 
config

Ignore my earlier message from this evening. I've overcome some blindness on my 
part, and have a bit more information, though I fear it's not enough. I used 
this page for what looks to be a better way to handle the errors:
https://stackoverflow.com/questions/38419325/catching-full-exception-message
The red highlighted error is new - but I don't know why that's there. It's very 
strange, as both are 2012R2 servers, in the same domain, and I'm running this 
on my Win10 workstation with my DA credentials.

--Begin revised script--
$NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
New-DfsReplicationGroup -GroupName US2AU-Engineering
$GroupName = Get-DfsReplicationGroup US2AU-Engineering
Foreach ($Line in $NewDFSR)
   {
$GroupName = $Line.GroupName
$SourceComputer = $Line.SourceComputer
$FolderName = $Line.FolderName
$SourceContentPath = $Line.SourceContentPath
$SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
$SourcePrimaryMember = 
[System.Convert]::ToBoolean($Line.SourcePrimary

Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Kurt Buff]

I believe so:

>From my workstation:
# rpcping -s aufs01p
Completed 1 calls in 609 ms
1 T/S or 609.000 ms/T

Kurt

On Mon, Jul 24, 2017 at 1:13 PM, Michael B. Smith <mich...@smithcons.com>
wrote:

> Does rpcping agree?
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kurt Buff
> *Sent:* Monday, July 24, 2017 4:04 PM
>
> *To:* ntsysadm
> *Subject:* Re: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> Seems to be...
>
> [image: Inline image 1]
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 12:50 PM, Ed Ziots <eziot...@gmail.com> wrote:
>
> Is tcp 135 open via fw rules on remote host?
>
>
>
> On Jul 24, 2017 12:21 PM, "Kurt Buff" <kurt.b...@gmail.com> wrote:
>
> So, fixing the MTU mismatch seems not to have worked. I left the physical
> interface MTUs on both sides at 1500, and set up the MTUs for the tunnel
> interfaces at 1385, and verified that ping -f -l succeeds at 1357 and fails
> at 1358 from both sides.
>
> I even took a single set of entries from my CSV file and unrolled the
> loop, manually replacing the variables with values, including FQDNs for the
> machine names.
>
> Same failure:
>
> # Add-DfsrMember -GroupName US2AU-Engineering -ComputerName
> usfs01p.example.com, aufs01p.example.com
>
> Add-DfsrMember : Could not add the computer to the replication group.
> Computer: aufs01p.example.com Replication group: "US2AU-Engineering" The
> remote procedure call failed
> At line:1 char:1
> + Add-DfsrMember -GroupName US2AU-Engineering -ComputerName usfs01p.exampl
> ...
> + ~
> + CategoryInfo  : NotSpecified: (aufs01p.example.com:String)
> [Add-DfsrMember], DfsrException
> + FullyQualifiedErrorId : Add-DfsrMember.NonTerminatingOMException,
> Microsoft.DistributedFileSystemReplication.Commands.AddDfsrMemberCommand
>
> Additionally, I tried running the script on the DC in the AU office, and
> get the reciprocal failure (RPC failure, can't resolve the name of the US
> file server).
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 7:54 AM, Michael B. Smith <mich...@smithcons.com>
> wrote:
>
> Yep, those MTUs.  Because inconsistent RPC fragmentation can cause
> transactions to fail.
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kurt Buff
> *Sent:* Monday, July 24, 2017 10:44 AM
>
>
> *To:* ntsysadm
> *Subject:* Re: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> MTUs? As in TCP/IP Maximum Transmission Units?
>
> I will check that and post back, but why would a mismatch in MTU show up
> as this?
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 5:31 AM, Michael B. Smith <mich...@smithcons.com>
> wrote:
>
> I’m certain you can google as well as I can – but after looking at 8-10
> results… are you sure you have matching MTUs?
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kurt Buff
> *Sent:* Monday, July 24, 2017 1:10 AM
> *To:* ntsysadm
> *Subject:* Re: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> Ignore my earlier message from this evening. I've overcome some blindness
> on my part, and have a bit more information, though I fear it's not enough.
> I used this page for what looks to be a better way to handle the errors:
> https://stackoverflow.com/questions/38419325/catching-
> full-exception-message
>
> The red highlighted error is new - but I don't know why that's there. It's
> very strange, as both are 2012R2 servers, in the same domain, and I'm
> running this on my Win10 workstation with my DA credentials.
>
>
>
> --Begin revised script--
> $NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
> New-DfsReplicationGroup -GroupName US2AU-Engineering
> $GroupName = Get-DfsReplicationGroup US2AU-Engineering
> Foreach ($Line in $NewDFSR)
>{
> $GroupName = $Line.GroupName
> $SourceComputer = $Line.SourceComputer
> $FolderName = $Line.FolderName
> $SourceContentPath = $Line.SourceContentPath
> $SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
> $SourcePrimaryMember = [System.Convert]::ToBoolean($
> Line.SourcePrimaryMember)
> $DestinationComputer = $Line.DestinationComputer
> $DestinationContentPath = $Line.DestinationContentPath
> $DestinationReadOnly = [System.Convert]::ToBoolean($
> Line.DestinationReadOnly)
> N

RE: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Ed Ziots]

We thinking same thing that network firewall rule set is blocking tcp and
up 135

On Jul 24, 2017 1:20 PM, "Michael B. Smith" <mich...@smithcons.com> wrote:

> Does rpcping agree?
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kurt Buff
> *Sent:* Monday, July 24, 2017 4:04 PM
> *To:* ntsysadm
> *Subject:* Re: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> Seems to be...
>
> [image: Inline image 1]
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 12:50 PM, Ed Ziots <eziot...@gmail.com> wrote:
>
> Is tcp 135 open via fw rules on remote host?
>
>
>
> On Jul 24, 2017 12:21 PM, "Kurt Buff" <kurt.b...@gmail.com> wrote:
>
> So, fixing the MTU mismatch seems not to have worked. I left the physical
> interface MTUs on both sides at 1500, and set up the MTUs for the tunnel
> interfaces at 1385, and verified that ping -f -l succeeds at 1357 and fails
> at 1358 from both sides.
>
> I even took a single set of entries from my CSV file and unrolled the
> loop, manually replacing the variables with values, including FQDNs for the
> machine names.
>
> Same failure:
>
> # Add-DfsrMember -GroupName US2AU-Engineering -ComputerName
> usfs01p.example.com, aufs01p.example.com
>
> Add-DfsrMember : Could not add the computer to the replication group.
> Computer: aufs01p.example.com Replication group: "US2AU-Engineering" The
> remote procedure call failed
> At line:1 char:1
> + Add-DfsrMember -GroupName US2AU-Engineering -ComputerName usfs01p.exampl
> ...
> + ~
> + CategoryInfo  : NotSpecified: (aufs01p.example.com:String)
> [Add-DfsrMember], DfsrException
> + FullyQualifiedErrorId : Add-DfsrMember.NonTerminatingOMException,
> Microsoft.DistributedFileSystemReplication.Commands.AddDfsrMemberCommand
>
> Additionally, I tried running the script on the DC in the AU office, and
> get the reciprocal failure (RPC failure, can't resolve the name of the US
> file server).
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 7:54 AM, Michael B. Smith <mich...@smithcons.com>
> wrote:
>
> Yep, those MTUs.  Because inconsistent RPC fragmentation can cause
> transactions to fail.
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kurt Buff
> *Sent:* Monday, July 24, 2017 10:44 AM
>
>
> *To:* ntsysadm
> *Subject:* Re: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> MTUs? As in TCP/IP Maximum Transmission Units?
>
> I will check that and post back, but why would a mismatch in MTU show up
> as this?
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 5:31 AM, Michael B. Smith <mich...@smithcons.com>
> wrote:
>
> I’m certain you can google as well as I can – but after looking at 8-10
> results… are you sure you have matching MTUs?
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kurt Buff
> *Sent:* Monday, July 24, 2017 1:10 AM
> *To:* ntsysadm
> *Subject:* Re: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> Ignore my earlier message from this evening. I've overcome some blindness
> on my part, and have a bit more information, though I fear it's not enough.
> I used this page for what looks to be a better way to handle the errors:
> https://stackoverflow.com/questions/38419325/catching-
> full-exception-message
>
> The red highlighted error is new - but I don't know why that's there. It's
> very strange, as both are 2012R2 servers, in the same domain, and I'm
> running this on my Win10 workstation with my DA credentials.
>
>
>
> --Begin revised script--
> $NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
> New-DfsReplicationGroup -GroupName US2AU-Engineering
> $GroupName = Get-DfsReplicationGroup US2AU-Engineering
> Foreach ($Line in $NewDFSR)
>{
> $GroupName = $Line.GroupName
> $SourceComputer = $Line.SourceComputer
> $FolderName = $Line.FolderName
> $SourceContentPath = $Line.SourceContentPath
> $SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
> $SourcePrimaryMember = [System.Convert]::ToBoolean($
> Line.SourcePrimaryMember)
> $DestinationComputer = $Line.DestinationComputer
> $DestinationContentPath = $Line.DestinationContentPath
> $DestinationReadOnly = [System.Convert]::ToBoolean($
> Line.DestinationReadOnly)
> New-DfsReplicatedFolder -GroupName $Grou

RE: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Michael B. Smith]

Does rpcping agree?

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Kurt Buff
Sent: Monday, July 24, 2017 4:04 PM
To: ntsysadm
Subject: Re: [NTSysADM] RPC not available on remote machine while doing DFSR 
config

Seems to be...

[Inline image 1]
Kurt

On Mon, Jul 24, 2017 at 12:50 PM, Ed Ziots 
<eziot...@gmail.com<mailto:eziot...@gmail.com>> wrote:
Is tcp 135 open via fw rules on remote host?

On Jul 24, 2017 12:21 PM, "Kurt Buff" 
<kurt.b...@gmail.com<mailto:kurt.b...@gmail.com>> wrote:
So, fixing the MTU mismatch seems not to have worked. I left the physical 
interface MTUs on both sides at 1500, and set up the MTUs for the tunnel 
interfaces at 1385, and verified that ping -f -l succeeds at 1357 and fails at 
1358 from both sides.
I even took a single set of entries from my CSV file and unrolled the loop, 
manually replacing the variables with values, including FQDNs for the machine 
names.
Same failure:

# Add-DfsrMember -GroupName US2AU-Engineering -ComputerName 
usfs01p.example.com<http://usfs01p.example.com>, 
aufs01p.example.com<http://aufs01p.example.com>

Add-DfsrMember : Could not add the computer to the replication group. Computer: 
aufs01p.example.com<http://aufs01p.example.com> Replication group: 
"US2AU-Engineering" The remote procedure call failed
At line:1 char:1
+ Add-DfsrMember -GroupName US2AU-Engineering -ComputerName usfs01p.exampl ...
+ ~
+ CategoryInfo  : NotSpecified: (aufs01p.example.com:String) 
[Add-DfsrMember], DfsrException
+ FullyQualifiedErrorId : 
Add-DfsrMember.NonTerminatingOMException,Microsoft.DistributedFileSystemReplication.Commands.AddDfsrMemberCommand
Additionally, I tried running the script on the DC in the AU office, and get 
the reciprocal failure (RPC failure, can't resolve the name of the US file 
server).
Kurt

On Mon, Jul 24, 2017 at 7:54 AM, Michael B. Smith 
<mich...@smithcons.com<mailto:mich...@smithcons.com>> wrote:
Yep, those MTUs.  Because inconsistent RPC fragmentation can cause transactions 
to fail.

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of Kurt Buff
Sent: Monday, July 24, 2017 10:44 AM

To: ntsysadm
Subject: Re: [NTSysADM] RPC not available on remote machine while doing DFSR 
config

MTUs? As in TCP/IP Maximum Transmission Units?
I will check that and post back, but why would a mismatch in MTU show up as 
this?
Kurt

On Mon, Jul 24, 2017 at 5:31 AM, Michael B. Smith 
<mich...@smithcons.com<mailto:mich...@smithcons.com>> wrote:
I’m certain you can google as well as I can – but after looking at 8-10 
results… are you sure you have matching MTUs?

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of Kurt Buff
Sent: Monday, July 24, 2017 1:10 AM
To: ntsysadm
Subject: Re: [NTSysADM] RPC not available on remote machine while doing DFSR 
config

Ignore my earlier message from this evening. I've overcome some blindness on my 
part, and have a bit more information, though I fear it's not enough. I used 
this page for what looks to be a better way to handle the errors:
https://stackoverflow.com/questions/38419325/catching-full-exception-message
The red highlighted error is new - but I don't know why that's there. It's very 
strange, as both are 2012R2 servers, in the same domain, and I'm running this 
on my Win10 workstation with my DA credentials.

--Begin revised script--
$NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
New-DfsReplicationGroup -GroupName US2AU-Engineering
$GroupName = Get-DfsReplicationGroup US2AU-Engineering
Foreach ($Line in $NewDFSR)
   {
$GroupName = $Line.GroupName
$SourceComputer = $Line.SourceComputer
$FolderName = $Line.FolderName
$SourceContentPath = $Line.SourceContentPath
$SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
$SourcePrimaryMember = 
[System.Convert]::ToBoolean($Line.SourcePrimaryMember)
$DestinationComputer = $Line.DestinationComputer
$DestinationContentPath = $Line.DestinationContentPath
$DestinationReadOnly = 
[System.Convert]::ToBoolean($Line.DestinationReadOnly)
New-DfsReplicatedFolder -GroupName $GroupName -FolderName $FolderName
Try
   {
   Add-DfsrMember -GroupName $GroupName -ComputerName $SourceComputer, 
$DestinationComputer
   }
Catch
   {
   $e = $_.Exception
   $msg = $e.Message
   while ($e.InnerException) {
  $e = $e.InnerException
  $msg += "`n" + $e.Message
   }
   $msg}
Add-DfsrConnection -GroupName $GroupName -SourceComputerName 
$SourceComputer -D

Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Kurt Buff]

I have not tried a PSSession. I don't think it's relevant in this
situation, though I could be wrong, and if I am wrong, I'm not sure how I'd
go about doing it in this case.

Script has been run on my workstation in the US and on DCs in both offices
(US and AU).

Interesting note, in case it was missed: Running the script on the AU DC
also fails RPC call, but against the US file server - so it's the
inverse/parallel of the failure when the script is run in the US office.

Kurt

On Mon, Jul 24, 2017 at 12:50 PM, elsalvoz <elsal...@gmail.com> wrote:

> Can you open PSSISSION on either server? You run the commands manually for
> testing purposes
>
> Cesar A.
>
> On Jul 24, 2017 12:22 PM, "Kurt Buff" <kurt.b...@gmail.com> wrote:
>
>> So, fixing the MTU mismatch seems not to have worked. I left the physical
>> interface MTUs on both sides at 1500, and set up the MTUs for the tunnel
>> interfaces at 1385, and verified that ping -f -l succeeds at 1357 and fails
>> at 1358 from both sides.
>>
>> I even took a single set of entries from my CSV file and unrolled the
>> loop, manually replacing the variables with values, including FQDNs for the
>> machine names.
>>
>> Same failure:
>>
>> # Add-DfsrMember -GroupName US2AU-Engineering -ComputerName
>> usfs01p.example.com, aufs01p.example.com
>>
>> Add-DfsrMember : Could not add the computer to the replication group.
>> Computer: aufs01p.example.com Replication group: "US2AU-Engineering" The
>> remote procedure call failed
>> At line:1 char:1
>> + Add-DfsrMember -GroupName US2AU-Engineering -ComputerName
>> usfs01p.exampl ...
>> + ~
>> + CategoryInfo  : NotSpecified: (aufs01p.example.com:String)
>> [Add-DfsrMember], DfsrException
>> + FullyQualifiedErrorId : Add-DfsrMember.NonTerminatingO
>> MException,Microsoft.DistributedFileSystemReplication.
>> Commands.AddDfsrMemberCommand
>>
>> Additionally, I tried running the script on the DC in the AU office, and
>> get the reciprocal failure (RPC failure, can't resolve the name of the US
>> file server).
>>
>> Kurt
>>
>> On Mon, Jul 24, 2017 at 7:54 AM, Michael B. Smith <mich...@smithcons.com>
>> wrote:
>>
>>> Yep, those MTUs.  Because inconsistent RPC fragmentation can cause
>>> transactions to fail.
>>>
>>>
>>>
>>> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.myitf
>>> orum.com] *On Behalf Of *Kurt Buff
>>> *Sent:* Monday, July 24, 2017 10:44 AM
>>>
>>> *To:* ntsysadm
>>> *Subject:* Re: [NTSysADM] RPC not available on remote machine while
>>> doing DFSR config
>>>
>>>
>>>
>>> MTUs? As in TCP/IP Maximum Transmission Units?
>>>
>>> I will check that and post back, but why would a mismatch in MTU show up
>>> as this?
>>>
>>> Kurt
>>>
>>>
>>>
>>> On Mon, Jul 24, 2017 at 5:31 AM, Michael B. Smith <mich...@smithcons.com>
>>> wrote:
>>>
>>> I’m certain you can google as well as I can – but after looking at 8-10
>>> results… are you sure you have matching MTUs?
>>>
>>>
>>>
>>> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.myitf
>>> orum.com] *On Behalf Of *Kurt Buff
>>> *Sent:* Monday, July 24, 2017 1:10 AM
>>> *To:* ntsysadm
>>> *Subject:* Re: [NTSysADM] RPC not available on remote machine while
>>> doing DFSR config
>>>
>>>
>>>
>>> Ignore my earlier message from this evening. I've overcome some
>>> blindness on my part, and have a bit more information, though I fear it's
>>> not enough. I used this page for what looks to be a better way to handle
>>> the errors:
>>> https://stackoverflow.com/questions/38419325/catching-full-e
>>> xception-message
>>>
>>> The red highlighted error is new - but I don't know why that's there.
>>> It's very strange, as both are 2012R2 servers, in the same domain, and I'm
>>> running this on my Win10 workstation with my DA credentials.
>>>
>>>
>>>
>>> --Begin revised script--
>>> $NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
>>> New-DfsReplicationGroup -GroupName US2AU-Engineering
>>> $GroupName = Get-DfsReplicationGroup US2AU-Engineering
>>> Foreach ($Line in $NewDFSR)
>>>{
>>> $GroupName = $Line.GroupName

Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Kurt Buff]

Seems to be...

[image: Inline image 1]

Kurt

On Mon, Jul 24, 2017 at 12:50 PM, Ed Ziots <eziot...@gmail.com> wrote:

> Is tcp 135 open via fw rules on remote host?
>
> On Jul 24, 2017 12:21 PM, "Kurt Buff" <kurt.b...@gmail.com> wrote:
>
>> So, fixing the MTU mismatch seems not to have worked. I left the physical
>> interface MTUs on both sides at 1500, and set up the MTUs for the tunnel
>> interfaces at 1385, and verified that ping -f -l succeeds at 1357 and fails
>> at 1358 from both sides.
>>
>> I even took a single set of entries from my CSV file and unrolled the
>> loop, manually replacing the variables with values, including FQDNs for the
>> machine names.
>>
>> Same failure:
>>
>> # Add-DfsrMember -GroupName US2AU-Engineering -ComputerName
>> usfs01p.example.com, aufs01p.example.com
>>
>> Add-DfsrMember : Could not add the computer to the replication group.
>> Computer: aufs01p.example.com Replication group: "US2AU-Engineering" The
>> remote procedure call failed
>> At line:1 char:1
>> + Add-DfsrMember -GroupName US2AU-Engineering -ComputerName
>> usfs01p.exampl ...
>> + ~
>> + CategoryInfo  : NotSpecified: (aufs01p.example.com:String)
>> [Add-DfsrMember], DfsrException
>> + FullyQualifiedErrorId : Add-DfsrMember.NonTerminatingO
>> MException,Microsoft.DistributedFileSystemReplication.
>> Commands.AddDfsrMemberCommand
>>
>> Additionally, I tried running the script on the DC in the AU office, and
>> get the reciprocal failure (RPC failure, can't resolve the name of the US
>> file server).
>>
>> Kurt
>>
>> On Mon, Jul 24, 2017 at 7:54 AM, Michael B. Smith <mich...@smithcons.com>
>> wrote:
>>
>>> Yep, those MTUs.  Because inconsistent RPC fragmentation can cause
>>> transactions to fail.
>>>
>>>
>>>
>>> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.myitf
>>> orum.com] *On Behalf Of *Kurt Buff
>>> *Sent:* Monday, July 24, 2017 10:44 AM
>>>
>>> *To:* ntsysadm
>>> *Subject:* Re: [NTSysADM] RPC not available on remote machine while
>>> doing DFSR config
>>>
>>>
>>>
>>> MTUs? As in TCP/IP Maximum Transmission Units?
>>>
>>> I will check that and post back, but why would a mismatch in MTU show up
>>> as this?
>>>
>>> Kurt
>>>
>>>
>>>
>>> On Mon, Jul 24, 2017 at 5:31 AM, Michael B. Smith <mich...@smithcons.com>
>>> wrote:
>>>
>>> I’m certain you can google as well as I can – but after looking at 8-10
>>> results… are you sure you have matching MTUs?
>>>
>>>
>>>
>>> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.myitf
>>> orum.com] *On Behalf Of *Kurt Buff
>>> *Sent:* Monday, July 24, 2017 1:10 AM
>>> *To:* ntsysadm
>>> *Subject:* Re: [NTSysADM] RPC not available on remote machine while
>>> doing DFSR config
>>>
>>>
>>>
>>> Ignore my earlier message from this evening. I've overcome some
>>> blindness on my part, and have a bit more information, though I fear it's
>>> not enough. I used this page for what looks to be a better way to handle
>>> the errors:
>>> https://stackoverflow.com/questions/38419325/catching-full-e
>>> xception-message
>>>
>>> The red highlighted error is new - but I don't know why that's there.
>>> It's very strange, as both are 2012R2 servers, in the same domain, and I'm
>>> running this on my Win10 workstation with my DA credentials.
>>>
>>>
>>>
>>> --Begin revised script--
>>> $NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
>>> New-DfsReplicationGroup -GroupName US2AU-Engineering
>>> $GroupName = Get-DfsReplicationGroup US2AU-Engineering
>>> Foreach ($Line in $NewDFSR)
>>>{
>>> $GroupName = $Line.GroupName
>>> $SourceComputer = $Line.SourceComputer
>>> $FolderName = $Line.FolderName
>>> $SourceContentPath = $Line.SourceContentPath
>>> $SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
>>> $SourcePrimaryMember = [System.Convert]::ToBoolean($L
>>> ine.SourcePrimaryMember)
>>> $DestinationComputer = $Line.DestinationComputer
>>> $DestinationContentPath = $Line.DestinationContentPath

Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Ed Ziots]

Is tcp 135 open via fw rules on remote host?

On Jul 24, 2017 12:21 PM, "Kurt Buff" <kurt.b...@gmail.com> wrote:

> So, fixing the MTU mismatch seems not to have worked. I left the physical
> interface MTUs on both sides at 1500, and set up the MTUs for the tunnel
> interfaces at 1385, and verified that ping -f -l succeeds at 1357 and fails
> at 1358 from both sides.
>
> I even took a single set of entries from my CSV file and unrolled the
> loop, manually replacing the variables with values, including FQDNs for the
> machine names.
>
> Same failure:
>
> # Add-DfsrMember -GroupName US2AU-Engineering -ComputerName
> usfs01p.example.com, aufs01p.example.com
>
> Add-DfsrMember : Could not add the computer to the replication group.
> Computer: aufs01p.example.com Replication group: "US2AU-Engineering" The
> remote procedure call failed
> At line:1 char:1
> + Add-DfsrMember -GroupName US2AU-Engineering -ComputerName usfs01p.exampl
> ...
> + ~
> + CategoryInfo  : NotSpecified: (aufs01p.example.com:String)
> [Add-DfsrMember], DfsrException
> + FullyQualifiedErrorId : Add-DfsrMember.NonTerminatingOMException,
> Microsoft.DistributedFileSystemReplication.Commands.AddDfsrMemberCommand
>
> Additionally, I tried running the script on the DC in the AU office, and
> get the reciprocal failure (RPC failure, can't resolve the name of the US
> file server).
>
> Kurt
>
> On Mon, Jul 24, 2017 at 7:54 AM, Michael B. Smith <mich...@smithcons.com>
> wrote:
>
>> Yep, those MTUs.  Because inconsistent RPC fragmentation can cause
>> transactions to fail.
>>
>>
>>
>> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.myitf
>> orum.com] *On Behalf Of *Kurt Buff
>> *Sent:* Monday, July 24, 2017 10:44 AM
>>
>> *To:* ntsysadm
>> *Subject:* Re: [NTSysADM] RPC not available on remote machine while
>> doing DFSR config
>>
>>
>>
>> MTUs? As in TCP/IP Maximum Transmission Units?
>>
>> I will check that and post back, but why would a mismatch in MTU show up
>> as this?
>>
>> Kurt
>>
>>
>>
>> On Mon, Jul 24, 2017 at 5:31 AM, Michael B. Smith <mich...@smithcons.com>
>> wrote:
>>
>> I’m certain you can google as well as I can – but after looking at 8-10
>> results… are you sure you have matching MTUs?
>>
>>
>>
>> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.myitf
>> orum.com] *On Behalf Of *Kurt Buff
>> *Sent:* Monday, July 24, 2017 1:10 AM
>> *To:* ntsysadm
>> *Subject:* Re: [NTSysADM] RPC not available on remote machine while
>> doing DFSR config
>>
>>
>>
>> Ignore my earlier message from this evening. I've overcome some blindness
>> on my part, and have a bit more information, though I fear it's not enough.
>> I used this page for what looks to be a better way to handle the errors:
>> https://stackoverflow.com/questions/38419325/catching-full-
>> exception-message
>>
>> The red highlighted error is new - but I don't know why that's there.
>> It's very strange, as both are 2012R2 servers, in the same domain, and I'm
>> running this on my Win10 workstation with my DA credentials.
>>
>>
>>
>> --Begin revised script--
>> $NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
>> New-DfsReplicationGroup -GroupName US2AU-Engineering
>> $GroupName = Get-DfsReplicationGroup US2AU-Engineering
>> Foreach ($Line in $NewDFSR)
>>{
>> $GroupName = $Line.GroupName
>> $SourceComputer = $Line.SourceComputer
>> $FolderName = $Line.FolderName
>> $SourceContentPath = $Line.SourceContentPath
>> $SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
>> $SourcePrimaryMember = [System.Convert]::ToBoolean($L
>> ine.SourcePrimaryMember)
>> $DestinationComputer = $Line.DestinationComputer
>> $DestinationContentPath = $Line.DestinationContentPath
>> $DestinationReadOnly = [System.Convert]::ToBoolean($L
>> ine.DestinationReadOnly)
>> New-DfsReplicatedFolder -GroupName $GroupName -FolderName $FolderName
>> Try
>>{
>>Add-DfsrMember -GroupName $GroupName -ComputerName
>> $SourceComputer, $DestinationComputer
>>}
>> Catch
>>
>>
>>
>>
>>
>>
>> * {$e = $_.Exception$msg = $e.Messagewhile
>> ($e.InnerException) {   $e = $e.InnerException   $msg +=
>> &q

Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[elsalvoz]

Can you open PSSISSION on either server? You run the commands manually for
testing purposes

Cesar A.

On Jul 24, 2017 12:22 PM, "Kurt Buff" <kurt.b...@gmail.com> wrote:

> So, fixing the MTU mismatch seems not to have worked. I left the physical
> interface MTUs on both sides at 1500, and set up the MTUs for the tunnel
> interfaces at 1385, and verified that ping -f -l succeeds at 1357 and fails
> at 1358 from both sides.
>
> I even took a single set of entries from my CSV file and unrolled the
> loop, manually replacing the variables with values, including FQDNs for the
> machine names.
>
> Same failure:
>
> # Add-DfsrMember -GroupName US2AU-Engineering -ComputerName
> usfs01p.example.com, aufs01p.example.com
>
> Add-DfsrMember : Could not add the computer to the replication group.
> Computer: aufs01p.example.com Replication group: "US2AU-Engineering" The
> remote procedure call failed
> At line:1 char:1
> + Add-DfsrMember -GroupName US2AU-Engineering -ComputerName usfs01p.exampl
> ...
> + ~
> + CategoryInfo  : NotSpecified: (aufs01p.example.com:String)
> [Add-DfsrMember], DfsrException
> + FullyQualifiedErrorId : Add-DfsrMember.NonTerminatingOMException,
> Microsoft.DistributedFileSystemReplication.Commands.AddDfsrMemberCommand
>
> Additionally, I tried running the script on the DC in the AU office, and
> get the reciprocal failure (RPC failure, can't resolve the name of the US
> file server).
>
> Kurt
>
> On Mon, Jul 24, 2017 at 7:54 AM, Michael B. Smith <mich...@smithcons.com>
> wrote:
>
>> Yep, those MTUs.  Because inconsistent RPC fragmentation can cause
>> transactions to fail.
>>
>>
>>
>> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.myitf
>> orum.com] *On Behalf Of *Kurt Buff
>> *Sent:* Monday, July 24, 2017 10:44 AM
>>
>> *To:* ntsysadm
>> *Subject:* Re: [NTSysADM] RPC not available on remote machine while
>> doing DFSR config
>>
>>
>>
>> MTUs? As in TCP/IP Maximum Transmission Units?
>>
>> I will check that and post back, but why would a mismatch in MTU show up
>> as this?
>>
>> Kurt
>>
>>
>>
>> On Mon, Jul 24, 2017 at 5:31 AM, Michael B. Smith <mich...@smithcons.com>
>> wrote:
>>
>> I’m certain you can google as well as I can – but after looking at 8-10
>> results… are you sure you have matching MTUs?
>>
>>
>>
>> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.myitf
>> orum.com] *On Behalf Of *Kurt Buff
>> *Sent:* Monday, July 24, 2017 1:10 AM
>> *To:* ntsysadm
>> *Subject:* Re: [NTSysADM] RPC not available on remote machine while
>> doing DFSR config
>>
>>
>>
>> Ignore my earlier message from this evening. I've overcome some blindness
>> on my part, and have a bit more information, though I fear it's not enough.
>> I used this page for what looks to be a better way to handle the errors:
>> https://stackoverflow.com/questions/38419325/catching-full-
>> exception-message
>>
>> The red highlighted error is new - but I don't know why that's there.
>> It's very strange, as both are 2012R2 servers, in the same domain, and I'm
>> running this on my Win10 workstation with my DA credentials.
>>
>>
>>
>> --Begin revised script--
>> $NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
>> New-DfsReplicationGroup -GroupName US2AU-Engineering
>> $GroupName = Get-DfsReplicationGroup US2AU-Engineering
>> Foreach ($Line in $NewDFSR)
>>{
>> $GroupName = $Line.GroupName
>> $SourceComputer = $Line.SourceComputer
>> $FolderName = $Line.FolderName
>> $SourceContentPath = $Line.SourceContentPath
>> $SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
>> $SourcePrimaryMember = [System.Convert]::ToBoolean($L
>> ine.SourcePrimaryMember)
>> $DestinationComputer = $Line.DestinationComputer
>> $DestinationContentPath = $Line.DestinationContentPath
>> $DestinationReadOnly = [System.Convert]::ToBoolean($L
>> ine.DestinationReadOnly)
>> New-DfsReplicatedFolder -GroupName $GroupName -FolderName $FolderName
>> Try
>>{
>>Add-DfsrMember -GroupName $GroupName -ComputerName
>> $SourceComputer, $DestinationComputer
>>}
>> Catch
>>
>>
>>
>>
>>
>>
>> * {$e = $_.Exception$msg = $e.Messagewhile
>> ($e.InnerException) {  

Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Kurt Buff]

So, fixing the MTU mismatch seems not to have worked. I left the physical
interface MTUs on both sides at 1500, and set up the MTUs for the tunnel
interfaces at 1385, and verified that ping -f -l succeeds at 1357 and fails
at 1358 from both sides.

I even took a single set of entries from my CSV file and unrolled the loop,
manually replacing the variables with values, including FQDNs for the
machine names.

Same failure:

# Add-DfsrMember -GroupName US2AU-Engineering -ComputerName
usfs01p.example.com, aufs01p.example.com

Add-DfsrMember : Could not add the computer to the replication group.
Computer: aufs01p.example.com Replication group: "US2AU-Engineering" The
remote procedure call failed
At line:1 char:1
+ Add-DfsrMember -GroupName US2AU-Engineering -ComputerName usfs01p.exampl
...
+ ~
+ CategoryInfo  : NotSpecified: (aufs01p.example.com:String)
[Add-DfsrMember], DfsrException
+ FullyQualifiedErrorId :
Add-DfsrMember.NonTerminatingOMException,Microsoft.DistributedFileSystemReplication.Commands.AddDfsrMemberCommand

Additionally, I tried running the script on the DC in the AU office, and
get the reciprocal failure (RPC failure, can't resolve the name of the US
file server).

Kurt

On Mon, Jul 24, 2017 at 7:54 AM, Michael B. Smith <mich...@smithcons.com>
wrote:

> Yep, those MTUs.  Because inconsistent RPC fragmentation can cause
> transactions to fail.
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kurt Buff
> *Sent:* Monday, July 24, 2017 10:44 AM
>
> *To:* ntsysadm
> *Subject:* Re: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> MTUs? As in TCP/IP Maximum Transmission Units?
>
> I will check that and post back, but why would a mismatch in MTU show up
> as this?
>
> Kurt
>
>
>
> On Mon, Jul 24, 2017 at 5:31 AM, Michael B. Smith <mich...@smithcons.com>
> wrote:
>
> I’m certain you can google as well as I can – but after looking at 8-10
> results… are you sure you have matching MTUs?
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kurt Buff
> *Sent:* Monday, July 24, 2017 1:10 AM
> *To:* ntsysadm
> *Subject:* Re: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> Ignore my earlier message from this evening. I've overcome some blindness
> on my part, and have a bit more information, though I fear it's not enough.
> I used this page for what looks to be a better way to handle the errors:
> https://stackoverflow.com/questions/38419325/catching-
> full-exception-message
>
> The red highlighted error is new - but I don't know why that's there. It's
> very strange, as both are 2012R2 servers, in the same domain, and I'm
> running this on my Win10 workstation with my DA credentials.
>
>
>
> --Begin revised script--
> $NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
> New-DfsReplicationGroup -GroupName US2AU-Engineering
> $GroupName = Get-DfsReplicationGroup US2AU-Engineering
> Foreach ($Line in $NewDFSR)
>{
> $GroupName = $Line.GroupName
> $SourceComputer = $Line.SourceComputer
> $FolderName = $Line.FolderName
> $SourceContentPath = $Line.SourceContentPath
> $SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
> $SourcePrimaryMember = [System.Convert]::ToBoolean($
> Line.SourcePrimaryMember)
> $DestinationComputer = $Line.DestinationComputer
> $DestinationContentPath = $Line.DestinationContentPath
> $DestinationReadOnly = [System.Convert]::ToBoolean($
> Line.DestinationReadOnly)
> New-DfsReplicatedFolder -GroupName $GroupName -FolderName $FolderName
> Try
>{
>Add-DfsrMember -GroupName $GroupName -ComputerName $SourceComputer,
> $DestinationComputer
>}
> Catch
>
>
>
>
>
>
> * {$e = $_.Exception$msg = $e.Messagewhile
> ($e.InnerException) {   $e = $e.InnerException   $msg +=
> "`n" + $e.Message}*
>$msg}
> Add-DfsrConnection -GroupName $GroupName -SourceComputerName
> $SourceComputer -DestinationComputerName $DestinationComputer -ErrorAction
> Stop
> Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName
> -ComputerName $SourceComputer -ContentPath $SourceContentPath
> -PrimaryMember $SourcePrimaryMember -StagingPathQuotaInMB
> $SourceStagingPathQuotaInMB -Force
> Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName
> -ComputerName $DestinationComputer -ContentPath $DestinationContentPath
> -ReadOnly $Destination

Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Kurt Buff]

H..

US Interface MTU: 1500
US tunnel MTU: 1428
AU Interface MTU: 1500
AU tunnel MTU: 1384

Definite mismatch on the tunnel MTUs.

Let me see if I can correct that, and see what happens.

Kurt

On Mon, Jul 24, 2017 at 5:31 AM, Michael B. Smith <mich...@smithcons.com>
wrote:

> I’m certain you can google as well as I can – but after looking at 8-10
> results… are you sure you have matching MTUs?
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kurt Buff
> *Sent:* Monday, July 24, 2017 1:10 AM
> *To:* ntsysadm
> *Subject:* Re: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> Ignore my earlier message from this evening. I've overcome some blindness
> on my part, and have a bit more information, though I fear it's not enough.
> I used this page for what looks to be a better way to handle the errors:
> https://stackoverflow.com/questions/38419325/catching-
> full-exception-message
>
> The red highlighted error is new - but I don't know why that's there. It's
> very strange, as both are 2012R2 servers, in the same domain, and I'm
> running this on my Win10 workstation with my DA credentials.
>
>
>
> --Begin revised script--
> $NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
> New-DfsReplicationGroup -GroupName US2AU-Engineering
> $GroupName = Get-DfsReplicationGroup US2AU-Engineering
> Foreach ($Line in $NewDFSR)
>{
> $GroupName = $Line.GroupName
> $SourceComputer = $Line.SourceComputer
> $FolderName = $Line.FolderName
> $SourceContentPath = $Line.SourceContentPath
> $SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
> $SourcePrimaryMember = [System.Convert]::ToBoolean($
> Line.SourcePrimaryMember)
> $DestinationComputer = $Line.DestinationComputer
> $DestinationContentPath = $Line.DestinationContentPath
> $DestinationReadOnly = [System.Convert]::ToBoolean($
> Line.DestinationReadOnly)
> New-DfsReplicatedFolder -GroupName $GroupName -FolderName $FolderName
> Try
>{
>Add-DfsrMember -GroupName $GroupName -ComputerName $SourceComputer,
> $DestinationComputer
>}
> Catch
>
>
>
>
>
>
> * {$e = $_.Exception$msg = $e.Messagewhile
> ($e.InnerException) {   $e = $e.InnerException   $msg +=
> "`n" + $e.Message}*
>$msg}
> Add-DfsrConnection -GroupName $GroupName -SourceComputerName
> $SourceComputer -DestinationComputerName $DestinationComputer -ErrorAction
> Stop
> Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName
> -ComputerName $SourceComputer -ContentPath $SourceContentPath
> -PrimaryMember $SourcePrimaryMember -StagingPathQuotaInMB
> $SourceStagingPathQuotaInMB -Force
> Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName
> -ComputerName $DestinationComputer -ContentPath $DestinationContentPath
> -ReadOnly $DestinationReadOnly -Force
> }
> Set-DfsrConnectionSchedule -GroupName "US2AU-Engineering"
> -SourceComputerName "USfs01p" -DestinationComputerName "AUfs01p" -Day
> 1,2,3,4,5 -BandwidthDetail "ff
> ff"
> Update-DfsrConfigurationFromAD -ComputerName $SourceComputer,$
> DestinationComputer
>
> -End Revised Script--
>
> Relevant output:
>
> -Begin snipped output--
> Could not add the computer to the replication group. Computer: AUFS01P
> Replication group: "US2AU-Engineering" The remote procedure call failed
> *The operating system version of server AUFS01P cannot be retrieved.*
> The remote procedure call failed
> Add-DfsrConnection : The connection could not be added because DFS
> Replication could not find at least one source and one destination computer
> in the replication group, or because the
> source and destination computers were the same. Source computer: USFS01P
> Destination computer: AUFS01P Replication group: "US2AU-Engineering"
> At C:\BatchFiles\Configure-NewDFSR2.ps1:32 char:5
> + Add-DfsrConnection -GroupName $GroupName -SourceComputerName $Sou ...
> + ~
> + CategoryInfo  : ObjectNotFound: (:) [Add-DfsrConnection],
> DfsrException
> + FullyQualifiedErrorId : Add-DfsrConnection.NoDistinctMemberPairs,
> Microsoft.DistributedFileSystemReplication.Commands.
> AddDfsrConnectionCommand
> -End snipped output--
>
>
>
> On Fri, Jul 21, 2017 at 8:27 PM, Michael B. Smith <mic

RE: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Michael B. Smith]

Yep, those MTUs.  Because inconsistent RPC fragmentation can cause transactions 
to fail.

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Kurt Buff
Sent: Monday, July 24, 2017 10:44 AM
To: ntsysadm
Subject: Re: [NTSysADM] RPC not available on remote machine while doing DFSR 
config

MTUs? As in TCP/IP Maximum Transmission Units?
I will check that and post back, but why would a mismatch in MTU show up as 
this?
Kurt

On Mon, Jul 24, 2017 at 5:31 AM, Michael B. Smith 
<mich...@smithcons.com<mailto:mich...@smithcons.com>> wrote:
I’m certain you can google as well as I can – but after looking at 8-10 
results… are you sure you have matching MTUs?

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of Kurt Buff
Sent: Monday, July 24, 2017 1:10 AM
To: ntsysadm
Subject: Re: [NTSysADM] RPC not available on remote machine while doing DFSR 
config

Ignore my earlier message from this evening. I've overcome some blindness on my 
part, and have a bit more information, though I fear it's not enough. I used 
this page for what looks to be a better way to handle the errors:
https://stackoverflow.com/questions/38419325/catching-full-exception-message
The red highlighted error is new - but I don't know why that's there. It's very 
strange, as both are 2012R2 servers, in the same domain, and I'm running this 
on my Win10 workstation with my DA credentials.

--Begin revised script--
$NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
New-DfsReplicationGroup -GroupName US2AU-Engineering
$GroupName = Get-DfsReplicationGroup US2AU-Engineering
Foreach ($Line in $NewDFSR)
   {
$GroupName = $Line.GroupName
$SourceComputer = $Line.SourceComputer
$FolderName = $Line.FolderName
$SourceContentPath = $Line.SourceContentPath
$SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
$SourcePrimaryMember = 
[System.Convert]::ToBoolean($Line.SourcePrimaryMember)
$DestinationComputer = $Line.DestinationComputer
$DestinationContentPath = $Line.DestinationContentPath
$DestinationReadOnly = 
[System.Convert]::ToBoolean($Line.DestinationReadOnly)
New-DfsReplicatedFolder -GroupName $GroupName -FolderName $FolderName
Try
   {
   Add-DfsrMember -GroupName $GroupName -ComputerName $SourceComputer, 
$DestinationComputer
   }
Catch
   {
   $e = $_.Exception
   $msg = $e.Message
   while ($e.InnerException) {
  $e = $e.InnerException
  $msg += "`n" + $e.Message
   }
   $msg}
Add-DfsrConnection -GroupName $GroupName -SourceComputerName 
$SourceComputer -DestinationComputerName $DestinationComputer -ErrorAction Stop
Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName 
-ComputerName $SourceComputer -ContentPath $SourceContentPath -PrimaryMember 
$SourcePrimaryMember -StagingPathQuotaInMB $SourceStagingPathQuotaInMB -Force
Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName 
-ComputerName $DestinationComputer -ContentPath $DestinationContentPath 
-ReadOnly $DestinationReadOnly -Force
}
Set-DfsrConnectionSchedule -GroupName "US2AU-Engineering" -SourceComputerName 
"USfs01p" -DestinationComputerName "AUfs01p" -Day 1,2,3,4,5 -BandwidthDetail 
""
Update-DfsrConfigurationFromAD -ComputerName 
$SourceComputer,$DestinationComputer
-End Revised Script--
Relevant output:
-Begin snipped output--
Could not add the computer to the replication group. Computer: AUFS01P 
Replication group: "US2AU-Engineering" The remote procedure call failed
The operating system version of server AUFS01P cannot be retrieved.
The remote procedure call failed
Add-DfsrConnection : The connection could not be added because DFS Replication 
could not find at least one source and one destination computer in the 
replication group, or because the
source and destination computers were the same. Source computer: USFS01P 
Destination computer: AUFS01P Replication group: "US2AU-Engineering"
At C:\BatchFiles\Configure-NewDFSR2.ps1:32 char:5
+ Add-DfsrConnection -GroupName $GroupName -SourceComputerName $Sou ...
+ ~
+ CategoryInfo  : ObjectNotFound: (:) [Add-DfsrConnection], 
DfsrException
+ FullyQualifiedErrorId : 
Add-DfsrConnection.NoDistinctMemberPairs,Microsoft.DistributedFileSystemReplication.Commands.AddDfsrConnectionCommand
-End snipped output--

On Fri, Jul 21, 2017 at 8:27 PM, Michael B. Smith 
<mich...@smithcons.com<mailto:mich...@smithcons.com>> wrote:
What is the InnerException of the error?

---

Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Kurt Buff]

MTUs? As in TCP/IP Maximum Transmission Units?

I will check that and post back, but why would a mismatch in MTU show up as
this?

Kurt

On Mon, Jul 24, 2017 at 5:31 AM, Michael B. Smith <mich...@smithcons.com>
wrote:

> I’m certain you can google as well as I can – but after looking at 8-10
> results… are you sure you have matching MTUs?
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kurt Buff
> *Sent:* Monday, July 24, 2017 1:10 AM
> *To:* ntsysadm
> *Subject:* Re: [NTSysADM] RPC not available on remote machine while doing
> DFSR config
>
>
>
> Ignore my earlier message from this evening. I've overcome some blindness
> on my part, and have a bit more information, though I fear it's not enough.
> I used this page for what looks to be a better way to handle the errors:
> https://stackoverflow.com/questions/38419325/catching-
> full-exception-message
>
> The red highlighted error is new - but I don't know why that's there. It's
> very strange, as both are 2012R2 servers, in the same domain, and I'm
> running this on my Win10 workstation with my DA credentials.
>
>
>
> --Begin revised script--
> $NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
> New-DfsReplicationGroup -GroupName US2AU-Engineering
> $GroupName = Get-DfsReplicationGroup US2AU-Engineering
> Foreach ($Line in $NewDFSR)
>{
> $GroupName = $Line.GroupName
> $SourceComputer = $Line.SourceComputer
> $FolderName = $Line.FolderName
> $SourceContentPath = $Line.SourceContentPath
> $SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
> $SourcePrimaryMember = [System.Convert]::ToBoolean($
> Line.SourcePrimaryMember)
> $DestinationComputer = $Line.DestinationComputer
> $DestinationContentPath = $Line.DestinationContentPath
> $DestinationReadOnly = [System.Convert]::ToBoolean($
> Line.DestinationReadOnly)
> New-DfsReplicatedFolder -GroupName $GroupName -FolderName $FolderName
> Try
>{
>Add-DfsrMember -GroupName $GroupName -ComputerName $SourceComputer,
> $DestinationComputer
>}
> Catch
>
>
>
>
>
>
> * {$e = $_.Exception$msg = $e.Messagewhile
> ($e.InnerException) {   $e = $e.InnerException   $msg +=
> "`n" + $e.Message}*
>$msg}
> Add-DfsrConnection -GroupName $GroupName -SourceComputerName
> $SourceComputer -DestinationComputerName $DestinationComputer -ErrorAction
> Stop
> Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName
> -ComputerName $SourceComputer -ContentPath $SourceContentPath
> -PrimaryMember $SourcePrimaryMember -StagingPathQuotaInMB
> $SourceStagingPathQuotaInMB -Force
> Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName
> -ComputerName $DestinationComputer -ContentPath $DestinationContentPath
> -ReadOnly $DestinationReadOnly -Force
> }
> Set-DfsrConnectionSchedule -GroupName "US2AU-Engineering"
> -SourceComputerName "USfs01p" -DestinationComputerName "AUfs01p" -Day
> 1,2,3,4,5 -BandwidthDetail "ff
> ff"
> Update-DfsrConfigurationFromAD -ComputerName $SourceComputer,$
> DestinationComputer
>
> -End Revised Script--
>
> Relevant output:
>
> -Begin snipped output--
> Could not add the computer to the replication group. Computer: AUFS01P
> Replication group: "US2AU-Engineering" The remote procedure call failed
> *The operating system version of server AUFS01P cannot be retrieved.*
> The remote procedure call failed
> Add-DfsrConnection : The connection could not be added because DFS
> Replication could not find at least one source and one destination computer
> in the replication group, or because the
> source and destination computers were the same. Source computer: USFS01P
> Destination computer: AUFS01P Replication group: "US2AU-Engineering"
> At C:\BatchFiles\Configure-NewDFSR2.ps1:32 char:5
> + Add-DfsrConnection -GroupName $GroupName -SourceComputerName $Sou ...
> + ~
> + CategoryInfo  : ObjectNotFound: (:) [Add-DfsrConnection],
> DfsrException
> + FullyQualifiedErrorId : Add-DfsrConnection.NoDistinctMemberPairs,
> Microsoft.DistributedFileSystemReplication.Commands.
> AddDfsrConnectionCommand
> -End snipped output--
>
>
>
> On Fri, Jul 21, 2017 at 8:27 PM, Michael B. Smith <mich...@smithcons.com>
> wrote:
>
> What is th

RE: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Michael B. Smith]

I’m certain you can google as well as I can – but after looking at 8-10 
results… are you sure you have matching MTUs?

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Kurt Buff
Sent: Monday, July 24, 2017 1:10 AM
To: ntsysadm
Subject: Re: [NTSysADM] RPC not available on remote machine while doing DFSR 
config

Ignore my earlier message from this evening. I've overcome some blindness on my 
part, and have a bit more information, though I fear it's not enough. I used 
this page for what looks to be a better way to handle the errors:
https://stackoverflow.com/questions/38419325/catching-full-exception-message
The red highlighted error is new - but I don't know why that's there. It's very 
strange, as both are 2012R2 servers, in the same domain, and I'm running this 
on my Win10 workstation with my DA credentials.

--Begin revised script--
$NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
New-DfsReplicationGroup -GroupName US2AU-Engineering
$GroupName = Get-DfsReplicationGroup US2AU-Engineering
Foreach ($Line in $NewDFSR)
   {
$GroupName = $Line.GroupName
$SourceComputer = $Line.SourceComputer
$FolderName = $Line.FolderName
$SourceContentPath = $Line.SourceContentPath
$SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
$SourcePrimaryMember = 
[System.Convert]::ToBoolean($Line.SourcePrimaryMember)
$DestinationComputer = $Line.DestinationComputer
$DestinationContentPath = $Line.DestinationContentPath
$DestinationReadOnly = 
[System.Convert]::ToBoolean($Line.DestinationReadOnly)
New-DfsReplicatedFolder -GroupName $GroupName -FolderName $FolderName
Try
   {
   Add-DfsrMember -GroupName $GroupName -ComputerName $SourceComputer, 
$DestinationComputer
   }
Catch
   {
   $e = $_.Exception
   $msg = $e.Message
   while ($e.InnerException) {
  $e = $e.InnerException
  $msg += "`n" + $e.Message
   }
   $msg}
Add-DfsrConnection -GroupName $GroupName -SourceComputerName 
$SourceComputer -DestinationComputerName $DestinationComputer -ErrorAction Stop
Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName 
-ComputerName $SourceComputer -ContentPath $SourceContentPath -PrimaryMember 
$SourcePrimaryMember -StagingPathQuotaInMB $SourceStagingPathQuotaInMB -Force
Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName 
-ComputerName $DestinationComputer -ContentPath $DestinationContentPath 
-ReadOnly $DestinationReadOnly -Force
}
Set-DfsrConnectionSchedule -GroupName "US2AU-Engineering" -SourceComputerName 
"USfs01p" -DestinationComputerName "AUfs01p" -Day 1,2,3,4,5 -BandwidthDetail 
""
Update-DfsrConfigurationFromAD -ComputerName 
$SourceComputer,$DestinationComputer
-End Revised Script--

Relevant output:
-Begin snipped output--
Could not add the computer to the replication group. Computer: AUFS01P 
Replication group: "US2AU-Engineering" The remote procedure call failed
The operating system version of server AUFS01P cannot be retrieved.
The remote procedure call failed
Add-DfsrConnection : The connection could not be added because DFS Replication 
could not find at least one source and one destination computer in the 
replication group, or because the
source and destination computers were the same. Source computer: USFS01P 
Destination computer: AUFS01P Replication group: "US2AU-Engineering"
At C:\BatchFiles\Configure-NewDFSR2.ps1:32 char:5
+ Add-DfsrConnection -GroupName $GroupName -SourceComputerName $Sou ...
+ ~
+ CategoryInfo  : ObjectNotFound: (:) [Add-DfsrConnection], 
DfsrException
+ FullyQualifiedErrorId : 
Add-DfsrConnection.NoDistinctMemberPairs,Microsoft.DistributedFileSystemReplication.Commands.AddDfsrConnectionCommand
-End snipped output--

On Fri, Jul 21, 2017 at 8:27 PM, Michael B. Smith 
<mich...@smithcons.com<mailto:mich...@smithcons.com>> wrote:
What is the InnerException of the error?

-Original Message-
From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of Kurt Buff
Sent: Friday, July 21, 2017 11:11 PM
To: ntsysadm
Subject: [NTSysADM] RPC not available on remote machine while doing DFSR config

All,

I'm re-doing the DFSR config for the file servers in our US and AU offices. The 
US has a bunch of directories that will be replicated to AU (but not back). No 
big deal, but the PowerShell script I'm writing is killing me. I don't know if 
I'm running into a time out problem, or what it might be.

I'm running the script from Redmond on m

Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Kurt Buff]

Ignore my earlier message from this evening. I've overcome some blindness
on my part, and have a bit more information, though I fear it's not enough.
I used this page for what looks to be a better way to handle the errors:
https://stackoverflow.com/questions/38419325/catching-full-exception-message

The red highlighted error is new - but I don't know why that's there. It's
very strange, as both are 2012R2 servers, in the same domain, and I'm
running this on my Win10 workstation with my DA credentials.

--Begin revised script--
$NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
New-DfsReplicationGroup -GroupName US2AU-Engineering
$GroupName = Get-DfsReplicationGroup US2AU-Engineering
Foreach ($Line in $NewDFSR)
   {
$GroupName = $Line.GroupName
$SourceComputer = $Line.SourceComputer
$FolderName = $Line.FolderName
$SourceContentPath = $Line.SourceContentPath
$SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
$SourcePrimaryMember =
[System.Convert]::ToBoolean($Line.SourcePrimaryMember)
$DestinationComputer = $Line.DestinationComputer
$DestinationContentPath = $Line.DestinationContentPath
$DestinationReadOnly =
[System.Convert]::ToBoolean($Line.DestinationReadOnly)
New-DfsReplicatedFolder -GroupName $GroupName -FolderName $FolderName
Try
   {
   Add-DfsrMember -GroupName $GroupName -ComputerName $SourceComputer,
$DestinationComputer
   }
Catch






* {   $e = $_.Exception   $msg = $e.Message   while
($e.InnerException) {  $e = $e.InnerException  $msg += "`n"
+ $e.Message   }*
   $msg}
Add-DfsrConnection -GroupName $GroupName -SourceComputerName
$SourceComputer -DestinationComputerName $DestinationComputer -ErrorAction
Stop
Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName
-ComputerName $SourceComputer -ContentPath $SourceContentPath
-PrimaryMember $SourcePrimaryMember -StagingPathQuotaInMB
$SourceStagingPathQuotaInMB -Force
Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName
-ComputerName $DestinationComputer -ContentPath $DestinationContentPath
-ReadOnly $DestinationReadOnly -Force
}
Set-DfsrConnectionSchedule -GroupName "US2AU-Engineering"
-SourceComputerName "USfs01p" -DestinationComputerName "AUfs01p" -Day
1,2,3,4,5 -BandwidthDetail
""
Update-DfsrConfigurationFromAD -ComputerName
$SourceComputer,$DestinationComputer
-End Revised Script--


Relevant output:
-Begin snipped output--
Could not add the computer to the replication group. Computer: AUFS01P
Replication group: "US2AU-Engineering" The remote procedure call failed
*The operating system version of server AUFS01P cannot be retrieved.*
The remote procedure call failed
Add-DfsrConnection : The connection could not be added because DFS
Replication could not find at least one source and one destination computer
in the replication group, or because the
source and destination computers were the same. Source computer: USFS01P
Destination computer: AUFS01P Replication group: "US2AU-Engineering"
At C:\BatchFiles\Configure-NewDFSR2.ps1:32 char:5
+ Add-DfsrConnection -GroupName $GroupName -SourceComputerName $Sou ...
+ ~
+ CategoryInfo  : ObjectNotFound: (:) [Add-DfsrConnection],
DfsrException
+ FullyQualifiedErrorId :
Add-DfsrConnection.NoDistinctMemberPairs,Microsoft.DistributedFileSystemReplication.Commands.AddDfsrConnectionCommand
-End snipped output--

On Fri, Jul 21, 2017 at 8:27 PM, Michael B. Smith 
wrote:

> What is the InnerException of the error?
>
> -Original Message-
> From: listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] On Behalf Of Kurt Buff
> Sent: Friday, July 21, 2017 11:11 PM
> To: ntsysadm
> Subject: [NTSysADM] RPC not available on remote machine while doing DFSR
> config
>
> All,
>
> I'm re-doing the DFSR config for the file servers in our US and AU
> offices. The US has a bunch of directories that will be replicated to AU
> (but not back). No big deal, but the PowerShell script I'm writing is
> killing me. I don't know if I'm running into a time out problem, or what it
> might be.
>
> I'm running the script from Redmond on my laptop.
>
> Here's the script, which should Just Work(tm):
> --
>$NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
>
>New-DfsReplicationGroup -GroupName US2AU-Engineering
>$GroupName = Get-DfsReplicationGroup US2AU-Engineering
>
>Foreach ($Line in $NewDFSR)
>{
> $GroupName = $Line.GroupName
> $SourceComputer = $Line.SourceComputer
> $FolderName = $Line.FolderName
> $SourceContentPath = $Line.SourceContentPath
> $SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
> 

Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Kurt Buff]

I've failed, and need some help.

I looked a a lot of web sites, and tried several things none of which
seemed to help get diagnostics, so I finally settled on this, which doesn't
seem to give me any output:

   $NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
   New-DfsReplicationGroup -GroupName US2AU-Engineering
   $GroupName = Get-DfsReplicationGroup US2AU-Engineering
   Foreach ($Line in $NewDFSR)
   {
$GroupName = $Line.GroupName
$SourceComputer = $Line.SourceComputer
$FolderName = $Line.FolderName
$SourceContentPath = $Line.SourceContentPath
$SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
$SourcePrimaryMember =
[System.Convert]::ToBoolean($Line.SourcePrimaryMember)
$DestinationComputer = $Line.DestinationComputer
$DestinationContentPath = $Line.DestinationContentPath
$DestinationReadOnly =
[System.Convert]::ToBoolean($Line.DestinationReadOnly)

New-DfsReplicatedFolder -GroupName $GroupName -FolderName $FolderName






* Try {Add-DfsrMember -GroupName $GroupName -ComputerName
$SourceComputer, $DestinationComputer}Catch [Exception]
 {   write-host $_.Exception|format-list -force   }*
Add-DfsrConnection -GroupName $GroupName -SourceComputerName
$SourceComputer -DestinationComputerName $DestinationComputer
Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName
-ComputerName $SourceComputer -ContentPath $SourceContentPath
-PrimaryMember $SourcePrimaryMember -StagingPathQuotaInMB
$SourceStagingPathQuotaInMB -Force
Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName
-ComputerName $DestinationComputer -ContentPath $DestinationContentPath
-ReadOnly $DestinationReadOnly -Force
}
Set-DfsrConnectionSchedule -GroupName "US2AU-EngDrops" -SourceComputerName
"zusfs01p" -DestinationComputerName "zaufs01p" -Day 1,2,3,4,5
-BandwidthDetail
""
Update-DfsrConfigurationFromAD -ComputerName
$SourceComputer,$DestinationComputer


Output from the script (I used a single line in the CSV) is:

--
GroupName   : US2AU-Engineering
DomainName  : example.com
Identifier  : 77fe8261-ab6a-4041-b7b2-c8805410ebc3
Description :
State   : Normal

GroupName  : US2AU-Engineering
FolderName : Folder1
DomainName : example.com
Identifier : e8870682-624d-4f81-a0b8-3360aec13283
Description:
FileNameToExclude  : {~*, *.bak, *.tmp}
DirectoryNameToExclude : {}
DfsnPath   :
IsDfsnPathPublished: False
State  : Normal

GroupName: US2AU-Engineering
ComputerName : USFS01P
DomainName   : example.com
Identifier   : faccf9f0-e35b-4935-a431-5c08bde03e78
Description  :
DnsName  : USFS01p.example.com
Site : ExampleUS
NumberOfConnections  : 0
NumberOfInboundConnections   : 0
NumberOfOutboundConnections  : 0
NumberOfInterSiteConnections : 0
NumberOfIntraSiteConnections : 0
IsClusterNode: False
State: Normal














*Add-DfsrMember : Could not add the computer to the replication group.
Computer: AUFS01P Replication group: "US2AU-Engineering" The remote
procedure call failedAt line:20 char:9+ Add-DfsrMember -GroupName
$GroupName -ComputerName $SourceCom ...+
~+
CategoryInfo  : NotSpecified: (AUFS01P:String) [Add-DfsrMember],
DfsrException+ FullyQualifiedErrorId :
Add-DfsrMember.NonTerminatingOMException,Microsoft.DistributedFileSystemReplication.Commands.AddDfsrMemberCommand
Add-DfsrConnection
: The connection could not be added because DFS Replication could not find
at least one source and one destination computer in the replication group,
or because the source and destination computers were the same. Source
computer: USFS01P Destination computer: AUFS01P Replication group:
"US2AU-Engineering"At line:26 char:5+ Add-DfsrConnection -GroupName
$GroupName -SourceComputerName $Sou ...+
~+
CategoryInfo  : ObjectNotFound: (:) [Add-DfsrConnection],
DfsrException+ FullyQualifiedErrorId :
Add-DfsrConnection.NoDistinctMemberPairs,Microsoft.DistributedFileSystemReplication.Commands.AddDfsrConnectionCommand*

GroupName   : US2AU-Engineering
ComputerName: USFS01P
FolderName  : Folder1
GroupDomainName : example.com
ComputerDomainName  : example.com
Identifier  : c31d0a9a-cdb4-469e-b6c8-52f399130f6b
DistinguishedName   :

Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[elsalvoz]

Try enter-pssession cmdlet to test.

When I experience remote RPC issues is normally is due to firewall ports or
WMI issues or DCOM permissions

Cesar A.

On Jul 21, 2017 9:13 PM, "Kurt Buff"  wrote:

There you go, trying to educate me again.

I don't know.

I will have to figure that out, because I've not heard that term before.

I'll get back to you.

Kurt

On Fri, Jul 21, 2017 at 8:27 PM, Michael B. Smith 
wrote:
> What is the InnerException of the error?
>
> -Original Message-
> From: listsad...@lists.myitforum.com [mailto:listsadmin@lists.
myitforum.com] On Behalf Of Kurt Buff
> Sent: Friday, July 21, 2017 11:11 PM
> To: ntsysadm
> Subject: [NTSysADM] RPC not available on remote machine while doing DFSR
config
>
> All,
>
> I'm re-doing the DFSR config for the file servers in our US and AU
offices. The US has a bunch of directories that will be replicated to AU
(but not back). No big deal, but the PowerShell script I'm writing is
killing me. I don't know if I'm running into a time out problem, or what it
might be.
>
> I'm running the script from Redmond on my laptop.
>
> Here's the script, which should Just Work(tm):
> --
>$NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
>
>New-DfsReplicationGroup -GroupName US2AU-Engineering
>$GroupName = Get-DfsReplicationGroup US2AU-Engineering
>
>Foreach ($Line in $NewDFSR)
>{
> $GroupName = $Line.GroupName
> $SourceComputer = $Line.SourceComputer
> $FolderName = $Line.FolderName
> $SourceContentPath = $Line.SourceContentPath
> $SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
> $SourcePrimaryMember =
> [System.Convert]::ToBoolean($Line.SourcePrimaryMember)
> $DestinationComputer = $Line.DestinationComputer
> $DestinationContentPath = $Line.DestinationContentPath
> $DestinationReadOnly =
> [System.Convert]::ToBoolean($Line.$Line.DestinationReadOnly)
>
> New-DfsReplicatedFolder -GroupName $GroupName -FolderName $FolderName
> Add-DfsrMember -GroupName $GroupName -ComputerName $SourceComputer,
$DestinationComputer
> Add-DfsrConnection -GroupName $GroupName -SourceComputerName
$SourceComputer -DestinationComputerName $DestinationComputer
> Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName
-ComputerName $SourceComputer -ContentPath $SourceContentPath
-PrimaryMember $SourcePrimaryMember -StagingPathQuotaInMB
$SourceStagingPathQuotaInMB -Force
> Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName
-ComputerName $DestinationComputer -ContentPath $DestinationContentPath
-ReadOnly $DestinationReadOnly -Force
> }
> --
>
> But it fails the Add-DfsrMember command, when trying to add the AU file
server:
> --
>Add-DfsrMember : Could not add the computer to the replication group.
Computer: ZAUFS01P Replication group: "US2AU-Engineering" The remote
procedure call failed
>At C:\BatchFiles\New-DfsrConfiguration.ps1:19 char:2
>+ Add-DfsrMember -GroupName $GroupName -ComputerName
$SourceCompute ...
>+ ~
>+ CategoryInfo  : NotSpecified: (ZAUFS01P:String)
> [Add-DfsrMember], DfsrException
>+ FullyQualifiedErrorId :
> Add-DfsrMember.NonTerminatingOMException,Microsoft.
DistributedFileSystemReplication.Commands.AddDfsrMemberCommand
> --
>
> However, if I RDP to that file server, I see this, which to me indicates
that it *is* listening:
> --
>C:\Windows\system32>winrm enumerate winrm/config/listener
>Listener [Source="GPO"]
>Address = *
>Transport = HTTP
>Port = 5985
>Hostname
>Enabled = true
>URLPrefix = wsman
>CertificateThumbprint
>ListeningOn = 10.212.1.30, 127.0.0.1, ::1,
fe80::a9e7:6f85:8115:b4ed%16
> --
>
> Heck, I even stood up wireshark on my laptop, from which I'm running this
script, and see traffic to that server, though I can't quite figure out the
conversation - but I have a 48kb capture file detailing the transaction for
the attempted configuration of a single directory, if anyone wants that.
>
> Kurt
>
>

Re: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Kurt Buff]

There you go, trying to educate me again.

I don't know.

I will have to figure that out, because I've not heard that term before.

I'll get back to you.

Kurt

On Fri, Jul 21, 2017 at 8:27 PM, Michael B. Smith  wrote:
> What is the InnerException of the error?
>
> -Original Message-
> From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] 
> On Behalf Of Kurt Buff
> Sent: Friday, July 21, 2017 11:11 PM
> To: ntsysadm
> Subject: [NTSysADM] RPC not available on remote machine while doing DFSR 
> config
>
> All,
>
> I'm re-doing the DFSR config for the file servers in our US and AU offices. 
> The US has a bunch of directories that will be replicated to AU (but not 
> back). No big deal, but the PowerShell script I'm writing is killing me. I 
> don't know if I'm running into a time out problem, or what it might be.
>
> I'm running the script from Redmond on my laptop.
>
> Here's the script, which should Just Work(tm):
> --
>$NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv
>
>New-DfsReplicationGroup -GroupName US2AU-Engineering
>$GroupName = Get-DfsReplicationGroup US2AU-Engineering
>
>Foreach ($Line in $NewDFSR)
>{
> $GroupName = $Line.GroupName
> $SourceComputer = $Line.SourceComputer
> $FolderName = $Line.FolderName
> $SourceContentPath = $Line.SourceContentPath
> $SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
> $SourcePrimaryMember =
> [System.Convert]::ToBoolean($Line.SourcePrimaryMember)
> $DestinationComputer = $Line.DestinationComputer
> $DestinationContentPath = $Line.DestinationContentPath
> $DestinationReadOnly =
> [System.Convert]::ToBoolean($Line.$Line.DestinationReadOnly)
>
> New-DfsReplicatedFolder -GroupName $GroupName -FolderName $FolderName
> Add-DfsrMember -GroupName $GroupName -ComputerName $SourceComputer, 
> $DestinationComputer
> Add-DfsrConnection -GroupName $GroupName -SourceComputerName 
> $SourceComputer -DestinationComputerName $DestinationComputer
> Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName 
> -ComputerName $SourceComputer -ContentPath $SourceContentPath -PrimaryMember 
> $SourcePrimaryMember -StagingPathQuotaInMB $SourceStagingPathQuotaInMB -Force
> Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName 
> -ComputerName $DestinationComputer -ContentPath $DestinationContentPath 
> -ReadOnly $DestinationReadOnly -Force
> }
> --
>
> But it fails the Add-DfsrMember command, when trying to add the AU file 
> server:
> --
>Add-DfsrMember : Could not add the computer to the replication group. 
> Computer: ZAUFS01P Replication group: "US2AU-Engineering" The remote 
> procedure call failed
>At C:\BatchFiles\New-DfsrConfiguration.ps1:19 char:2
>+ Add-DfsrMember -GroupName $GroupName -ComputerName $SourceCompute ...
>+ ~
>+ CategoryInfo  : NotSpecified: (ZAUFS01P:String)
> [Add-DfsrMember], DfsrException
>+ FullyQualifiedErrorId :
> Add-DfsrMember.NonTerminatingOMException,Microsoft.DistributedFileSystemReplication.Commands.AddDfsrMemberCommand
> --
>
> However, if I RDP to that file server, I see this, which to me indicates that 
> it *is* listening:
> --
>C:\Windows\system32>winrm enumerate winrm/config/listener
>Listener [Source="GPO"]
>Address = *
>Transport = HTTP
>Port = 5985
>Hostname
>Enabled = true
>URLPrefix = wsman
>CertificateThumbprint
>ListeningOn = 10.212.1.30, 127.0.0.1, ::1, fe80::a9e7:6f85:8115:b4ed%16
> --
>
> Heck, I even stood up wireshark on my laptop, from which I'm running this 
> script, and see traffic to that server, though I can't quite figure out the 
> conversation - but I have a 48kb capture file detailing the transaction for 
> the attempted configuration of a single directory, if anyone wants that.
>
> Kurt
>
>

RE: [NTSysADM] RPC not available on remote machine while doing DFSR config

[Michael B. Smith]

What is the InnerException of the error?

-Original Message-
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Kurt Buff
Sent: Friday, July 21, 2017 11:11 PM
To: ntsysadm
Subject: [NTSysADM] RPC not available on remote machine while doing DFSR config

All,

I'm re-doing the DFSR config for the file servers in our US and AU offices. The 
US has a bunch of directories that will be replicated to AU (but not back). No 
big deal, but the PowerShell script I'm writing is killing me. I don't know if 
I'm running into a time out problem, or what it might be.

I'm running the script from Redmond on my laptop.

Here's the script, which should Just Work(tm):
--
   $NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv

   New-DfsReplicationGroup -GroupName US2AU-Engineering
   $GroupName = Get-DfsReplicationGroup US2AU-Engineering

   Foreach ($Line in $NewDFSR)
   {
$GroupName = $Line.GroupName
$SourceComputer = $Line.SourceComputer
$FolderName = $Line.FolderName
$SourceContentPath = $Line.SourceContentPath
$SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB
$SourcePrimaryMember =
[System.Convert]::ToBoolean($Line.SourcePrimaryMember)
$DestinationComputer = $Line.DestinationComputer
$DestinationContentPath = $Line.DestinationContentPath
$DestinationReadOnly =
[System.Convert]::ToBoolean($Line.$Line.DestinationReadOnly)

New-DfsReplicatedFolder -GroupName $GroupName -FolderName $FolderName
Add-DfsrMember -GroupName $GroupName -ComputerName $SourceComputer, 
$DestinationComputer
Add-DfsrConnection -GroupName $GroupName -SourceComputerName 
$SourceComputer -DestinationComputerName $DestinationComputer
Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName 
-ComputerName $SourceComputer -ContentPath $SourceContentPath -PrimaryMember 
$SourcePrimaryMember -StagingPathQuotaInMB $SourceStagingPathQuotaInMB -Force
Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName 
-ComputerName $DestinationComputer -ContentPath $DestinationContentPath 
-ReadOnly $DestinationReadOnly -Force
}
--

But it fails the Add-DfsrMember command, when trying to add the AU file server:
--
   Add-DfsrMember : Could not add the computer to the replication group. 
Computer: ZAUFS01P Replication group: "US2AU-Engineering" The remote procedure 
call failed
   At C:\BatchFiles\New-DfsrConfiguration.ps1:19 char:2
   + Add-DfsrMember -GroupName $GroupName -ComputerName $SourceCompute ...
   + ~
   + CategoryInfo  : NotSpecified: (ZAUFS01P:String)
[Add-DfsrMember], DfsrException
   + FullyQualifiedErrorId :
Add-DfsrMember.NonTerminatingOMException,Microsoft.DistributedFileSystemReplication.Commands.AddDfsrMemberCommand
--

However, if I RDP to that file server, I see this, which to me indicates that 
it *is* listening:
--
   C:\Windows\system32>winrm enumerate winrm/config/listener
   Listener [Source="GPO"]
   Address = *
   Transport = HTTP
   Port = 5985
   Hostname
   Enabled = true
   URLPrefix = wsman
   CertificateThumbprint
   ListeningOn = 10.212.1.30, 127.0.0.1, ::1, fe80::a9e7:6f85:8115:b4ed%16
--

Heck, I even stood up wireshark on my laptop, from which I'm running this 
script, and see traffic to that server, though I can't quite figure out the 
conversation - but I have a 48kb capture file detailing the transaction for the 
attempted configuration of a single directory, if anyone wants that.

Kurt