SMB shearing issue

[James_Darkness]

hi, I enabled SMB but none of my pc can access/see the Nas. I changed a few settings and got one of my PC's to see/access the NAS (Mary-PC)  to see it NAS but none of my other PC's could. I then restarted the Nas and now none of my computers can see the NASexpect my brother's MacBook but that doesn't use SMB. since I'm using a server I didn't know if it could be a bios setting that's turned on for security reasons but I did clear the CMOS before installing unraid

[James_Darkness]

here are some of the setting I had

[rootshare]
path = /mnt/user/Media
comment =
browseable = yes
valid users = ed
write list = ed
vfs objects =
[global]
domain master = yes
preferred master = yes
os level = 255
ntlm auth = yes
NTLMv2 auth = yesv

[Frank1940]

13 minutes ago, James_Darkness said:

[rootshare]
path = /mnt/user/Media
comment =
browseable = yes
valid users = ed
write list = ed
vfs objects =

 

Why did you add this?  Access by root to shares is not allowed in unRAID for security reasons.  I would even question at this time these two additions:

 

ntlm auth = yes
NTLMv2 auth = yesv

Plus the "yesv" should not be there....

 

To begin to resolve your problems, let's move forward in baby steps.  First, go through this thread:

 

        https://lime-technology.com/forums/topic/53172-windows-issues-with-unraid/

 

 

It has enabled a lot of folks to fix SMB problems.  Pay particular attention to the sections on determine which computer on your network in the Local Master.  You really want your unRAID server to become the Local Master.  It does require that your server be on 24-7 but it solves a lot of issues that folks have with SMB. 

 

Second, don't try to secure shares until you can get public access of the files on the server working.  

 

Third, if you are still having problems, tell us what version of Windows, you are using.  And post up your Diagnostics file:

 

  Tools   >>>>  Diagnostics    

 

[James_Darkness]

27 minutes ago, Frank1940 said:

 

Why did you add this?  Access by root to shares is not allowed in unRAID for security reasons.  I would even question at this time these two additions:

 

ntlm auth = yes
NTLMv2 auth = yesv

Plus the "yesv" should not be there....

 

To begin to resolve your problems, let's move forward in baby steps.  First, go through this thread:

 

        https://lime-technology.com/forums/topic/53172-windows-issues-with-unraid/

 

 

It has enabled a lot of folks to fix SMB problems.  Pay particular attention to the sections on determine which computer on your network in the Local Master.  You really want your unRAID server to become the Local Master.  It does require that your server be on 24-7 but it solves a lot of issues that folks have with SMB. 

 

Second, don't try to secure shares until you can get public access of the files on the server working.  

 

Third, if you are still having problems, tell us what version of Windows, you are using.  And post up your Diagnostics file:

 

  Tools   >>>>  Diagnostics    

 

I saw the  [rootshare] in another post and thought it might help 

 

NTLMv2 auth = yesv 

the v was just a typo when I did control-v 

 

tomorrow ill try to shut down every computer using SMB.  Then restart my server and after about ten minutes start to add back in your computers slowly one at a time. 

 

                      thank you

[pwm]

 

9 hours ago, Frank1940 said:

Access by root to shares is not allowed in unRAID for security reasons.

 

[rootshare] doesn't mean user root. It's just the name the share gets exported as - while the share internally is "Media".

The main open question is mostly why calling the share "rootshare" instead of making use of the 

 

And "valid users = ed" also indicates that the share isn't giving access to user root but to user "ed".

[James_Darkness]

8 hours ago, pwm said:

 

[rootshare] doesn't mean user root. It's just the name the share gets exported as - while the share internally is "Media".

The main open question is mostly why calling the share "rootshare" instead of making use of the 

 

And "valid users = ed" also indicates that the share isn't giving access to user root but to user "ed".

1

currently, i have no setting. but the setting I posted were just a mix of some setting that other people posted to fix their smb issues 

 

also, i have a Plex server running which I can see and play/copy the files from just cant upload.

[James_Darkness]

20 hours ago, Frank1940 said:

 

Why did you add this?  Access by root to shares is not allowed in unRAID for security reasons.  I would even question at this time these two additions:

 

ntlm auth = yes
NTLMv2 auth = yesv

Plus the "yesv" should not be there....

 

To begin to resolve your problems, let's move forward in baby steps.  First, go through this thread:

 

        https://lime-technology.com/forums/topic/53172-windows-issues-with-unraid/

 

 

It has enabled a lot of folks to fix SMB problems.  Pay particular attention to the sections on determine which computer on your network in the Local Master.  You really want your unRAID server to become the Local Master.  It does require that your server be on 24-7 but it solves a lot of issues that folks have with SMB. 

 

Second, don't try to secure shares until you can get public access of the files on the server working.  

 

Third, if you are still having problems, tell us what version of Windows, you are using.  And post up your Diagnostics file:

 

  Tools   >>>>  Diagnostics    

 

5

ok I only had my unraidnas and my computer connected to the router and I still didn't see my NAS in my network. I even tried booting unraid into safe mode. also, the unraidnas has always been local master I think I changed the setting once 

