Accessing WD MyCloud share via Start - Run

My Cloud OS 3 Personal & Network Attached Storage My Cloud
1

I may have inadvertently placed this in the My Cloud Home section… it feels like it should belong here.

Good evening, :wink:

My first post as it’s the first ever issue I’ve had with my WD MyCloud that I couldn’t seem to get past (and I can’t even claim the issue is down to this device, but more so my new Windows 10 laptop).

On previous laptops (which I still have, and have tried) I could happily access the folders on the WD MyCloud by typing the following (for my Images top-level folder) into Start → Run - \\192.168.1.2\Images and it would open up in a Windows Explorer window and I could happily drag and drop files etc…

This still works fine on a laptop running Windows XP and one running Windows 7.

On the new Windows 10 laptop - this does not work. Earlier today it seemed to result in opening a browser and arriving at http://192.168.1.2:9000 and showing me a Twonky page. I had no idea what that was all about, so a little research (possibly misguided now) led me to believe it was because Windows 10 had disabled Samba / CIFS and if I toggled that setting I would be able to access my shares by \\IP_address .

After some time today I’ve tweaked a number of Windows 10 settings and when I try to access \\192.168.1.2\Images from my Windows 10 laptop I just get a message saying “The specified server cannot perform the request operation.”

I’m guessing that’s not exactly true - Windows 10 is pointing the finger of ‘blame’ at the NAS, but I can prove it certainly can perform that operation, just on other Windows versions - it’s Windows 10 where it doesn’t like it.

My MyCloud has always had a static IP address of 192.168.1.2 and the Images share has “Public Access” turned on in the. Current position I’m in is where I have Get-SmbServerConfiguration | Select EnableSMB2Protocol and Get-SmbServerConfiguration | Select EnableSMB1Protocol both returning true in Powershell. Turn on Network Discovery is checked in the Private (current) profile in Advanced Sharing Settings. Enable NetBIOS Over TCP/IP is checked on the Wireless connection itself. I have even gone into gpedit.msc and enabled the option to Enable insecure guest logons .

I can see the MyCloud in Network - with its name WD2TB - it’s both in Media Devices and in Storage , but I cannot get it to do anything when I right-click and do Open from the Storage icon. I still get the same error when trying to access \\192.168.1.2\Images from Start - Run .

I can happily ping 192.168.1.2 - no problem with reaching it from this specific laptop (obviously I can get to it via the browser too). The Music Library for Sonos is also stored here, and Sonos is working just fine - this is a Windows 10 thing pure and simple, but I can’t see the wood for the trees now, I think.

Can anyone provide any advice and guidance on this, please? Or ask me any clarification questions which I will respond to. Firmware of the MyCloud is said to be WDMyCloud v04.04.05-101 : Core F/W .

Thanks, Hippo

P.S. - these WD instructions seemed to be related to what I wanted - How to Map a WD Network Drive on Windows 10 and Windows 11 - so I worked through - in step 4 I do see my NAS under Storage, but in step 5 when I enter \\192.168.1.2 I get the error message Windows cannot access 192.168.1.2 with error code 0x80004005… I am not prompted for a username and password as step 5 implies I should be.

2

Not sure if this will help. I have never used the start run with an ip address. So I tried to use the start run to access my router. with a single slash or a double slash it just brings up a google search for the ip address. When I tried the single slash in the browser it also brought up the google search. But if I used two slashes it opened up the router page.

3

Good morning,

First, thanks for replying - but the single \ is a thing I should’ve spotted - it’s just this Community post that is [mis-]representing what I typed - to be 100% clear - I am typing \\192.168.1.2\Images and have done so for years on Windows XP and Windows 7 machines. The new variable here is Windows 10.

I haven’t made any changes to the NAS itself, or the rest of the things on my home network - the only addition is this Windows 10 laptop, which will not connect in a similar way as all other PCs (and phones and tablets and, I guess, Sonos) will.

I’ll try to edit my post so it shows double-backslashes… (I’ve managed this now). You can try using double-slashes and IP address from Start - Run too, I’m sure… I’d hope it would open a share for you, depending on what OS you’re running, maybe.

4

I mean… if it just provided some idea of what was going wrong, and where, that would be helpful. I’ve only got this far - nowhere - by Googling. :wink: It’s basically in the mode of not working and not telling me anything about why.

