I'm a noob with linux system, installed latest Zorin few days ago (17.3 Core).
My NAS is really old and I've few infos about it or I don't know where I can found them except brand and model, Linksys NAS200.
The NAS is used as a common base for all the shared file in my office between the three pcs (1 windows 7; 1 win10 and the Zorin I'm trying now) overall they are .odt .ods and .pdf
All the windows versions work properly.
However I link the NAS in nautilus via "other position" and using FTP protocol (no other will work no afp nor nfs neither smb etc ), then bookmarked it so I have two ways to read and write files in it, by nautilus and with a mounting link on Desktop after I mount it (not a launcher, no way to make it work for now need to do some other tries). Now it appear as: Admin on 192.168.1.7.
After clicking the link button the login mask will appear and I can navigate in the nas directories.
The strange behavoirs are: If I try to upload a file from nas to internet (a mail attachment, a pdf to be shrinked and so on) no way to do it: I must be forced to copy the file on the Zorin desktop and then upload on the net.
Any time I save a Libreoffice file or an exported by Libreoffice pdf or a modified with SAMpdf Zorin say me that a problem occour and fail to safe the file. Dunno if also other programs will generate similar troubles.
Except this I really also need help to configure an automounting launcher that mount the NAS at the system boot
Sorry for my eng, I came from Rome, Italy
Angelo
Welcome to the forum!
Just wanting to figure out some more information, on your windows systems, how are you connecting to the NAS? Through SMB or also through FTP? If they're going through SMB, we would want to get figure out why that wouldn't work on Zorin first before anything else.
Also, I see you mentioned that you're trying to also upload files to the internet. Which websites/locations are you trying to go to? Another thing to check would be if you have the firewall on, to disable it temporarily just to see if some issues go away after that.
Hi, I tried all the configurations in the pop up menu that appear when I clicked on the question mark at the end of the "connect to the server" in the bottom of Nautilus window, only the ftp:// protocol saw the NAS neither the ftps:// did it!!! We usually send .pdf, rarely .odt-.doc, as email attachments (pec.it, Libero.it or Gmail.com) or directly to customer sites or to the sites of Italian state and regional bodies. One of the first things I did was turn off the Firewall, nothing change.
Thanks for helps
What browser are you using to send the email attachments and upload files, and have you tried different browsers?
About the errors that you get when saving files, do they happen with any other type of file e.g. plain text files? What does the error message say exactly?
And lastly, are you able to access the NAS configuration panel? You might be able to enable other file sharing protocols like SMB, which might work better.
About internet:
Same trouble using firefox, Brave, Vivaldi and Yandex. Mail's attachements couldn't be uploaded directly from the NAS i must copy them on my own PC and then upload. I tryed also to modify a pdf on the web in various dedicated sites and a odt file on googledoc (built on with a C&P from an .odt in the NAS opened on my PC and downloaded on the NAS); always the same: the sites can't "pick up" the files from the NAS, only from my own directories. It seems like internet have no permission to touch files in the NAS... But only using Zorin, the other Windows PCs work properly.
About files in the NAS:
I tryied to modify and save an existed .txt file and to create and save a new .txt and all went fine. Modifying and saving a Jpeg and a png file with Pinta, Nautilus went busy and didn't save the image files.
About the NAS conf panel:
I reach it, of course but have no specs about linking protocls. The main menu voices are:
[Status] disk status (like disk name, free space etc)
[Users] users list (2 voices: Admin and guest, one generic guest)
[Shared Folders] Disk 1 and Public Disk 1; and a table with the Admin and Guest permission to R/W
[System Options] with a submenu: [Identification]* [IP Address] [DNS Server] [WINS] [DDNS] [Date & Time] [E-Mail Alert] [Scheduled Shutdown] [Download Manager] [UPnP] [Options]. In no one of those voices are settings to smb-ftp-shh or other protocols except in Options where I can set the Guest permission and if there is a checkbox to Enable the FTP server (port 21 for logged users and if allowed port 80 for anonymous guests). the FTP server is Enabled, the "anonymous FTP Login" not.
The other main menu voices are:
[ - Firmware Upgrade] [Media Server][ Disk Utility] [Disk Configuration] always without smb-ftp-shh-nfs-dav etc...
If needed I can share screenshots.
THX for the time you gift to help me
Angelo
Does this happen even when you drag & drop the files from Nautilus into those sites? Please try with Brave browser for now, since that's the only one guaranteed to be installed using the native Debian package format — that's a whole other conversation, don't worry about it.
It might be an issue with how Nautilus handles transfers using this protocol. If we can't change it, and it seems pretty consistent all around, we could try to go around Nautilus later.
Discovered and partially solved!!!
But still not able to do some other things...
Working for a few hours on some odt I noticed that Nautilus "lost the NAS". Explain what I mean:
I bookmarked the NAS in Nautilus. Every time I turn on the PC and start Zorin I click the bookmark and the NAS administrator login page appears I do the login and can access to the NAS directories. As I wrote at the beginning I have been using Zorin for a few days and I have been in the office for a short periods time by time. Today I had to do more work and I noticed that Nautilus few minutes after the login as admin would not let me access the various directories of the NAS and I was forced to unmount and remount it to work, but Nautilus did not ask me to do login again!!!
I went to the Options page of the System Options Menu and checked the box "Allow anonymous FTP Login ("guest" rights)" and in User entry and in Share folder entry I gave to the guest the same admin privileges. Magic! Now I can upload files to mail, save, modify, move, do everything! I think because Nautilus lost the NAS and therefore when I mount again the NAS it treated me as a guest with restricted privileges and not as an admin with full access.
Now to complete solve I need to know how mount the nas at the boot and fix the Nautilus Lostings!!!
That's pretty weird, but I'll take it 
I think Nautilus may be using a basic implementation of FTP that supports only some operations, or has timeout until it disconnects, or something like that. I've recently seen this with NFS as well.
Anyway, hopefully mounting the remote share directly will fix all the problems. You will need to launch "Terminal" from the application menu, and run a few commands:
-
Install necessary packages:
sudo apt install curlftpfs -
Create a new folder where the remote files will be made available to you. Unlike with the Nautilus approach, you need to create this upfront.
mkdir ~/SharedWe can change this later, let's focus on getting it working first. You could also do this with the graphical interface but for consistency I'll stick with terminal commands.
-
Let's try it if it works by mounting it manually:
curlftpfs -o allow_other <user>:<password>@<remote_host_or_ip> /home/<your_username>/SharedMake sure to replace the placeholders:
<user>and<password>should be the credentials for the FTP server (although if you've allowed access for guests this may not be required),<remote_host_or_ip>should be the IP address or domain name of the remote computer, and<your_username>is your account name.For example:
curlftpfs -o allow_other drake:mypassword123@192.168.1.7 /home/zenzen/Shared
If you don't see any errors after running this last command you should be able to open that "Shared" folder and confirm whether this worked or not.
Also, if you are concerned about typing your username and password over the network: you're right, this is a bad idea. However, just for now, this should do to confirm that things work.
Installed the curl package
modified the fuse.conf file allowing other
angelo@Angelo:~$ curlftpfs -o allow_other admin:admin@192.168.1.7 /home/angelo/Shared
fusermount: option allow_other only allowed if 'user_allow_other' is set in /etc/fuse.conf
angelo@Angelo:~$ curlftpfs -o allow_other admin:admin@192.168.1.7 /home/angelo/Shared
angelo@Angelo:~$
In Nautilus the Shared folder is mounted
Opening Shared folder I can see the two NAS folder: DISK 1 (the only admin security copy) and PUBLIC DISK 1 (the shared files disk)
Both are empty
Mounted the bookmarked NAS in Nautilus, done the login, I entered the NAS and navigate folders and file there but the Shared mounted folders (DISK & PUBLIC DISK) are still empty
I'll try to set it up over the weekend and test it, see what's going on exactly.
If it can help I found the nmap command to "better know" the NAS, this is the output:
angelo@Angelo:~$ sudo nmap -sS -A -dd 192.168.1.7
Starting Nmap 7.80 ( https://nmap.org ) at 2025-04-11 15:05 CEST
Nmap scan report for ufficioserver.station (192.168.1.7)
Host is up (0.00047s latency).
Not shown: 995 closed ports
PORT STATE SERVICE VERSION
21/tcp open ftp Linksys NSLU2 ftpd
21/tcp open ftp syn-ack ttl 64
80/tcp open http thttpd
80/tcp open http syn-ack ttl 64
39/tcp open netbios-ssn syn-ack ttl 64
445/tcp open microsoft-ds syn-ack ttl 64
6789/tcp open ibm-db2-admin syn-ack ttl 64
Final times for host: srtt: 1917 rttvar: 2181 to: 100000
|_http-title: Network Storage System
139/tcp open netbios-ssn Samba smbd 3.X - 4.X (workgroup: WIER)
445/tcp open netbios-ssn Samba smbd 3.X - 4.X (workgroup: WIER)
6789/tcp open upnp Portable SDK for UPnP devices 1.4.3 (Linux 2.6.19; UPnP 1.0)
MAC Address: 00:1D:7E:B6:4E:F9 (Cisco-Linksys)
Device type: general purpose
Running: Linux 2.6.X
OS CPE: cpe:/o:linux:linux_kernel:2.6
OS details: Linux 2.6.9 - 2.6.33
Network Distance: 1 hop
Service Info: OS: Linux; Device: storage-misc; CPE: cpe:/h:linksys:nslu2, cpe:/o:linux:linux_kernel:2.6.19
Host script results:
|_ms-sql-info: ERROR: Script execution failed (use -d to debug)
|_nbstat: NetBIOS name: UFFICIOSERVER, NetBIOS user: , NetBIOS MAC: (unknown)
|smb-os-discovery: ERROR: Script execution failed (use -d to debug)
| smb-security-mode:
| account_used: guest
| authentication_level: user
| challenge_response: supported
| message_signing: disabled (dangerous, but default)
|_smb2-time: Protocol negotiation failed (SMB2)
TRACEROUTE
HOP RTT ADDRESS
1 0.47 ms ufficioserver.station (192.168.1.7)
Read from /usr/bin/../share/nmap: nmap-mac-prefixes nmap-payloads nmap-services.
Nmap done: 1 IP address (1 host up) scanned in 1.42 seconds
Raw packets sent: 1013 (44.556KB) | Rcvd: 1001 (40.048KB)
OS and Service detection performed. Please report any incorrect results at Nmap OS/Service Fingerprint and Correction Submission Page .
Nmap done: 1 IP address (1 host up) scanned in 31.15 seconds
angelo@Angelo:~$
Thanks for sharing that. According to the scan, you should be able to connect via SMB, which I think will work much better than simple FTP.
Try to follow along these instructions instead:
followed all the steps:
trying to install cifs-utils Zorin said back the daemon is just updated no download needed.
LAVORO folder built in home/angelo/Scrivania
modified as root the fstab placing the new string:
//IP/directory /home/angelo/Scrivania/LAVORO cifs credentials=/home/angelo/.smbcredentials,uid=1000,gid=1000,x-systemd.automount 0 0
Create a new text file in /home/angelo named .smbcredentials containing:
username=admin
password=admin
System rebooted
doubleclick on the LAVORO folder on my Desktop
Folder is empty.
If I try to open that folder via Nautilus the answer is:
Impossible to access LAVORO
mount.cifs permission denied
Samba is working (2 services loaded-active-running: nmbd and smbd) if I ask via CLI using systemctl list-units the first row is red and say:
home-angelo-Scrivania-LAVORO.automount LOAD/Loaded ACTIVE/failed SUB/failed
Mounting the NAS with the usual procedure change nothing, LAVORO will stay empty
What if you mount it directly through the terminal?
sudo mount -t cifs //IP/directory /home/angelo/Scrivania/LAVORO -o username=admin,password=admin
Does this work? Also, just to confirm, what is the output of?
id -u
Typically that's 1000, but whatever number appears should be used for the uid and gid options inside /etc/fstab.
angelo@Angelo:~$ sudo mount -t cifs //192.168.1.7/PUBLIC DISK 1 /home/angelo/Scrivania/LAVORO -o username=admin,password=admin
[sudo] password di angelo:
mount: bad usage
Try 'mount --help' for more information.
angelo@Angelo:~$ id -u
1000
angelo@Angelo:~$
With or without the NAS previously mounted the output is the same
Also the guid is 1000.
Surfing on the net I found a lot of troubles and troublesolving about the NAs mounting and try also to modify the fstab with various combinations of this string:
//192.168.1.7/Files/PUBLIC\ DISK\ 1/LAVORO /media/LAVORONAS cifs auto,_netdev,username=admin,password=admin,uid=1000,gid=WIER 0 0
changing gid(1000-root-angelo-Angelo-WIER[according with the nmap data]-nothing); changing the mount source (variations of 192.168.1.7 folders) and mountpoints (in the copied string /media/LAVORONAS) no way 
Seems cifs and samba wish really not to work with this NAS I'm so sorry to involve you for all this time. Thank you so much helping me.
I think the issue might be with the folder name that you're sharing. Spaces don't play well with UNIX-based systems in general, so you might want to rename name "PUBLIC DISK 1" to something like "PUBLIC_DISK_1", instead.
But before you do that, try running the same command but quoting that part:
sudo mount -t cifs "//192.168.1.7/PUBLIC DISK 1" /home/angelo/Scrivania/LAVORO -o username=admin,password=admin
And let's see if that makes any difference.
angelo@Angelo:~$ sudo mount -t cifs "//192.168.1.7/PUBLIC DISK 1" /home/angelo/Scrivania/LAVORO -o username=admin,password=admin
[sudo] password di angelo:
mount error: Server abruptly closed the connection.
This can happen if the server does not support the SMB version you are trying to use.
The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0.
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
angelo@Angelo:~$
Also I read about spaces in directories' names and that is because I posted the previous string with 192.168.1.7/files/PUBLIC\ DISK\ 1/LAVORO. I see this strange (for me) directory name using the systemctl list command
All because I've no way to rename that folder also if logged by admin, except (I think not sure) formatting the disk but is the very last step I wish to do!
Yes, spaces can be quite a pain to deal with. It's best to avoid them if you can, but don't worry we can still work around that.
Luckily, this is giving us a clue. It's possible that the NAS doesn't support SMB at version 2 and higher. Not ideal, but maybe we can get it work by adding that as an option:
sudo mount -t cifs "//192.168.1.7/PUBLIC DISK 1" /home/angelo/Scrivania/LAVORO -o ver=1.0,username=admin,password=admin
the dmesg log said:
...
[62100.992536] netfs: FS-Cache loaded
[62101.097257] Key type cifs.spnego registered
[62101.097288] Key type cifs.idmap registered
[62101.098206] CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount.
[62101.098212] CIFS: Attempting to mount //192.168.1.7/PUBLIC DISK 1
[62101.131258] CIFS: VFS: cifs_mount failed w/return code = -112
[62922.933333] CIFS: Attempting to mount //192.168.1.7/PUBLIC DISK 1
[62922.966455] CIFS: VFS: cifs_mount failed w/return code = -112
...
angelo@Angelo:~$ sudo mount -t cifs "//192.168.1.7/PUBLIC DISK 1" /home/angelo/Scrivania/LAVORO -o ver=1.0,username=admin,password=admin
[sudo] password di angelo:
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
angelo@Angelo:~$
Oops, I think that's supposed to be vers=1.0, with an "s".
sudo mount -t cifs "//192.168.1.7/PUBLIC DISK 1" /home/angelo/Scrivania/LAVORO -o vers=1.0,username=admin,password=admin