sheeple wrote: 
> It remains that only with SMB 1.0 support reenabled on my Windows 10
> machine, I can see the drive at all on the network. But with the
> previously described limitations, that it is barely usable. These issues
> are known issues. It shreds me that there are Windows 10 users where it
> is purportedly working, however there is many reports on the webs where
> it isnt.
> 
> Here is my troubleshooting attempts so far, maybe someone can guide me
> from here to a new approach. What I did:
> 
> 1.) I checked with PowerShell ssh (working with this so far) whether the
> disk and the mounted partition are recognized: fdisk -l
> > 
Code:
--------------------
  >   > 
  > fdisk -l
  > tc@pCP:~$ tc@pCP:~$ fdisk -l
  > Disk /dev/mmcblk0: 30 GB, 32010928128 bytes, 62521344 sectors
  > 976896 cylinders, 4 heads, 16 sectors/track
  > Units: sectors of 1 * 512 = 512 bytes
  > 
  > Device       Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  
Size Id Type
  > /dev/mmcblk0p1    128,0,1     127,3,16          8192     139263     131072 
64.0M  c Win95 FAT32 (LBA)
  > /dev/mmcblk0p2    1023,3,16   1023,3,16       139264    2187263    2048000 
1000M 83 Linux
  > Disk /dev/sda: 932 GB, 1000204883968 bytes, 1953525164 sectors
  > 121601 cylinders, 255 heads, 63 sectors/track
  > Units: sectors of 1 * 512 = 512 bytes
  > 
  > Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size 
Id Type
  > /dev/sda1    0,1,1       1023,254,63         63 1953525104 1953525042  931G 
 7 HPFS/NTFS
--------------------
> > 
> 
> Yup, 931 GB recognized as disk and mounted device.
> 
> I checked whether samba was running: used smbd status
> 
> > 
Code:
--------------------
  >   > tc@pCP:~$ smbd status
  > [2022/02/27 13:05:46,  0] ../../lib/util/debug.c:1099(reopen_one_log)
  > reopen_one_log: Unable to open new log file '/var/log/log.smbd': Permission 
denied
  > [2022/02/27 13:05:46,  0] 
../../source3/lib/dumpcore.c:59(get_default_corepath)
  > Failed to create /var/log/cores for user 1001 with mode 0700
  > [2022/02/27 13:05:46,  0] ../../source3/lib/dumpcore.c:256(dump_core_setup)
  > Unable to setup corepath for smbd: File exists
  > [2022/02/27 13:05:46.291139,  0] ../../lib/util/debug.c:1099(reopen_one_log)
  > reopen_one_log: Unable to open new log file '/var/log/log.smbd': Permission 
denied
  > [2022/02/27 13:05:46.291185,  0] ../../source3/smbd/server.c:1782(main)
  > smbd version 4.12.6 started.
  > Copyright Andrew Tridgell and the Samba Team 1992-2020
  > 
--------------------
> > 
> Perhaps not the best command, anyway, a Samba 4.X instance is started.
> Fine.
> 
> According to this source
> https://www.elektronik-kompendium.de/sites/raspberry-pi/2101091.htm,
> for Windows 10 after Fall Creators Update 1709 with disabled SMB 1.0,
> it is recommended to add the following lines in smb.conf under the
> section [global]
> 
> > 
Code:
--------------------
  >   > client min protocol = SMB2
  > client max protocol = SMB3
  > 
--------------------
> > 
> According to this source
> https://www.cyberciti.biz/faq/how-to-configure-samba-to-use-smbv2-and-disable-smbv1-on-linux-or-unix/,
> for Samba 4.X it is possible to instead add the line 
> 
> > 
Code:
--------------------
  >   > protocol = SMB3
--------------------
> > 
> 
> I tried both but will document the first solution here. I entered 
> > 
Code:
--------------------
  >   > sudo vi /usr/local/etc/samba/smb.conf
--------------------
> > 
> and added the lines
> > 
Code:
--------------------
  >   > client min protocol = SMB2
  > client max protocol = SMB3
