Issue with SMB (or could be with Win 10)

#4

What happens if you attempt to access the My Cloud, or map the My Cloud Share using the My Cloud’s IP address? Do you have the same problem?

In the following thread there is some discussion on SMB in Windows 10 when Microsoft borked the SMB2 a while back. May want to take a look and see if anything in there might help. There is a suggestion in that thread to configure the router as the “master browser” for SMB if the router supports such an option.

https://community.wd.com/t/compilation-of-windows-10-methods-steps-and-solutions/142576

#5

Thanks for that. Since this issue seems to happen randomly (after a reboot of my PC), the next time it happens I will look at a few things. I’ve never checked to see if my MyCloud shows up under network in Windows Explorer.

#6

try to use ipaddress to mount, its ez to resovle

#7

I’ll try that the next time it fails.

#8

OK, it happened again. So I tried with the IP address and it worked. Note that the WD MyCloud isn’t showing in Network on Windows explorer when I have this problem.

Also this is only a work around. It doesn’t get to the root cause of the problem.

Thanks to Bennor and liuhangchen.

#9

Have you updated your Windows 10 PC with ALL of the latest Windows 10 updates?

Are you running a third party Firewall software program? Or have you modified the Windows Firewall to block local network access to the My Cloud? Have you enabled NetBIOS over TCP/IP in Windows 10? Have you enabled local network sharing within Windows 10? Have you installed all of the latest Windows 10 updates?

See the link I posted previously that has this and other Windows 10 suggestions when one has issues accessing the My Cloud under Windows 10.

https://community.wd.com/t/compilation-of-windows-10-methods-steps-and-solutions/142576

#10

Windows 10 is up to date. I just use the Windows firewall and anti virus.

I’ve done all the things you suggest.

Remember this works OK most of the time. It’s just that occasionally for some reason the connection fails when I boot up my Windows PC.

This is different that when it fails because it tries before the network is connected. In that case you can just click on the drive icon and it works.

I have previously gone through that thread but will review it again.

#11

Is the IP address of your MyCloud being changed by the router?

#12

No. It’s address is reserved in the router.

Just as an FYI the last Win 10 update I have is cumulative update KB3200970. It was installed Nov 9th.

#13

As a test, try setting the Windows 10 SMB to SMB 1 or SMB3 and see if that works around your issue. See the link I posted earlier in the thread for directions on how to change the Windows 10 SMB version.

#14

OK, I’ll try that. BTW as always, rebooting the MyCloud resolves the issue. It now shows up in Network on my PC.

#15

OK, changing smb-global.conf to smb3. Not sure if I should try 1 or 3 but my windows 10 has ver 3.1.1.

Will let you know how it goes.

#16

Here is the difference after changing MyCloud to SMB3. Not the extra share for MyCloud at the bottom of the second group.

ServerName ShareName UserName Credential Dialect NumOpens


192.168.2.22 xxxxxxxx DESKTOP-EEIOJ9E\xxxxxxx MicrosoftAccount\xxxxxxxxx@outlook.com 2.1 1
192.168.2.22 xxxxxxx DESKTOP-EEIOJ9E\xxxxxx MicrosoftAccount\xxxxxxxxx@outlook.com 2.1 1
192.168.2.22 xxxxxxxx DESKTOP-EEIOJ9E\xxxxxx MicrosoftAccount\xxxxxxxxx@outlook.com 2.1 1
192.168.2.22 xxxxxxx DESKTOP-EEIOJ9E\xxxxxx MicrosoftAccount\xxxxxxxxx@outlook.com 2.1 1
DESKTOP-EEIOJ9E Users DESKTOP-EEIOJ9E\xxxxxx MicrosoftAccount\xxxxxxxxx@outlook.com 3.1.1 1
EPSON63F5DF MEMORYCARD DESKTOP-EEIOJ9E\xxxxxx MicrosoftAccount\xxxxxxxxx@outlook.com 1.5 1
EPSON63F5DF USBSTORAGE DESKTOP-EEIOJ9E\xxxxxx MicrosoftAccount\xxxxxxxxx@outlook.com 1.5 1

PS C:\WINDOWS\system32> Get-SmbConnection

ServerName ShareName UserName Credential Dialect NumOpens


