Hi there,
New here from Mint. So apologies if I don't know the whole etiquette yet
About 1 month ago I've moved from Win10 to mint and i've managed to set up my Ugreen NAS DXP2800 on Mint. Then out the blue it stopped working.
My phones/ other win10 desktop can still see it but for me is saying is not available.
I was hoping with a move to Zorin this will get fixed, but is the same.
Even when I try to open it on a Brave is still not working.
I can see the name in the Other locations and another External Driver I can access with no issues.
Any ideas?.
Thanks
Welcome to the Forum!
So, the NAS is connected via Network or directly connected to Your PC?
Hi there,
Via Network. Thanks
Anyone ?
You say it was working first on Zorin then at some point not working. True/False?
If true, I am wondering if the dreaded kernel 6.17 update could be responsible.
Have you tried rolling back to 6.14 kernel?
From grub menu:
select "Additional Options for Zorin"
then select a 6.14 kernel generic option that should be listed.
try boot with that kernel and see if any difference.
EDIT: I have now stumbled on this thread. Zorin Not booting after restarting - #7 by AndreiZorin
Can you confirm re-installation has fixed everything here?
2 Likes
Apologies for the delay in my reply.
False, it worked on Mint and then it stopped working.
I've done a switch from Mint to Zorin hoping that would solve the issue, but this is not the case.
EDIT- So even after a 2nd reinstall of Zorin is still not showing up. My second External HDD is working normally. But this NAS not.
Where did you access the NAS on Mint? You mentioned the web browser (i presume the webui of the device). Did you also access files directly via Files (the "file explorer")?
Do you know the ip address of the NAS? Can you ping it?
Terminal: ping ipaddress
You mention: "I can see the name in the Other locations"
What exactly happens when you click on it?
1 Like
I've set it up via webui. I was able to move some files via "file explorer".
Yes I know the IP address and I get a ping response from it
This is what I get when I try to access it via Other locations.
When I try the IP address on the browser I get this
Thank you
Do You have the Firewall in Zorin enabled?
I do, but I've tried to access it when it was disabled and it made no difference.
Is this a wired or wireless Connection?
Unless you changed it the Web HMI is on port 9999. Try connecting using http://192.168.1.11:9999.
I am not sure why, but sometimes Zorin does not see SMB servers on the other locations tab. You can connect to the share by typing smb://192.168.1.11/"personal_folder" in the server address box, replace "personal_folder" with the share name on your NAS.
You can also add a mount command to your .profile if you want to connect to the share every time you log on.
Create a file called .smbcreds in you home folder and put your logon user name and password in this file.
Then add this command to the .profile file in your home directory.
Again, replace 'share_name' with the share name on your NAS.
gio mount smb://192.168.1.11/'share_name' < ~/.smbcreds
1 Like
is wired connection via router
Same thing..
Unable to connect. Is like is not there. But on the same network I can connect to my NAS from 4 different Android phones/tablets (via WIFI), 1 Win 10 PC via wired connection, and via another Zorin laptop using WIFI.
Only my main PC doesn't want to see it.
Can you ping the NAS from your Linux machine?
(edit) never mind, I re-read the thread and see where you said that you are able to ping the NAS, sorry.
1 Like
For the browser, does it force https?
Have you tried manually mapping (either via the GUI or /etc/fstab), rather than relying on discovery?
I wonder, is the NAS using an older version of SMB? I think the kernel might have dropped anything less than v3 by default. Earlier versions can be specified in fstab if required.
Yes it force it https.
Finally now is working.
What I've done is to connect it via the bottom task bar smb://192.168.1.11 and it worked
EDIT - I've done that before and it didn't worked.
1 Like
For the webUI, i would expect you'll have to force it to accept http, not https. Your browser may have a setting which allows you to define exceptions to the https-always 'rule'.
1 Like
If that is the fix, can you mark the post as 
Solution.
Well to be fair I don't know what was the solution. It just started working after 3 months