Forums

Resolved
2 votes
I was having issues connecting to my ClearOS7 Samba 4 after upgrading to Windows 10 Home from Windows 7 Home. I could ping the server, I got a correct response from "nbtstat -A x.x.x.x", and Angry IP scanner saw the server fine still, but no shares were accessible. Immediately after upgrading I could no longer use the same script I was using to connect when the system was Windows 7. I worked through a plethora of other possibilities of what it could be, network drivers and properties, firewall, etc, and just in case those made some difference, I thought I'd list the major ones here, #4 fixed everything for me except the slow reveal of the mappings showing, at times, in Computer. What I'm saying is "net use" in a command prompt would show they were mapped immediately, but they were not visible in Computer for some time occasionally.

1.) Turn on File and Printer Sharing for network discovery under Advanced Sharing Settings for the Profile being used and the Network, as it's disabled by default. Turn your Network Location to the appropriate setting, for "Home" use it's now called "Private". It might be locked down a bit by being set to Public.
Network Location - Set to Private or Public in Windows 10 - http://www.tenforums.com/tutorials/6815-network-location-set-private-public-windows-10-a.html

2.) A website suggested running this with Powershell helped login issues. "We have found it necessary to fix a multitude of network share mapping issues with Winblowz 2008 R2 and above and older CIFS/SMB file sharing devices:" Ran with elevated Privileges in PowerShell: Set-ItemProperty -Path “HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters” RequireSecureNegotiate -Value 0 -Force
https://lime-technology.com/forum/index.php?topic=41590.0
https://support.microsoft.com/en-us/kb/2686098


3.) Add the most popular registry entry for network errors if you are experiencing "\\something is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The account is not authorized to log in from this station." This allows you to re-enable the guest access to remote shared folders and network locations in Windows 10.
HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters AllowInsecureGuestAuth DWORD(32-bit) 1
Linux and Windows 8 Interoperability - http://www.dedoimedo.com/computers/windows-10-network-share-access.html

4.)This was my final and only addition that made any real difference. I will list both sources as one gave me the other. KB2696547 was the fix that I needed and this entry "Windows 10 will try to negotiate SMB3_11, which Samba4 doesn't yet support except in the current 4.3 release candidate. I suspect for now disabling SMB2/3 on the Windows 10 client is your best, if not ideal, option." from the Ubuntu forums clinched it for me as being the issue. The Windows 10 Home client was just giving up after trying SMBv3. I didn't even see anything in the logs on the server side showing it was failing looking at /var/log/samba.
•To disable SMBv2 and SMBv3 on the SMB client, run the following commands:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled
Re: Cannot connect to Samba share (4.1.11) from Windows 10 - http://ubuntuforums.org/showthread.php?t=2293617
How to enable and disable SMBv1, SMBv2, and SMBv3 in Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012 - https://support.microsoft.com/en-us/kb/2696547


5.) Of course I already had the Windows 7 settings for ClearOS in my registry, but I didn't want to just glaze past that without mentioning it as well for new folks. HKLM\System\CCS\Services\LanmanWorkstation\Parameters DWORD DomainCompatibilityMode = 1 DWORD DNSNameResolutionRequired = 0
https://www.clearos.com/resources/documentation/clearos/content:en_us:5_windows_settings

6.) Many sites make mention as well of using authentication to shares by using IPADDRESS\username (as a poor example, replace IPADDRESS with appropriate IP like 10.0.0.1 or servername) followed with password. Turn off checkmark to Hide Empty Drives as well in the Folder Options / View settings. And it seems that using Credential Manager is going to become more important in the very near future. Hope this helps someone looking for quick advice and fosters continued interest in ClearOS 7.
Tuesday, September 15 2015, 12:40 AM
Like
2
Share this post:
Responses (5)
  • Accepted Answer

    Friday, April 01 2016, 04:18 PM - #Permalink
    Resolved
    0 votes
    If I'm correct this post continues in a other THREAD

    Also moved this post to the correct subforum.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 01 2016, 12:39 AM - #Permalink
    Resolved
    0 votes
    I saw a similar issue and what I found was that when the system was upgraded that they used the same smb.conf file from a previous version and that conf file had a restriction to only use 'port 139' for samba. This means that other typical ports related to CIFS was disabled and Windows 10 recently dropped support for SMB2 (which runs on 139). So check that as well.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 01 2016, 12:37 AM - #Permalink
    Resolved
    0 votes
    I have implemented all of the above and am still unable to connect :(
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, March 31 2016, 03:58 PM - #Permalink
    Resolved
    0 votes
    Thank you for sharing this with ClearOS community. :)
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, March 31 2016, 11:01 AM - #Permalink
    Resolved
    0 votes
    Thank you for this comprehensive list. Hopefully this will help me solve my connection issues :)
    The reply is currently minimized Show
Your Reply