When trying to access samba shares from windows 2003 R2 SP2 I get "The specified network name is no longer available" and "System error 64 has occured" Accessing the sambe sambamachines from windows 2000 and windows XP pc-clients goes without any problems. Accessing other windows server on the same subnet as the sambservers from the terminalservers goes fine. I.e. Starte -> run -> \\<sambaserver>\<sharename> Results in the above error. To isolate the problem I have picked one sambaserver which and one terminalserver and one command to test (net use \\lordvader), lordvader being the sambaserver with sles9, x86 and samba 3.2.3 Net use \\lordvader results int the above error messages. I will upload debuglevel 10 output from lordvader during the above command + smb.conf + wireshark run from the test-server. -regards Erik
Created attachment 3631 [details] tar-gzip of /var/log/samba during the test. In addition smb.conf is there as well sambalogsandsmb.conf.tar.gz is an upload of the samba log dirctory during the run of "net view \\lordvader" + smb.conf
Created attachment 3632 [details] tar-gzip of /var/log/samba during netmon trace of "net view \\lordvader" tar-gzip of /var/log/samba during netmon trace of "net view \\lordvader"
Created attachment 3633 [details] gzipped smb.conf from lordvader
Created attachment 3634 [details] netmon trace from the same timeframe the sambalogs are from
>Net use \\lordvader results int the above error messages. Sorry. The command i tested was "net view \\lordvader" NOT "net use \\lordvader" -regards Erik
The terminalserver: hostname: h1-586-os0025, ip 10.151.28.27 linux-samaba-sserver: hostname: lordvader, ip 10.225.3.15 -regards Erik
I have found the root cause for this problem. The cause was that the windows Group Policy "Microsoft network client: Digitally sign communication (always)" was set to "enabled" Setting this to "disabled" and all our samba servers became accessible to windows-machines on the network. As I don't know if this samba 3.2.3 is supposed to support "Microsoft network client: Digitally sign communication (always)", I leave this bug in state NEW. -kind regards Erik
>As I don't know if this samba 3.2.3 is supposed to support "Microsoft network >client: Digitally sign communication (always)", I leave this bug in state NEW. The man pages for smb.conf says this is supported by setting "server signig = auto" However we didn't see that so we solved the problem by setting digital singing to optional at the windows client side.