[opensuse] Can't access Windows 10 shares
One thing I've noticed is I can no longer access Windows 10 file shares, since updating to Windows 10. Even though they're visible on other Windows computers, I cannot see them under SMB shares. Any ideas on how to fix them. I suspect MS deliberately broke this. ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thursday, 15 September 2016 3:29:50 PM ACST James Knott wrote:
One thing I've noticed is I can no longer access Windows 10 file shares, since updating to Windows 10. Even though they're visible on other Windows computers, I cannot see them under SMB shares. Any ideas on how to fix them. I suspect MS deliberately broke this. ;-)
What version of openSuSE are you running? How are you trying to access the Win10 shares? What permissions do you have set on the shares? What about the Windows firewall? Exactly what happens when you try to access a share e.g. by typing the UNC name into the location bar on Dolphin? Do you get prompted for a username/ password? Much of the historical backwards compatibility with smb/cifs networks seems to have gone with Windows 10; for example, it no longer works logging onto an NT4-style domain (using Samba as PDC). It pretty much requires AD, which means a properly configured LDAP setup if you want to use Samba as the AD server, or a Windows server to serve the AD shares. I have oS Leap 42.1 talking seamlessly to an AD network at work, which worked out of the box with no additional setup needed for browsing and accessing network shares, but not doing domain logons. I do have other boxes doing domain logons, but they're running Debian (it will work with openSuSE but I just haven't needed to). Regards, Rodney. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/15/2016 07:42 PM, Rodney Baker wrote:
On Thursday, 15 September 2016 3:29:50 PM ACST James Knott wrote:
One thing I've noticed is I can no longer access Windows 10 file shares, since updating to Windows 10. Even though they're visible on other Windows computers, I cannot see them under SMB shares. Any ideas on how to fix them. I suspect MS deliberately broke this. ;-) What version of openSuSE are you running? How are you trying to access the Win10 shares? What permissions do you have set on the shares? What about the Windows firewall?
openSUSE 13.1. I previously was able to access shares, but a recent W10 update apparently killed that. I have tried turning off the W10 firewall but no difference.
Exactly what happens when you try to access a share e.g. by typing the UNC name into the location bar on Dolphin? Do you get prompted for a username/ password?
I see nothing.
Much of the historical backwards compatibility with smb/cifs networks seems to have gone with Windows 10; for example, it no longer works logging onto an NT4-style domain (using Samba as PDC). It pretty much requires AD, which means a properly configured LDAP setup if you want to use Samba as the AD server, or a Windows server to serve the AD shares. I have oS Leap 42.1 talking seamlessly to an AD network at work, which worked out of the box with no additional setup needed for browsing and accessing network shares, but not doing domain logons. I do have other boxes doing domain logons, but they're running Debian (it will work with openSuSE but I just haven't needed to).
This is at home, so no AD. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Rodney Baker wrote:
On Thursday, 15 September 2016 3:29:50 PM ACST James Knott wrote:
One thing I've noticed is I can no longer access Windows 10 file shares, since updating to Windows 10. Even though they're visible on other Windows computers, I cannot see them under SMB shares. Any ideas on how to fix them. I suspect MS deliberately broke this. ;-)
I wouldn't doubt it... They did with desktop search in Win7 and refused to backdown with any fix. You want search results from your home NAS? It better be running a MS-server OS...
Much of the historical backwards compatibility with smb/cifs networks seems to have gone with Windows 10; for example, it no longer works logging onto an NT4-style domain (using Samba as PDC).
Has anyone tried running Samba under Cygwin on Win10? Seems like you could have a Win10 home-edition functioning as a AD-server -- theoretically, that is... Rather than Ms creating more incompatibility w/samba in an attempt to marginalize samba, they could conceivably create the opposite effect. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
James Knott
-
Linda Walsh
-
Rodney Baker