Cannot add network share (1 Viewer)

[octessence]

I have a Synology Diskstation 1812+. In the Windows Network it does not appear in the Computer section but under Other Devices. This means that it doesn't appear as a computer under Network until I enter \\vault\.

Within MediaPortal 2, I cannot add any shared folders from this device because I cannot manually enter paths. Even if I have browsed for the device in Explorer an have it listed under Network, I still can't get MP2 to see it.

You could call this a feature request to be able to add a share by entering the path directly, but for me it's a bug because it stops me being able to use MP2.

EDIT: Screenshots attached. N.B. "NAS" is a QNAP running debian, I'm talking about the one called vault.

 

[Lehmden]

Hi.
You're not the only one with this issue. We're working on a solution but still haven't nailed down the root cause of this issue.

 

[morpheus_xx]

@octessence can you please try the attached file?
Simply save, extract and run it from console. It will test different methods to enumerate available network shares. Please post the output of this file, maybe we can find the source of your problem.

 

[octessence]

M:\Downloads\190030_NetworkComputerEnum>NetworkComputerEnum.exe
Testing method: ListMP1Way
\\HTPC
\\NAS
Duration: 2503 ms
---------------
Testing method: ListWinNT
ListWinNT: Domain/Workgroup: TUCKER
ListWinNT: HTPC
ListWinNT: NAS
Duration: 2259 ms
---------------
Testing method: ListWindowsAPICodePackShell
ListWindowsAPICodePackShell: \\NAS
ListWindowsAPICodePackShell: \\HTPC
ListWindowsAPICodePackShell: \\HTPC
Duration: 9370 ms
---------------
Testing method: ListWNetEnum
ListWNetEnum: \\HTPC
ListWNetEnum: \\NAS
Duration: 36 ms
---------------

M:\Downloads\190030_NetworkComputerEnum>ping vault

Pinging vault [192.168.1.6] with 32 bytes of data:
Reply from 192.168.1.6: bytes=32 time<1ms TTL=64
Reply from 192.168.1.6: bytes=32 time<1ms TTL=64
Reply from 192.168.1.6: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.6:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C

M:\Downloads\190030_NetworkComputerEnum>dir \\vault\video
Volume in drive \\vault\video is video
Volume Serial Number is 609A-7944

Directory of \\vault\video

25/11/2013 00:26 <DIR> Documentaries
17/01/2014 18:10 <DIR> Movies
28/02/2014 00:32 <DIR> TV
27/01/2013 22:08 <DIR> Amanda
16/09/2013 13:57 <DIR> Sports
17/01/2014 18:28 <DIR> Fireplace
16/09/2013 13:37 <DIR> Wedding
17/09/2013 10:14 <DIR> Podcasts
27/03/2013 00:11 <DIR> Stand-up Comedy
0 File(s) 0 bytes
9 Dir(s) 4,600,217,010,176 bytes free

M:\Downloads\190030_NetworkComputerEnum>NetworkComputerEnum.exe
Testing method: ListMP1Way
\\HTPC
\\NAS
Duration: 2630 ms
---------------
Testing method: ListWinNT
ListWinNT: Domain/Workgroup: TUCKER
ListWinNT: HTPC
ListWinNT: NAS
Duration: 2259 ms
---------------
Testing method: ListWindowsAPICodePackShell
ListWindowsAPICodePackShell: \\NAS
ListWindowsAPICodePackShell: \\HTPC
Duration: 311 ms
---------------
Testing method: ListWNetEnum
ListWNetEnum: \\HTPC
ListWNetEnum: \\NAS
Duration: 28 ms
---------------

M:\Downloads\190030_NetworkComputerEnum>

 

[morpheus_xx]

Not sure what's the root of your experienced problem:
as also the explorer is not able to detect the "vault" as normal network resource, the test methods also fail to find them. It could be, that Plex media server doesn't provide all required services to be seen as a network share. But I wonder, why the device appears after you entered it's path manually...

I can offer to take a look at your setup, using remote access via TeamViewer...

 

[octessence]

It is caused by how the nas appears to any Windows system on the Network so it's not just limited to my HTPC. I have reset the nas to factory defaults and still get the same problem so it might be down to the way Synology have decided to configure samba. Previously it was never an issue really because MP1 allows you to type the direct path without needing to browse for it. For MP2 I don't really have a workaround. Where is the configuration for the shares held? Is it an xml file or one of the sqlite databases?

 

[morpheus_xx]

If you really want do insert your share manually, you can take these steps. But only if you are sure what you are doing. Warning: I have not tested this completely!

1) Find your server's system ID, look into: C:\ProgramData\Team MediaPortal\MP2-Server\Config\MediaPortal.Common.Services.SystemResolver.Settings.SystemResolverSettings.xml

2) Stop the MP2-Server

3) Open the MP2-Server DB with a Sqlite query tool: C:\ProgramData\Team MediaPortal\MP2-Server\Database\Datastore.s3db

4) Modify those statements to contain you real systemid and execute them:

insert into SHARES(share_id, system_id, base_resource_path, name)
values (X'777AAB873C2D4F99A885204EC3D4B9D1', 'your system ID', '{03dd2da6-4da8-4d3e-9e55-80e3165729a3}:////vault/video/', 'vault videos');

insert into SHARES_CATEGORIES(share_id, categoryname)
values (X'777AAB873C2D4F99A885204EC3D4B9D1', 'Video');

5) Start MP2-Server service

6) Enter MP2-Client share settings, edit the share and/or do a reimport

 

[octessence]

Great thanks. I'll give that a try if I don't manage to find out what the nas is doing.

 

[mnmr]

I can add that I didn't have any issues finding my NAS (a Synology DS-1813), so it sounds more like a firewall issue or perhaps network browsing has been disabled on the NAS.

The device you see in Other Devices is probably the built-in media server on the NAS. The samba (windows file sharing) should show up under the Network folder.

 

[mnmr]

You could also open a command prompt and type "net view" to have windows enumerate the machines it can find. If it doesnt see it, MP wont either.