--------------------
> > 
> then safed and closed vi with :wq
> 
> I checked whether it was saved and reopend:
> 
> > 
Code:
--------------------
  >   > [global]
  > netbios name = music
  > workgroup = WORKGROUP
  > log file = /var/log/%m.log
  > max log size = 1000
  > local master = no
  > security = user
  > map to guest = bad user
  > dns proxy = no
  > load printers = no
  > client min protocol = SMB2
  > client max protocol = SMB3
  > [music]
  > path = /mnt/music
  > create mask = 0664
  > browseable = yes
  > writeable = yes
--------------------
> > 
> 
> Yes, still there. Then I used the smbd command that give a bit sketchy
> returns, and also restarted from within pCP backend later. I entered
> smbd restart smb.service and got
> > 
Code:
--------------------
  >   > tc@pCP:~$ tc@pCP:~$ smbd restart smb.service
  > [2022/02/27 13:10:18,  0] ../../lib/util/debug.c:1099(reopen_one_log)
  > reopen_one_log: Unable to open new log file '/var/log/log.smbd': Permission 
denied
  > [2022/02/27 13:10:18,  0] 
../../source3/lib/dumpcore.c:59(get_default_corepath)
  > Failed to create /var/log/cores for user 1001 with mode 0700
  > [2022/02/27 13:10:18,  0] ../../source3/lib/dumpcore.c:256(dump_core_setup)
  > Unable to setup corepath for smbd: File exists
  > [2022/02/27 13:10:18.240644,  0] ../../lib/util/debug.c:1099(reopen_one_log)
  > reopen_one_log: Unable to open new log file '/var/log/log.smbd': Permission 
denied
  > [2022/02/27 13:10:18.240691,  0] ../../source3/smbd/server.c:1782(main)
  > smbd version 4.12.6 started.
  > Copyright Andrew Tridgell and the Samba Team 1992-2020
--------------------
> > 
> 
> But no network drive appeared in windows. A restart of the Windows 10
> machine does not help either, nor a refresh of the network devices via
> Windows Explorer context menu. It is not shown.
> 
> After this, I did a reboot of the RaspberryPi. After reboot, no
> network drive in Windows 10, but also, I checked what happend to
> smb.conf. So I entered vi /usr/local/etc/samba/smb.conf and the
> entries that I had added to the file where erased:
> 
> > 
Code:
--------------------
  >   > [global]
  > netbios name = music
  > workgroup = WORKGROUP
  > log file = /var/log/%m.log
  > max log size = 1000
  > local master = no
  > security = user
  > map to guest = bad user
  > dns proxy = no
  > load printers = no
  > [music]
  > path = /dev/sda1
  > create mask = 0664
  > browseable = yes
  > writeable = yes
--------------------
> > 

Are you looking on Windows Explorer under “Network” or have you mapped a
Network drive?

The Pi may not appear under “Network” for some time due to the way
Windows works however if you go to PC and do “map network drive” and
enter \\PiIPaddress\share this should be available whenever the Pi is
up.

It’s Netbios vs TCP



Jim
https://jukeradio.double6.net


VB2.4[/B] STORAGE *QNAP TS419P (NFS)
[B]Living Room* Joggler & Pi4/Khadas  -> Onkyo TXNR686 -> Celestion F20s

*Office* Joggler & Pi3 -> Denon RCD N8 -> Celestion F10s 
*Dining Room* SB Radio
*Bedroom (Bedside)* Pi Zero+DAC ->ToppingTP21 ->AKG Headphones
*Bedroom (TV) & Bathroom* SB Touch ->Denon AVR ->Mordaunt Short M10s +
Kef ceiling speakers
*Guest Room* Joggler > Topping Amp -> Wharfedale Modus Cubes
------------------------------------------------------------------------
d6jg's Profile: http://forums.slimdevices.com/member.php?userid=44051
View this thread: http://forums.slimdevices.com/showthread.php?t=116037

_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins

Reply via email to