samba - Feb 2019 - Issue network share mapping - Windows 10

Hello,

I am facing issues to keep samba share to be mapping in Windows 10

After computer start, and first login, the share is mounted correctly.
Then user logout, wait for 5 min, and log in windows again, the share 
cannot be mounted.

An "error 64" occurs, with then "the specified network path is
not
available"...

My samba server is in version 3.5.6 (SMB1)
My Windows 10 client is uptodate 1609, and Worsktation is part of an 
Active Directory

I tried to solve by myself, and found this :

https://support.microsoft.com/en-us/help/4469342/november292018kb4469342osbuild17763167

I even configured GPO to reconnect mapped network drives via GPO in the 
AD, but not better success.

With Windows 7 client, I do not faced this issue...

May you help me ?

Best regards,

Ed

On Mon, 11 Feb 2019 14:46:56 -0300
Edouard Guigné via samba <samba at lists.samba.org> wrote:
> Hello,
> 
> I am facing issues to keep samba share to be mapping in Windows 10
> 
> After computer start, and first login, the share is mounted correctly.
> Then user logout, wait for 5 min, and log in windows again, the share 
> cannot be mounted.
> 
> An "error 64" occurs, with then "the specified network path
is not
> available"...
> 
> My samba server is in version 3.5.6
This is a dead release, it is over 8 years old
> (SMB1)
This is dying and is insecure.
 
> My Windows 10 client is uptodate 1609, 
No it isn't up to date, there have been at least a couple of updates
since 1609
>and Worsktation is part of an 
> Active Directory
Then why not turn the Samba server into a Unix domain client ? this
will require a Samba update and very probably an OS upgrade.
> 
> I tried to solve by myself, and found this :
> 
>
https://support.microsoft.com/en-us/help/4469342/november292018kb4469342osbuild17763167
> 
> I even configured GPO to reconnect mapped network drives via GPO in
> the AD, but not better success.
> 
> With Windows 7 client, I do not faced this issue...
That will be your next problem, Win7 mainstream support ended in 2015
and extended support will end in 2020.
> 
> May you help me ?
We can try, tell us what OS your Samba machine is running and post
your smb.conf

Rowland

On Mon, 11 Feb 2019 16:59:04 -0300
eguigne at pasteur-cayenne.fr wrote:
> Hello Rowland,
> 
> The linux is a very old Debian 5.0
> 
> That is why I want to migrate all workstations in a new AD domain,
> then replace the old samba share with a new one.
> Users needs to get access to the share during the migration (about 80
> workstations windows 7/10).
> Then, I will replace the old Win7 Workstations...
> 
> I did not precise that the share is mounted at users windows login via
> script .bat loaded by the AD controlers.
> 
> So I need to make Windows 10 working with this old Samba share during
> the time of the migration...
> 
> May you also tell me any weird things you notice in the attach
> smb.conf ?
> 
> 
The smb.conf is for an LDAP PDC, I do hope that your new AD domain isn't
using 'IPG' as its workgroup name.

Try adding 'server max protocol = NT1' to the samba.conf

Rowland

On Tue, 12 Feb 2019 14:21:10 -0300
Edouard Guigné <eguigne at pasteur-cayenne.fr> wrote:
> Hello Rowland,
> 
> I reinstalled the PC with the original image Windows 10 1607 ; in
> order to check if it was due to an windows update issue...
> 
> But this is not, the SMB1 share is accessible after pc boot and log
> in. User logs out.
> When the user logins back in Windows, the share is not accessible : 
> system error 85
> 
> *The only way to reconnect shares is to reboot the PC.*
> 
 
> On the server, this is the samba log for the windows 10 workstation :
> jaguar:/var/log/samba# tailf log.ipgvir11
> [2019/02/12 13:24:20.647863,  0]
> smbd/nttrans.c:2204(call_nt_transact_ioctl)
> call_nt_transact_ioctl(0x94264): Currently not implemented.
> [2019/02/12 13:26:39.879058,  1] smbd/service.c:1251(close_cnum)
> ipgvir11 (10.9.7.191) closed connection to service groups 
OK, I think this is your problem:

call_nt_transact_ioctl(0x94264): Currently not implemented.

0x94264 = FSCTL_OFFLOAD_READ

This was introduced with win8, so it wont be in your Samba 3.5

Have you got any old windows machines ?

Rowland