Can anybody give me further Information. I cannot find a way to connect my synology via smb, nfs or UPNP or…Is there a way to do that?
same here. i have network storage (hdd connected to router and shared via SMB) and i don’t know how to add it to PMS on my Shield. anyone?
It was fast and easy for me :
System Seetings -> Storage -> Network Storage
It will find all available networks on your local network and you can connect to it.
I have a Synology NAS and it connected right away. Choose to connect as your synology admin user to have write permissions.
@kerwan said:
It was fast and easy for me :
System Seetings → Storage → Network StorageIt will find all available networks on your local network and you can connect to it.
I have a Synology NAS and it connected right away. Choose to connect as your synology admin user to have write permissions.
I can connect to my device no problem. I can’t see any of the shares I have created. Only Downloads and Users which I haven’t shared?!
Be sure to have activated Windows Share (smb) in your Synology Pannel Configuration.
I have guest permission to read to my shared folders and admin permission to write /read.
I connected on the Shield with my admin account and I have access to everything I configured.
@kerwan said:
It was fast and easy for me :
System Seetings → Storage → Network Storage
where? on my Shield? On my PC logged to PlexServer?
I have noticed that PLEX on Shield doesn’t seem to see SMB folder on NAS which have spaces in the names. Anyone else seen this?
@stuartlockey said:
I have noticed that PLEX on Shield doesn’t seem to see SMB folder on NAS which have spaces in the names. Anyone else seen this?
Yep, I noticed that too, and a bunch of users on the GeForce Shield board noticed it too.
@kegobeer-plex said:
@stuartlockey said:
I have noticed that PLEX on Shield doesn’t seem to see SMB folder on NAS which have spaces in the names. Anyone else seen this?Yep, I noticed that too, and a bunch of users on the GeForce Shield board noticed it too.
@kegobeer-plex said:
@stuartlockey said:
I have noticed that PLEX on Shield doesn’t seem to see SMB folder on NAS which have spaces in the names. Anyone else seen this?Yep, I noticed that too, and a bunch of users on the GeForce Shield board noticed it too.
Thanks for confirming that. Glad I’m not going mad. I’m certainly not restructuereing my NAS for this, so hopefully it’ll be fixed before long.
does anyone has his synology on a different subnet? i.e. shield on 192.168.1.* and synology on 192.168.2.*
i can manually connect to smb:\user:password@192.168.2.2\share and plex sees the share no problem.
however, as soon as i reboot the shield, the mounted share disappears, i’ll have to manually add share again…
anyone has the same problem?
Do you have a router connecting the two subnets?
I was able to connect my Synology NAS under the ‘Settings > Device > Storage & reset > Network storage’, you should see your NAS under the available shares in 10-20 seconds (for me it was). The only issue I ran into, I couldn’t connect as a guest, I had to use the admin account to connect it to my Nvidia Shield. Once I did that, I was able to connect without an issue.
@kegobeer-plex said:
Do you have a router connecting the two subnets?
yes, it’s an edge router and having both subnets connected to it.
I know the Synology NAS doesn’t care where it is, this kind of configuration is done all the time when the network is set up right, which it sounds like yours is. Do you have this working on a standard Plex server, where if you reboot the Plex server it reconnects to the existing mount?
@kegobeer-plex said:
I know the Synology NAS doesn’t care where it is, this kind of configuration is done all the time when the network is set up right, which it sounds like yours is. Do you have this working on a standard Plex server, where if you reboot the Plex server it reconnects to the existing mount?
the main PLEX server is running on synology itself, but i don’t think it’s a plex problem, rather than a shield mounting problem. it somehow can’t remember the smb share…
btw, everything else in the network works fine, connects fine.
@garyleecn said:
@kegobeer-plex said:
I know the Synology NAS doesn’t care where it is, this kind of configuration is done all the time when the network is set up right, which it sounds like yours is. Do you have this working on a standard Plex server, where if you reboot the Plex server it reconnects to the existing mount?the main PLEX server is running on synology itself, but i don’t think it’s a plex problem, rather than a shield mounting problem. it somehow can’t remember the smb share…
btw, everything else in the network works fine, connects fine.
Do you have any way to create some shares on a machine that’s on a different subnet from the NAS and test rebooting it to see if the shares are remembered?
Fist start controlpanel locate windows file-servise and enable (also known as SNB)
I control panel go to security locate firewall and disable it
in 20 sec you should see your nas drive and be able to mount it
the next problem is that I can’t enable the firewall again without loosing connection to the mounted drive, any ideas for that? som port or programpermission is needed, but can’t figure out what
I THINK I’VE FIXED IT!! I’ve been having this issue for ages and I may have solved it…
So, my NAS password had a ‘@’ in it, which I changed to a different password this evening, without the ‘@’. I was previously mounting the diskstation from the ‘available drives’ list, not by adding it manually and ended up trying the manual route as a last resort. Below is an example of the path I was trying:
smb://user:p@ssword@192.168.1.60/share
That wasn’t working, but in seeing the full path it was obvious why - the ‘@’ in my password was being used as a delimiter between the password field and the NAS path. Essentially the Shield was trying to connect to ‘ssword’ using the password ‘p’. I changed my password to something else without the ‘@’ and tried just adding the drive again via the ‘available drives’ list… this worked first time and I can access my files perfectly. I didn’t even need to mess around with the manual route.
Like I said, I only did this tonight, but I’ve not been able to connect for months and now this works, so I’m confident it’s fixed it.
I hope that helps everyone with an issue I’ve struggled with for ages!
