samba - Feb 2015 - Error 64 connecting from WIndows 7

Hi all,

I'm running Samba 4.1.6 with Ubuntu 14.04.1 LTS on a Power 8 box.

Here is my smb.conf file:

[global]
client lanman auth = yes
client ntlmv2 auth = no
lanman auth = yes
netbios name = myName
map untrusted to domain = yes
log level = 3

[myshare]
path = /home/myuser/myshare
available = yes
valid users = myuser
read only = no
browseable = yes
public = yes
writable = yes

When I try to connect to the samba share from Windows 7 I get this error:

System error 64 - the specified network name is no longer available

In the /var/log/samba/log.my.client.ip.address I read:

[2015/02/24 18:03:00.468592,  3] ../source3/lib/access.c:338(allow_access)
  Allowed connection from x.x.x.x (x.x.x.x)
[2015/02/24 18:03:00.468977,  3] ../source3/smbd/oplock.c:870(init_oplocks)
  init_oplocks: initializing messages.
[2015/02/24 18:03:00.469149,  3] ../source3/smbd/process.c:1795(process_smb)
  Transaction 0 of length 4 (0 toread)
[2015/02/24 18:03:00.469205,  2] ../source3/smbd/process.c:1823(process_smb)
  Non-SMB packet of length 0. Terminating server
[2015/02/24 18:03:00.469358,  3] 
../source3/smbd/server_exit.c:212(exit_server_common)
  Server exit (Non-SMB packet)


Could you help me?

Thanks

Bye

Franco

Am 25.02.2015 um 17:03 schrieb Franco Lombardo:
> I'm running Samba 4.1.6 with Ubuntu 14.04.1 LTS on a Power 8 box.
>
> Here is my smb.conf file:
>
> [global]
> client lanman auth = yes
> client ntlmv2 auth = no
> lanman auth = yes
why?!

lanman auth = no
ntlm auth = no
client lanman auth = no
client ntlmv2 auth = yes
client signing = mandatory
server signing = mandatory

as recommended by security scanners works fine with Windows 7 and even 
WinXP after change a registry setting 
([HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"lmcompatibilitylevel"=dword:00000005)



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.samba.org/pipermail/samba/attachments/20150225/2026830c/attachment.pgp>

Reindl,

thank you for you answer. I did that strange configuration, because the 
default one did not work.

I tried what you suggested, but I'm still experiencing the same problem :-(


Bye

Franco