Look at Dusty Harpers post on Nov. 21.
DoItJust, the WD MyClouds have been headaches for a lot of people. I use a Lenovo ix2-4 and have no problems with it.
Using Static IP's and Host names isn't a sensible answer -- too much maintenance etc.
Netbios simply works.
On Windows though some people report that one of the ports that used to be used in searching / retrieving data from the LAN should be disabled -- I can't remember if it was 445 or another one. This trick worked in earlier releases of W10 but AFAIK it isn't needed any more.
I used also to have a problem when accessing WINDOWS FROM LINUX is that even if you shared the whole "C" drive most of the "C" directory wasn't shown and not all files were listed.
Seems to work 100% these days.
It could be the versions of Linux you are using. CENTOS is based on RED HAT ENTERPRISE which is extremely widely used for networking so I'd expect CENTOS to work perfectly as a server (which it does).
Other distros which aren't based on existing commercial servers might not work so well -- you have to search the various 'Nix forums.
OPENSUSE might be another good one to try as it's also based on a commercial server too.
I'm actually quite surprised to find networking seems to be working as it should be in this release of Windows --must be a First for ms this time as windows networking has always been a dog ever since Windows first started using it !!.
Jimbo anything like printers, NAS, etc, get a Static IP on my network. Everything else gets a Dynamic IP.
Four questions I really would like you guys who understand this give an anser to:
Why does it work in 10240 but not in 10586, a bug or a setting changed?
Why can I see my Nas when the air pressure is the right one? (I.e. sometimes)
What about my Mac, are Mac's also being a headache for a lot of people?
Best thing to do, continue looking for solution for 10586, wait for a MS fix or stay on 10240 forever?
I have not had any issues with 10586 on my wife's laptop. The samba config I use, works just fine with no issues.
Very interesting thread. I myself have struggled with this issue for far to long. I believe the problem lies in Widows File Explorer view. I have been able to discover a workaround for at least my problem of not being able to browse to Linux Samba shares and truly it is only a workaround but it is simple enough for the average user to perform to get things useable in File Explorer.
A little background to the issue seems appropriate here so here goes. I have a total of 5 Win 10 installs at this time. I was in on the Insider program during the Win 10 development stage. I had no problem with preview builds of Win 10 prior to 10586 like many if not all others here. After the upgrade to 10586 as has been discussed here in great detail browsing to a Samba share became impossible. I still participate in the Insider program but I am on the slow track so have not upgraded yet to the latest build so I cannot say at this time if the issue being discussed here has been fixed or not.
Shortly after the release of Win 10 I upgraded 3 machines to Win 10, all Home versions and immediately noticed that it was now possible to browse my Samba server with File Explorer without issue. I was pleased to see this and figured problem solved. I still had the issue on my Insider install but did not think much of it as I had gotten so use to just typing in the server/share name to gain access it became second nature to do so. Over the holidays I embarked on a new machine build on which I installed the PRO version of Win 10 and immediately discovered that this install had the same issue of not being able to browse Samba shares. After way to much trial and error I finally found a way to work around the issue.
To have File Explorer display a Samba server and be able to browse the shares apply the following tweaks to File Explorer
Open File Explorer and click on the View tab. Now click on the Options and select Change folder and search options. From the resulting window in the Open File Explorer to field select This PC and click Apply. This will invoke a more familiar Win 7 style view in Explorer but you must close and reopen Explorer to see the results.
With a newly opened Explorer window click to select This PC in the menu in the left pane. Right click for a context menu and select Add a Network Location. This will start a Wizard to create a shortcut for a network location in File Explorer. Select Next and select Choose a custom network location then click Next. Now enter your servername/share or IP address to the share you wish to access (Example: //server/sharename). Click Next and enter a name for the short cut you are about to create and click Next. The wizard will now create a shortcut in the left menu with the name you chose and an icon will appear under Network showing your Samba server as an essentially Other Network Device.
I have a network with 4 notebooks, 3 android mobiles, 2 WD external ethernet hard drive, 1 WDTV Live. After upgrade to Windows 10, when I click to "Network" (On Windows Explorer left panel), I can not see nothing. The computer can not see even itself. I have been searching in foruns and a lot of people are talking about this Windows 10 bug. I have tryed to configure the network using the router (DLink dir635) and the modem Humax. Nothing. The curious is: I have 3 notebooks with Windows 10. If I turn them all off and turn off the router, after turn on again, the first computer the see the shares, but the others can not. Other people talk in foruns about this problem. My problem is not only makes Windows 10 see My Cloud and My Book Live, but get back my home network Windows 10 get way. In the beginning, I thought the problem was with the Windows 10 version. I have one notebook Windows 10 (10240) that work perfectly well and two notebooks with Windows 10 (1511) that did not. After, I discover that, as I do not turn them off, the diference was not the Windows 10 version, but the fact the notebook with Windows 10 (10240) was the first turned on in the network. As I explained before, when I turn them all off, if I turn one notebook with Windows 10 (1511) [November Update] it will work perfectly well, but only the first turned on.