[global]
domain master = yes
preferred master = yes
os level = 255

to marry-pc and that was the only way I had file access just only from that pc 

all my PC's run windows 10. the one I'm using runs windows 10 pro 64 bit. but i do have VMware Workstation Pro with a lot of different os' i can test with

unraidnas-diagnostics-20180224-1431 (1).zip

[Frank1940]

Windows 10 has been a real bear with regard to SMB.  And it is not helping that besides the named releases (Home, Pro, etc) that are also the numbered release versions (1709, 1703, etc) and all of them are a bit different when it comes to SMB and security.  It seems that what works with one combination does not work with another one!   

 

Using Windows explorer (the File manager),  in the box to the left of the Search Box, enter    \\192.168.1.75      and see what you get.  

 

If that does work, install the 'Local Master' plugin (it is referenced in the first post of the "Windows issues with unRAID" thread) and see if your server is really the Local Master.  If it is, you will next want to see what computer your Windows10 machine thinks is the Local Master.  There is an utility that you can run on your Windows computer that will provide with information about your current networking configuration from that computer's viewpoint.  It is called LANscan and you can find it by googling 'Scottie's LANscanner v1.68'.  I know that many folks are reluctant to download programs from the Internet and you may want to do a bit of resource first.  (I would definitely get it directly from Scottie's website and make sure that you scan it for any bad stuff.)

 

Here is one more item to be check out with Windows10 computers:

 

       https://support.microsoft.com/en-us/help/4046019/guest-access-smb2-disabled-by-default-in-windows-10-server-2016

 

 

[James_Darkness]

31 minutes ago, Frank1940 said:

Windows 10 has been a real bear with regard to SMB.  And it is not helping that besides the named releases (Home, Pro, etc) that are also the numbered release versions (1709, 1703, etc) and all of them are a bit different when it comes to SMB and security.  It seems that what works with one combination does not work with another one!   

 

Using Windows explorer (the File manager),  in the box to the left of the Search Box, enter    \\192.168.1.75      and see what you get.  

 

If that does work, install the 'Local Master' plugin (it is referenced in the first post of the "Windows issues with unRAID" thread) and see if your server is really the Local Master.  If it is, you will next want to see what computer your Windows10 machine thinks is the Local Master.  There is an utility that you can run on your Windows computer that will provide with information about your current networking configuration from that computer's viewpoint.  It is called LANscan and you can find it by googling 'Scottie's LANscanner v1.68'.  I know that many folks are reluctant to download programs from the Internet and you may want to do a bit of resource first.  (I would definitely get it directly from Scottie's website and make sure that you scan it for any bad stuff.)

 

Here is one more item to be check out with Windows10 computers:

 

       https://support.microsoft.com/en-us/help/4046019/guest-access-smb2-disabled-by-default-in-windows-10-server-2016

 

OMG CAN I HUG YOU 

 The //198.168.1.75 worked

[Frank1940]

Quote

 

OMG CAN I HUG YOU 

 The //198.168.1.75 worked

 

 

Good to hear.  Just remember that in the Windows Explorer it should be   \\198.162.1.75      (Note the back slashes!)  to see your shares.   The forward slashes    //198.168.1.75     are used in your browser and should bring up the GUI.   Folks often miss fail to notice the difference and then find that things don't work...

 

[James_Darkness]

14 minutes ago, Frank1940 said:

 

Good to hear.  Just remember that in the Windows Explorer it should be   \\198.162.1.75      (Note the back slashes!)  to see your shares.   The forward slashes    //198.168.1.75     are used in your browser and should bring up the GUI.   Folks often miss fail to notice the difference and then find that things don't work...

 

yeah, it was just a typo since I was on my phone, again I can't thank you enough.

 

kind of a side question but I have a few files on the server but I need a different HBA since I'm using 4tb which my current HBA doesn't support so there 2.2tb. so my side question is when I upgrade my HBA will the data be lost/or will I need to rebuild the array. the data isn't moved just copied to the NAS so its nothing important

[Frank1940]

Normally, installing a new HBA will be transparent as unRAID 'remembers' disk assignment by the serial number of the drive.  However, there are a very few HBA's which 'fool around' with the reporting of the serial numbers.  It is best to print out a copy of the disk assignments (using the Main tab) and have it handy.  (As with all Murphy's Laws, "proper prior prevention prevents problems".)  You will probably not need it.  

 

As a further note if you are using single parity, if you know which are the parity and cache disks, the data disk disks can be arbitrarily assigned to any disk slot and parity will be preserved. 

[itimpi]

4 hours ago, James_Darkness said:

kind of a side question but I have a few files on the server but I need a different HBA since I'm using 4tb which my current HBA doesn't support so there 2.2tb. so my side question is when I upgrade my HBA will the data be lost/or will I need to rebuild the array. the data isn't moved just copied to the NAS so its nothing important

If your new HBA reports a different size to the disks (which it sounds as if it should in your case) then it will think your 4TB disks are new disks.