Posts: 5,952
Joined: Sep 2008
Reputation:
201
Koying
Retired Team-Kodi Member
Posts: 5,952
Somehow, I doubt your server is named "WORKGROUP"...
Posts: 18
Joined: Sep 2009
Reputation:
0
hojan
Junior Member
Posts: 18
Same issue here on a Xperia Z2 Tablet, works well connecting to a real windows server, but not to a Synology NAS.
It works as it should with all the other XBMC boxes I have though. I have changed the workgroup name in settings, but no luck.
Posts: 48
Joined: Dec 2013
Reputation:
0
2014-04-09, 12:07
(This post was last modified: 2014-04-10, 01:43 by imaddicted2u.)
In my case I have 2 MK809III mini PC/TV sticks.
One has Android 4.2.2, It connects to all shares in the network named WORKGROUP just fine.
The other has Android 4.4.2. It gives the Operation not permitted error when WORKGROUP is selected while browsing for network shares so a list of servers is not presented. Before upgrading this unit had Android 4.2.2 on it, It all connected and worked correctly then.
Posts: 48
Joined: Dec 2013
Reputation:
0
I just discovered that I can stream content from the servers in the network named WORKGROUP using upnp. I still can't connect to the shares on the servers using SMB.
Posts: 48
Joined: Dec 2013
Reputation:
0
2014-04-10, 12:10
(This post was last modified: 2014-04-10, 12:17 by imaddicted2u.)
Can anybody help on this, streaming using upnp stutters a lot so isn't a good solution. When I used to be able to connect via SMB it worked perfectly.
Could this be an incompatibility issue between XBMC and Android 4.4.2 since it worked fine under 4.2.2?
Thanks in advance.
Posts: 48
Joined: Dec 2013
Reputation:
0
Just to add a new twist to this, I rebooted router on my network. Low and behold I could browse the network, I added a music source, scanned to library, all went well.
I went to add a video source, I got the Operation not permitted error again. I rebooted the router again and was able to add a video source, set content and scan, etc.
I went to add another video source, got the Operation not permitted error again.
Seems in XBMC I can browse the network once with each router reboot. However, In ES file explorer I can always scan and browse the network. Both use SMB. Makes it hard to isolate the source of the problem. If the issue was with the router, wouldn't both programs be affected?
Any thoughts on why this is happening?
Posts: 48
Joined: Dec 2013
Reputation:
0
How or why does XBMC handle SMB shares differently than ES file explorer.
Posts: 31,445
Joined: Jan 2011
No idea. What is hosting your SMB server?
Posts: 48
Joined: Dec 2013
Reputation:
0
Thanks for responding.
A windows 7 PC is hosting the shares.
From my Android device, ES file explorer can always browse the shares while XBMC can browse once with each router reboot. Once the content source is added it can always be accessed from the shares in XBMC. New content is added when XBMC scans the library at startup.
So it's not that XBMC can't access the shares but rather that XBMC can't always browse the shares. So it makes me wonder what ES file explorer does differently.
Posts: 31,445
Joined: Jan 2011
SMB browsing and netbios stuff is kind of a dark art, from what I understand. A lot of reverse engineering and things don't always play nicely. It's hard to say what is different here since I don't believe ES File Explorer is open source, so we don't know what they are doing differently.
Posts: 48
Joined: Dec 2013
Reputation:
0
Thanks Ned,
I have heard of others having same issue so thought SMB browsing could be improved in XBMC.
Posts: 25
Joined: Jan 2007
Reputation:
0
umbala
Junior Member
Posts: 25
Ok, so after all this time there's still no solution for this issue then?? Why is this site so damn useless? Every time I or someone else has a problem, there's never a solution. I remember years ago when I had an issue with XBMC and came here and NO ONE could help me. The answer was "It works for most people. If it's not working for you, then you must be doing something wrong." Well, I just got a new Android box last week and I'm getting this ridiculous "Operation not permitted message" and no one has any idea how to fix it.