Wrapper not accessing files

[mtenga]

Hi,

I've just taken delivery of a Q10 Pro and have problems with the wrapper.

My six hard drives are attached to a Zappiti media player which acts as a Samba server. I have no problem accessing these files via SMB V1 over my network. Various devices can read the files including Kodi on the Q10 Pro. No passwords are used.

However, the wrapper will not access the files. The wrapper app itself says its wants credentials, which do not exist.

The LAN option in the Media Centre will let me browse to the six drives but not any of the eighteen shares that are on them. When I click on one of the drives it simply says..."no such file or directory exists".

I can't add the shares manually using the "add share" function in Media Centre. I get a "network server error" message.

The Kodi Player is no good to me and I need the wrapper.

Any ideas?

[Phil181]

Your issue does sound like a networking problem but it may be difficult to make suggestions since you are using an old media player for your Samba network rather than something well known like Windows 10 (which has its own thread for SMB network issues).

Perhaps it is related to Samba shares if Kodi can see your network ok?  If MediaCenter can see the drives but not the folders, there maybe something wrong in your settings, somewhere.
 
If you have not already done so, definitely update to the latest firmware and I'd suggest the Custom Firmware.  Have you read the through the FAQ completely on networking?

[Joker]

You will need to narrow down which device in your network is causing the issue. Given that we know that Windows PC SMBv1.0 works with Q10 Pro. You need to find some way of validating your network, do you have access to a PC? If you test with a PC and Q10 Pro and can access each other then you know the Q10 Pro is working correctly.

What about NAS? Have you tried to use this as an alternative, I think I read somewhere that Zappiti media player supports NAS.

[mtenga]

It is academic now since I reluctantly have sent the machine back.

As to the Zappiti server I have no problem accessing the files via SAMBA on 2 Amazon Firesticks, 3 PC's, another Zappit Media player and an OSMC Vero. As I said, Kodi on the Q10 also picked them up without issues. The only device in the whole of the network to have any issue with access was the wrapper. So I would suggest that the evidence strongly suggests that there is nothing wrong with my network or settings and this is due to the fussy way the wrapper works.

I did try a Win10 PC as a server and the wrapper would pick up certain folders but not others. Seemed to be something to do with whether the underlying media was in its own folder (bad) or just listed at the same level (good). Might have been due to naming as well. But again I have no probelm with these shares elsewhere.

Anyway, just too much unnecessary effort in the end for no positive result.

[Mount81]

I'm not sure that Media Center can handle whole drives directly, eg. when you try to access them by drive letter, and directly from their root directory. Rather it needs the shares to be in subfolders.  That applies as well when adding the shares manually, it's clear that it asks for directory names. Maybe you can try to rearrange your SMB shares according to this somehow, and rather than sharing the whole drive, specify only the subfolders (or a main subfolder) to be shared.

[mtenga]

[futeko.com]

I think this was most likely a problem with spaces or special characters (non alphanumeric) in the paths. Q10 Pro SMB client is fussy with these.

[mtenga]

I think this was most likely a problem with spaces or special characters (non alphanumeric) in the paths. Q10 Pro SMB client is fussy with these.

Could be the case.

The Zappiti server names the drives and I have no power over that. Typically the drives are named "Disk_sda1", "Disk_sdb2", etc...

Thereafter the shares are variously named "Movies One", "TV2", etc...

If it is just the case of an underscore throwing the wrapper then it is disappointing as a solution. I have no trouble elsewhere on numerous devices including Kodi on the Q10 as I've said.

It is a pity because otherwise the device seems to have an impressive spec and ticks a number of boxes for me.

[Mount81]

What version of FW are you on?

Quote from the latest 2.1.1 FW changelog:

4. Solved the problem that if there is a blank space,the SMB share path cannot be mounted
6. Solved the problem that SMB cannot be accessed to the shared file, of which title includes special characters

[mtenga]

[saltino]

I confirm mediacenter have problem with WINDOWS share

I can access on Synology NAS (no-problem), drive letter or directory it's same, not access under WINDOWS10 "query is wrong" error everytime.

I've a root Himedia Q10Pro where is log of native 'mediacenter' I would read...

[futeko.com]

Possibly this?: https://www.futeko.com/newforum/index.php?topic=2536.0

[saltino]

Possibly this?: https://www.futeko.com/newforum/index.php?topic=2536.0

Obviusly if I regress to SMB1 everything work again, but this insecure!!

Now also Kodi Leila accept SMB v2/3, please.. I ask again, where is log of native 'mediacenter???