I just reinstalled after I was having issues. Everything seems to be working smoothly, except that I can't access the shares on all but one of my other computers for some reason. Most devices that aren't running either some flavor of Windows or Samba show up just fine.
I tried blocking port 139 and made sure Network file and printer sharing is on, and a few other things, but I'm out of ideas.
Thanks in advance.
Hi there
I have NO issues now with SAMBA on build 10049 -- before the "C" drive was only showing SOME files - now the whole drive / shares are visible. Works FROM SAMBA ===> WINDOWS and from WINDOWS ==>SAMBA. No problem either with WIN 10 ==>WIN7 and XP and from XP / WIN 7 ==>W10. I don't have W8.1 any more.
Running CENTOS 7 (64 bit) SAMBA version 4.1.12-21. If you use YUM there's a great GUI -- YUM-EXTENDER - makes updating a synch. Other distros -- not sure maybe some type of apt-get.
Try updating your system / distro with relevant updates.
Cheers
jimbo
Huh, interesting. Both systems are completely updated, and I'm able to see the Samba shares from other devices on my network.
It appears that I'm running Samba 3.6, and the current version is 4.2 so It's possible this issue has been fixed in between. I'll try reinstalling Samba later today and see what happens.
EDIT: I was eventually able to connect manually by ip address despite not getting to connect by name, which suggests some sort of issue with DNS. But in 10049 I can't change network adapter settings so I can't know for sure at the moment.
I'll leave this here in case someone else has a similar problem.
May find help here.............I just reinstalled after I was having issues. Everything seems to be working smoothly, except that I can't access the shares on all but one of my other computers for some reason. Most devices that aren't running either some flavor of Windows or Samba show up just fine.
I tried blocking port 139 and made sure Network file and printer sharing is on, and a few other things, but I'm out of ideas.
Thanks in advance.
I've edited the page to connect another device to a home network down to a "sorta" checklist page. After editing it's 7KB zipped and I'd be glad to email it to anyone that wants it but I don't know how............ never tried it
Huh, interesting. Both systems are completely updated, and I'm able to see the Samba shares from other devices on my network.
It appears that I'm running Samba 3.6, and the current version is 4.2 so It's possible this issue has been fixed in between. I'll try reinstalling Samba later today and see what happens.
EDIT: I was eventually able to connect manually by ip address despite not getting to connect by name, which suggests some sort of issue with DNS. But in 10049 I can't change network adapter settings so I can't know for sure at the moment.
I'll leave this here in case someone else has a similar problem.
Build 10049 -- known problem and acknowledged by Ms -- WIRED (Ethernet) adapter settings can't be changed -- bit of a bummer if you need to change Ethernet settings.
Will be fixed in next release. You could test with a USB Wifi (wireless) adapter of course. Not as good a s a LAN but better than nothing just to see if connectivity works.
Cheers
jimbo
Networking with 10041 and 10049 is somehow messed up and is a hit or miss.
Although manual connection works by using IP addresses but auto detect isn't working.
Same problem with clean install of 10051 but I am not gonna bother with it too much because it's not an official release.
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.
It IS a 1511 version problem. The reason your turn on sequence sees the first come right is that the first one turned on becomes the master browser and the master browser does not have the discovery problem.