Even when it presents an ‘error’ - the text accompanying it is unspecified error… I mean why bother???

I am not blaming the WD MyCloud - I am 100% positive this is all Windows 10.

5

After reading up that this kind of failure could be related to some Windows 10 changes disabling SMB 1.0 I thought that was definitely relevant.

But I just ran sc qc lanmanworkstation on my Windows 7 PC (which definitely can access the share at \192.168.1.2\Images - I’ve just done it again to prove it :wink: beyond a shadow of a doubt) and it shows the same output as on Windows 10, that being:

DEPENDENCIES       : Bowser
                           : MRxSmb20
                           : NSI

My understanding is that this means SMB 1.0 is not enabled on the Windows 7 PC anyway, and that can access the MyCloud share. Therefore the Windows 7 and Windows 10 PCs are the same in this regard (I’ve not checked Windows XP - I’m going to assume it’ll be SMB 1.0 for obvious age reasons).

On Windows 10 running: Get-SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol returns true, true - but running the following in an elevated Command Prompt on both Windows 7 (can access the share) and Windows 10 (can’t access the share) shows:

sc query mrxsmb10 returns STOPPED
sc query mrxsmb20 returns RUNNING

So surely that’s enough to prove this isn’t SMB 1.0 related?

6

More as an act of desperation, really, I checked the Windows Defender setup - I can see that File and Printer Sharing (SMB-Out) for Private (active network profile) is set to Allow the connection (predefined rule anyway it says) - same for SMB-In ;-). In any event, I also tried to completely disable Windows Defender for a few moments.

I get the same error when trying to access \\192.168.1.2\Images. Hopefully firewall issues ruled-out.

7

If one hasn’t done so already they can re-enable SMB1/CIFS support in Windows 10 if Microsoft has disabled it. WD has a Knowledgebase article covering this issue.

How to Enable SMB 1.0/CIFS File Sharing Support on Windows 10
https://support-en.wd.com/app/answers/detail/a_id/4155

8

Yes, I’ve already done that.

9

I have been running Wireshark on both the Windows 10 (doesn’t work) and Windows 7 (works) laptops, on both I have just gone to the NAS with Start - Run - \\192.168.1.2 - nothing more - just hit return and on the Windows 7 PC the NAS opens up in an Explorer window and on Windows 10 I get the error message. At no point is any username or password asked for or supplied by either.

There was a difference between the 2 traces…

  • In packet 6 I see my IP address send a SMB2 Negotiate Protocol Request to the NAS.
  • In packet 8 the NAS responds with a Negotiate Protocol Response saying Dialect: SMB2 wildcard (0x02ff).
  • That means another SMB2 Negotiate Protocol Request needs sending and that happens in packet 9 and in packet 10 the NAS responds with Dialect: SMB 2.1 (0x0210).
  • In packet 11 the client PC sends its first Session Setup Request, Security mode: 0x01, Signing enabled.
  • Packet 12 the NAS responds with a SMB2 Packet Header - SYNC (ProtocolId: 0xfe534d42), and it has NT Status: STATUS_MORE_PROCESSING_REQUIRED - it indicates this is an error, but it’s exactly the same on both PCs.
  • The client PCs both then send a SMB2 Session Setup Request, NTLMSSP_AUTH, this is where the difference is:

On the Windows 10 PC this is \ - which ends up being User name: NULL inside Security Blob.

On the Windows 7 PC this is <PCName>\<UserName> - which ends up populating Domain Name:, User Name: and Host name: in the Security Blob.

Both PCs then receive a Session Setup Response with STATUS_SUCCESS and Session Flags: 0x0003 which means Guest = true, Null = true and Ecrypt = false… so they’re the same here - but Window 7 goes on to do a Tree Connect Request for \\192.168.1.2\IPC$ and open the share in a Window and Windows 10 goes back to Negotiate Protocol Request (and then seems to do this possibly up to 30 times) before it aborts.

So I started to figure out it must be to do with a Domain and Username (not password) being needed. I went into Credential Manager and added a new Windows Credential for 192.168.1.2, for this I just put in the output of hostname.exe followed by \ and my username (although I just tested it with blah\blah too - and, yeah, I can confirm it still worked! - and I left the password blank.

Hitting \\192.168.1.2 from Start - Run opens the share.

1 Like
10

private network / public network

11

Thank you, Thank you, Thank you!