-------- Original Message --------
On 7/18/25 12:31, Zé Loff <zel...@zeloff.org> wrote:
> On Fri, Jul 18, 2025 at 09:39:43AM +0000, otto.cooper wrote:
> > -------- Original Message --------
> > On 7/17/25 23:36, Kenneth Gober wrote:
> > On Thu, Jul 17, 2025 at 11:05 AM otto.cooper <otto.coo...@proton.me> wrote:
> > Because alldirs was the only way to export different paths to specific
> clients.
> > /export/folder1 -alldirs client1 client2 client3
> > /export/folder2 -alldirs client1 client2
> > /export/folder3 -alldirs client1
> > Have you tried the following? The man page indicates this is how to do it:
> >
> > /export/folder1 /export/folder2 /export/folder3 client1
> > /export/folder1 /export/folder2 client2
> > /export/folder1 client3
> >
> > -ken
> >
> > I just tried it. OBSD exports it, no errors, but the windows client is
> unable to find those paths.
>
> FWIW, I have a similar setup, and it works fine with Windows 10. E.g.:
>
> /shared/misc -mapall=<user> <Win 10 client's IP>
>
> Where <user> is a valid user on the server, with the appropriate
> permissions for the /shared/misc directory.
>
>
> Did you really use "/export", or "/archive", as in your prior example?
As with all things Microsoft, rebooting was required. Now each client mounts
most of their folders, and can rename files in them. Renaming is a key test to
see if it working properly. They do not mount all folders: long paths are
refused when using mount.exe, but they are seen and mounted when exploring the
local network with microsoft explorer.
I'll work it some more, then report the results.