192.168.2.22 xxxxxx DESKTOP-EEIOJ9E\xxxxxx MicrosoftAccount\xxxxxx@outlook.com 3.0 1
192.168.2.22 xxxxxx DESKTOP-EEIOJ9E\xxxxxx MicrosoftAccount\xxxxxx@outlook.com 3.0 2
192.168.2.22 xxxxxx DESKTOP-EEIOJ9E\xxxxxx MicrosoftAccount\xxxxxx@outlook.com 3.0 2
192.168.2.22 xxxxxx DESKTOP-EEIOJ9E\xxxxxx MicrosoftAccount\xxxxxx@outlook.com 3.0 1
DESKTOP-EEIOJ9E Users DESKTOP-EEIOJ9E\xxxxxx MicrosoftAccount\xxxxxx@outlook.com 3.1.1 2
EPSON63F5DF MEMORYCARD DESKTOP-EEIOJ9E\xxxxxx MicrosoftAccount\xxxxxx@outlook.com 1.5 1
EPSON63F5DF USBSTORAGE DESKTOP-EEIOJ9E\xxxxxx MicrosoftAccount\xxxxxx@outlook.com 1.5 1
WDMYCLOUD IPC$ DESKTOP-EEIOJ9E\xxxxxx MicrosoftAccount\xxxxxx@outlook.com 3.0 0

#17

Have rebooted PC several times since last post and so far so good.

#18

Problem is back. I booted my PC this am and all mapped drives were big red X. Clicking on them resulted in the original error message.

Did the Get-SMBConnection command in powershell and Mycloud didn’t show up. SSH’d into mycloud and ran TOP. Didn’t see nmb or smb. Started SAMBA and my mapped drives work. Also ran Get-SMBConnection and mycloud shows up.

I’m not sure this is the same issue, as before, if I started SAMBA, it didn’t fix things.

#19

One would ask why wasn’t SAMBA running? It’s suppose to start up on every boot.

#20

SAMBA was running when MyCloud last booted. However this morning when I booted my PC it apparently wasn’t. I will be checking logs on MyCloud to see if I can determine why SAMBA tasks weren’t running.

#21

I see this message in the SAMBA log, "WARNING: Ignoring invalid value ‘SMB3’ for parameter ‘max protocol’
".

Will try SMB1 as specified in the thread on Windows 10 methods posted by bennor.

#22

With SMB1 I get these messages:

[2016/12/06 15:51:25.924299, 0] (lp_set_enum_parm)
WARNING: Ignoring invalid value ‘SMB1’ for parameter ‘max protocol’
[2016/12/06 15:51:25.941807, 0] (lp_set_enum_parm)
WARNING: Ignoring invalid value ‘SMB1’ for parameter ‘max protocol’
[2016/12/06 15:52:09.099025, 0] (lp_set_enum_parm)
WARNING: Ignoring invalid value ‘SMB1’ for parameter ‘max protocol’
[2016/12/06 15:52:26.793302, 0] (pidfile_unlink)
Failed to delete pidfile /var/run/smbd.pid. Error was No such file or directory
[2016/12/06 15:55:16.302135, 0] (lp_set_enum_parm)
WARNING: Ignoring invalid value ‘SMB1’ for parameter ‘max protocol’
[2016/12/06 15:55:17.793646, 0] param/loadparm.c:7885(lp_set_enum_parm)
WARNING: Ignoring invalid value ‘SMB1’ for parameter ‘max protocol’
[2016/12/06 15:55:17.824837, 0] winbindd/winbindd_cache.c:3147(initialize_winbindd_cache)
initialize_winbindd_cache: clearing cache and re-creating with version number 2
[2016/12/06 15:57:38.074708, 0] (lp_set_enum_parm)
WARNING: Ignoring invalid value ‘SMB1’ for parameter ‘max protocol’

Apparently smb2 is the only form of the parameter that it will accept.

#23

What My Cloud model and version are you using? What other devices are on the local network?

If I remember right, I don’t think I had problems using SMB1 or SMB3 to access a first generation v4.x My Cloud when I was writing up the Compilation of Windows 10 Methods Steps and Solutions post.

If you haven’t done so already perhaps you should do a 40 second reset as it sounds like you have something weird going on with Samba on your My Cloud. I would also, as another troubleshooting step, disconnect/turn off all other network devices but the router, the My Cloud, and one single computer and then test again to see if the issues persist. I would reboot just those three devices to perform the testing to isolate if the issue is related to some other device on the local network.