[Samba] Domain DFS on new share

[L.P.H. van Belle]

Hai, 

Did you configure mutual authentication and integrity for the new share? 

I suspect something related to this, since you posted : 
> \\mydomain\sysvol does work, as well as \\mydomain\netlogon. 
> But, there is some issue with any \\mydomain\newshare.

Good info here : 
https://blogs.technet.microsoft.com/askpfeplat/2015/02/22/guidance-on-deployment-of-ms15-011-and-ms15-014/ 


Greetz, 

Louis



> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> Jonathan Hunter via samba
> Verzonden: vrijdag 21 april 2017 11:47
> Aan: mueller at tropenklinik.de
> CC: samba; Jeremy Allison
> Onderwerp: Re: [Samba] Domain DFS on new share
> 
> Hi,
> 
> On 21 April 2017 at 06:46, Mueller <mueller at tropenklinik.de> wrote:
> > Since  past the beta-times of samba 4  (and it worked in 
> former times!!) it never worked like this: \\yourdomain\share 
> or \\yourdomain \dfs-share.
> > The only thing working along witch your domain is: 
> \\yourdomain\netlogon.
> >
> > I had another thread open on this case some times ago.
> 
> Thank you Daniel - at least I am not going crazy and it did 
> work in the past :)
> 
> \\mydomain\sysvol does work, as well as \\mydomain\netlogon. 
> But, there is some issue with any \\mydomain\newshare.
> 
> I am not even sure that this is purely DFS related, as such, 
> now. Just to check things, I added the following share 
> definition to all my DCs (i.e. a simple share, without "msdfs 
> root = yes"), and I can't access this share either, via 
> \\mydomain\notdfs - albeit I get a different error from this.
> 
> [notdfs]
>         path = /usr/local/samba/dfsroot
> 
> From Windows Explorer (Windows 7 VM, domain member):
> \\mydomain\notdfs --> "\\mydomain\notdfs is not accessible. 
> You might not have permission to use this network resource. 
> Contact the administrator of this server to find out if you 
> have access permissions."
> 
> From cmd.exe on the same Windows 7 VM:
> C:\>net use * \\mydomain\notdfs
> Drive Y: is now connected to \\mydomain\notdfs.
> (Very weird! Y: does work, I can see an empty folder with no 
> issues (presumably the msdfs symlink in there is ignored by 
> default). Still no luck from Windows Explorer even if I try 
> \\mydomain\notdfs again)
> 
> When I try the same for my DFS share, though, still no luck, 
> even with "net use" :
> C:\>net use * \\mydomain\dfs
> System error 67 has occurred.
> The network name cannot be found.
> 
> I have also shared some packet captures with Jeremy; perhaps 
> he might spot something simple that's going on.
> 
> > -----Ursprüngliche Nachricht-----
> > Von: Jeremy Allison via samba [mailto:samba at lists.samba.org]
> > Gesendet: Freitag, 21. April 2017 01:27 [...]
> >
> > Wireshark trace needed I think.
> 
> --
> "If we knew what it was we were doing, it would not be called 
> research, would it?"
>       - Albert Einstein
> 
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
> 
>