Page 1 of 1

Cannot access NAS4Free from Windows 10 after 1803 upgrade

Posted: 16 May 2018 11:40
by Floh
Hi, I am running NAS4Free embedded ( 11.0.0.4 - Sayyadina (revision 3330)) and have some HPTCs running Linux and a couple of Windows machines.
The servers seems to be running fine and I can play movies and TV shows from my Kodi machines, but I no longer have access to my mounted network drive on my Windows machines. I have two NAS4Free machines, a main and a backup, and both have this problem with connecting from Windows.

The windows error message roughly translates to "Network error: You have no permission to access (IP\mnt\sharedfolder). Ask your network administrator for access". All of my windows PCs have this problem. I have tried some workarounds such as allowing SMB v1 in Windows, but it has not helped. I can mount the drive using the IP and mount point I defined, but I cannot see any content.

- Is there a chance that an upgrade to a newer version of NAS4Free would help solve this?
- Would setting a max and min protocol help (currently set to default)?
- Can I enable another protocol that is more Windows 10 friendly? I am currently running NFS and CIFS/SMB.

My configuration looks like this: Image

Re: Cannot access NAS4Free from Windows 10 after 1803 upgrade

Posted: 16 May 2018 13:59
by Floh
Quick Update: I just installed the newest version (11.1.0.4 rev 5565) of NAS4Free on my backup server, and I can access the backup server from Windows 10...

BUT ONLY IF NFS IS ENABLED

The same thing does not work on 11.0.0.4 - Sayyadina (revision 3330)

Re: Cannot access NAS4Free from Windows 10 after 1803 upgrade

Posted: 16 May 2018 14:24
by raulfg3
Please play with server max & min protocol to adapt to your windows needs.

PD: I use SMB3 for example.
1.jpg

Re: Cannot access NAS4Free from Windows 10 after 1803 upgrade

Posted: 16 May 2018 21:43
by Floh
Thanks for your help. I did fiddle around with every possible setting but it does not work.
Since the newest version seems to allow access from Windows again, I will update my main server.
First item of business though is backing everything up. Going to use rsync between the two systems.

Re: Cannot access NAS4Free from Windows 10 after 1803 upgrade

Posted: 16 May 2018 22:59
by raulfg3
revise your folder owner, must be your local user, and this local user must be the user used to login whith windows.

Re: Cannot access NAS4Free from Windows 10 after 1803 upgrade

Posted: 17 May 2018 00:34
by Floh
I've set up users on both NAS4Free systems with the same name as my Windows user, no how do I change ownership?
Is it chown <user>:<usergroup> <directory> , and would that be recursive (i.e. also for subfolders and files within them)?

Re: Cannot access NAS4Free from Windows 10 after 1803 upgrade

Posted: 17 May 2018 07:31
by raulfg3
yes, chown.


PD: I use winSCP that have a webGUI for that , but chown is the shell command.

Re: Cannot access NAS4Free from Windows 10 after 1803 upgrade

Posted: 17 May 2018 09:56
by Floh
Win SCP was a great tip. I installed it, activated ftp service on both servers, and am able to access all my files from there.

Rather than fiddle with the permissions on the files I already backed up for test purposes, I found that I can use Win SCP to directly pull files from my main server to my backup server using wget. However, when I open Win SCP terminal window, it says "do not start commands that require user input or file transfer" so I am a bit worried about doing it that way.

So I have managed to get SSH access working, and will probably run it from there.
Does this syntax
wget --progress=bar --preserve-permissions --mirror ftp://user:password@111.222.333.44:/mnt/path ./
do what I would want, namely to pull a backup from my main server to the backup server, when executed on the backup server?

EDIT I guess wget is not on NAS4Free by default, and the commands to install it do not work... sigh
# make install clean
# pkg_add wget

Re: Cannot access NAS4Free from Windows 10 after 1803 upgrade

Posted: 17 May 2018 13:42
by Floh
Success!!
I set the user permissions using Win SCP and now I can access my files again!

EDIT... No not really... I can access the folders and see the files, but when I try to open them I get "in use by another user, please try again later" and an error message for pictures.
My user permissions are set to the same as my local PC login, and that user is also an admin in NAS4Free.

Re: Cannot access NAS4Free from Windows 10 after 1803 upgrade

Posted: 17 May 2018 17:10
by raulfg3
post your user & group permission for the offending folder to revise please.

