this post was submitted on 07 Jul 2025
9 points (90.9% liked)

Synology

96 readers
1 users here now

Community to discuss Synology products including Network Attached Storage (NAS)

Rules

1. No off topic posts

Posts must be related to Synology

2. Be kind

No insults or overtly rude behavior. You can be right just try to be kind too.

founded 3 months ago
MODERATORS
notnotmike@programming.dev
9
SMB synology connection error (lemmy.world)
submitted 2 weeks ago* (last edited 2 weeks ago) by happeningtofry99158@lemmy.world to c/synology@programming.dev
8 comments fedilink hide all child comments
 

I'm trying to connect to smb on synology nas using material files

  • add storage > SMB server > add manually >
  • Hostname: wwddiyt.synology.me
  • Port: 445
  • Path: blank
  • Username: Username
  • Password: Password
  • Domain: blank

But it gives me this error below

java8.nio.file.FileSystemException:/:
java.net.ConnectException:failed to connect to
wwddiyt.synology.me/192.168.0.101 (port 445) from /: (port
0):connect failed:EACCES (Permission denied)

Just want to provide more info: I have 7 Shared folders under Volume 1 in my synology NAS. docker, home, homes... and I can access those shared folders in windows explorer by tying //NasName

Thanks a lot in advance

top 8 comments
sorted by: hot top controversial new old
[–] encrust9870@lemmy.world 3 points 2 weeks ago (2 children)

You may need to include a path. You might need to add each of your Shared folders separately. I have had this issue with Samba before where the host was browseable, but you could not mount the whole server.

[–] Onomatopoeia@lemmy.cafe 1 points 2 weeks ago

Yep, this is how SMB works when using Linux - I can't explain why, but that's always been my experience when either side is Linux - you just get a cryptic error.

I was just fighting this earlier today trying to connect to my networked photo frame (which runs Linux). I'd forgotten the share name, and Windows Explorer couldn't open just the server name. Once I added the share name it opened no problem.

[–] happeningtofry99158@lemmy.world 1 points 2 weeks ago* (last edited 2 weeks ago)

I have added Path in material files setting using FOLDERNAME and /FOLDERNAME but neither worked. What exact syntax should I use to fill in Path option?

EDIT: just want to provide more info: I have 7 Shared folders under Volume 1 in my synology NAS. docker, home, homes... and I can access those shared folders in windows explorer by tying //NasName

[–] boblin@sh.itjust.works 1 points 2 weeks ago (1 children)

Are you potentially trying to mount a SMB share to the root folder on your client (i.e. / )? The error looks like the client is attempting to do something it itself is not allowed on its machine. Try specifing a path to mount to which is writable - e.g. /tmp/mount (not that you should keep mounting there if it works).

[–] happeningtofry99158@lemmy.world 1 points 2 weeks ago (1 children)

Is this Path option referring to the path on my android mobile? I thought it is referring to the path of my synology NAS.

Should I use exact path of android or relative path? I'm not quite sure what is the full path of my android mobile. But I think it is something like ...emulated/0/...

[–] boblin@sh.itjust.works 1 points 2 weeks ago (1 children)

I think its you device‘s path, i.e. on Android - otherwise the error would look different I presume.

Yes, /emulated/0/my-smb-mount or similar looks about right.

[–] happeningtofry99158@lemmy.world 1 points 2 weeks ago

The issue is I have VPN enabled. Very unexpected

[–] happeningtofry99158@lemmy.world 1 points 2 weeks ago

The issue is I have VPN enabled. Very unexpected