eg:
3.jpg

PD: Check your windows side: https://forum.openmediavault.org/index. ... indows-10/

the guide is valid for all unix flavours.

Re: Cannot access NAS4Free from Windows 10 after 1803 upgrade

Posted: 17 May 2018 18:27
by raulfg3
post your user permision like:
2.jpg

and use same user as gest on advanced :
1.jpg

Re: Cannot access NAS4Free from Windows 10 after 1803 upgrade

Posted: 18 May 2018 19:04
by Floh
These are my users. The one on top is the same as my Windows 10 login name.
Image

The permissions and ownerships on the mounted drive as seen from Win SCP are:
Image

Re: Cannot access NAS4Free from Windows 10 after 1803 upgrade

Posted: 18 May 2018 21:00
by Floh
I updated NAS4Free to 11.1.04 rev 5565 and it is still not working. I am not worried, because I can access my files through FTP, so I know they're there and not corrupted, but this is starting to become annoying.
I did what the post on openmediavault said, forced SMB2 protocol, set network to private, added my servers to the hosts file. Problem persists.

Re: Cannot access NAS4Free from Windows 10 after 1803 upgrade

Posted: 19 May 2018 18:15
by Snufkin
Floh wrote:
18 May 2018 21:00
I updated NAS4Free to 11.1.04 rev 5565 and it is still not working. I am not worried, because I can access my files through FTP, so I know they're there and not corrupted, but this is starting to become annoying.
I did what the post on openmediavault said, forced SMB2 protocol, set network to private, added my servers to the hosts file. Problem persists.
Did you check Windows registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa for parameter LmCompatibilityLevel=3?

For unknown reason one of nearby PC (Win 10) got this parameter equal to 1 and failed to connect, but another one (Win 10 too) even missed parameter at all (not defined in Microsoft terms) and succesfully connected.

Actually this parameter could be set in MS Windows Local policy management console and not in registry editor directly.

More about NTLMv2 authentication (default for latest Samba) could be found here

If all above did not help, you could increase Samba log level (what I did), see detailed error description for each event when Windows client - Samba server session starts and post error event here to discuss.

Re: Cannot access NAS4Free from Windows 10 after 1803 upgrade

Posted: 21 May 2018 11:08
by Floh
Thanks. That key did not exist, so I created it as a REG_DWORD and set it to decimal 3.
Did not help.

I also deleted the stored passwords in windows for access to the server and made sure I was re-connecting as my local user to NAS4Free.
My local user is a member of the groups "admin" and "wheel" on NAS4FRee and that user (and the group admin) has all the permissions on that drive.

I also still have a filename encoding problem. I set my character set to CP 850 since I need the German Ä and Ü and whatnot, but the filenames still show up garbled.
When I try to open a jpg the viewing program says "unable to read header".

How can I increase the log level for Samba?

Re: Cannot access NAS4Free from Windows 10 after 1803 upgrade

Posted: 21 May 2018 11:17
by Snufkin
Floh wrote:
21 May 2018 11:08
How can I increase the log level for Samba?
On this page point to Log level drop-down list and choose full or even debug.

Re: Cannot access NAS4Free from Windows 10 after 1803 upgrade

Posted: 21 May 2018 23:19
by Floh
OK so I have made a bit of progress. Due to one thing or another (I've been fiddling with registry and security policies for so long I don't know what did it exactly), I suddenly saw my server appear in my network folder by its actual name. I DO NOT KNOW WHY EXACTLY. Maybe it's the SMB protocol level 2 I forced, maybe it's due to the fact that I wrote it into the hosts file.

So I re-mounted my network drive NOT using the 192.xxx.xxx.yy\mnt\folder but \\SERVERNAME\mnt\folder and there it was again, but this time with the correct character set, and I was able to open files. I was still not able to write to the directories though.

BUT after setting SMB log level to "full", I also noticed that the NAS4Free log had a message saying: permission request for user "office" - no such user. I had named my NAS4Free user Office with a capital O and given that as login credentials in Windows, but it kind of dawned on me that maybe uppercase is ignored in user names... So I created another user with a small o and reset all permissions and ownerships to that user using WinSCP. I was kind of beyond caring at this point.

And BAM!, I have my access back.

Thanks a TON to all you helpful people on this forum. I will be back in other subforums to nag people about backup scripts, and hope it goes just as well.
Topic closed...