Jump to content

Fire TV sees SMB, Kodi not so much


atomicmoon

Recommended Posts

atomicmoon

I apologize for asking a question that has been asked since the dawn of 17.1 Kodi, but all posts with similar problem do not list a solution, just someone saying, "I figured it out!"

I upgraded from a Fire TV to a Mi Box, and can not get the SMB to work to allow native playback.

I have successfully set it up with add-on default, but I would LIKE to bypass this for response speed.

 

I have gone through "windows features" and insure all SMB versions are enabled on windows 10 server, but my Kodi can't even see anything on my "workgroup"

I've attempted to set the WINS in kodi to my router's IP, (in the past I believe this fixed this issue) but no luck on seeing anything.

 

I again, apologize for asking a question that has been asked before, but I'm hitting walls, and this is the only device that I can't manipulate to use native paths, or even see my network.

 

If there is a post with a step-by-step solution, please forgive my inability to find it searching the forums, and toss the link in a reply.

 

Boggled that my fire tv has no issues, but my more powerful mibox is throwing a fit....

Link to comment
Share on other sites

atomicmoon

At the moment I don't have any version preference of Kodi. I was using 17.6, but tried the beta when I couldn't get anywhere. 
Honestly I don't want to take much of your time with this as you are extremely busy helping legit problems lol.

I'm willing to use any version of Kodi and any version of Emby to get this working. 

I'm just very aware this problem exists and I'm just frustrated that it isn't a smooth transition.

 

I have a mi box 3

Willing to use any version of kodi/emby to get SMB working correctly for native playback.

 

Thanks for any assistance!

Link to comment
Share on other sites

atomicmoon

Update: using RC1, I was able to edit the WINS settings to my internal IP and miraculously after it restarted I was able to browse my "workgroup!"
Sadly, when trying to add the my network storage device, I went through file browser and attempted to connect again I got a "Operation Not Permitted"

when trying to select "workgroup" which previously had shown me all my network PCs.
 

So, 2 small step forward and 1 back at this time.

 

Update 2: Set minimum SMB to ver1.0 in Kodi RC1 service settings. Bypassing the browse SMB option in Kodi RC1, I manually added my NAS and it is allowing me to browse my files. Going to attempt to do the same for my Emby server machine.

 

Update 3: Started off rocky. Attempted to test the "browse" option and sometimes it shows me my machines, sometimes "operation is not permitted". So abandoning hope with the SMB browse. Was getting "operation is not permitted" when I attempted to manually added my Emby server machine but I believe it was due to a password error, because I corrected the password, and I now have added my Emby server machine to KodiRC1 file browser and they can in theory see one another. Would have been nice to get an invalid password error but whatever.
Next up, installing the beta Emby add-on and seeing if it will play nice and see my machines.

Update 4: Upon installing the emby beta add-on, the moment it installed, the pop-up showed and listed my servers!!! Previously it popped up, but didn't list any local servers. Feeling kinda optimistic....
Hoping that after initial sync they don't give a fit about "file not found would you like to remove", but so far, so good.....

 

Update 5: Profit! It was the simplest fix but wow, what a frustration over something so minor. Glad to be back with Kodi/Emby, and even some new things to explore!

Edited by atomicmoon
  • Like 1
Link to comment
Share on other sites

Angelblue05

You think the fix was the SMB setting AND the WINS settings?

Edited by Angelblue05
Link to comment
Share on other sites

atomicmoon

You think the fix was the SMB setting AND the WINS settings?

That's a good question...... Now that I know I can get to this point one way or another, I'll give it a try again this weekend and see which steps prevent access. 

 

  • Like 1
Link to comment
Share on other sites

atomicmoon

You think the fix was the SMB setting AND the WINS settings?

It appears it is just the WINS settings.

Wiped everything, started from scratch (aside from resetting my SMB settings on my current Emby server)

My backup server was still accessible without adjusting the SMB version settings to allow 1.0.

The troubleshooting problem is if you leave kodi idle for for a couple of hours, it says it can't find the files and asks to remove them. A simple restart of Kodi "fixes" this, but gave a couple of scares when I thought I had

everything sorted out.

I'm going to stick it out with RC1 and Emby Beta addon for now since they are working rather solid for me.

Link to comment
Share on other sites

I cannot say much since I have a Synology with Emby Server but a simple question, if you search for the machine IP instead of it's workgroup name, does it get listed/browseable?

Set up the source on KODI and check it out.

 

Sounds to me like you had a master browser issue since you're using a Windows Server (ewwww :D  :D ).

 

And basically, when you say you couldn't browse your server using KODI in the Mi Box, does it meant that you were not able to direct play using the plugin? What about library building?

Edited by djhifi
Link to comment
Share on other sites

atomicmoon

I cannot say much since I have a Synology with Emby Server but a simple question, if you search for the machine IP instead of it's workgroup name, does it get listed/browseable?

Set up the source on KODI and check it out.

 

Sounds to me like you had a master browser issue since you're using a Windows Server (ewwww :D  :D ).

 

And basically, when you say you couldn't browse your server using KODI in the Mi Box, does it meant that you were not able to direct play using the plugin? What about library building?

 

 

Manually adding IP addresses gave the same, "operation has failed" error message until the WINS was set to the router's IP address.

I'm not sure what a "master browser issue" is, but I've always used Windows as a server with little to no issues until attempting RC1 setup.

 

I did not attempt to build a library solely in Kodi as I wouldn't be using that in the future. I do not believe it would have found the media items if it could not find the computer the media is hosted on without setting up WINS settings first.

Link to comment
Share on other sites

atomicmoon

Today, new content populated in Kodi from Emby but path could not be found.
I checked the path and it was looking for my "Optional Shared Network" path that I had setup as nfs://
Switched all paths to SMB:// as Kodi has no problems with this protocol. 
Currently resyncing library and off to work. Appears I'm not 100% out of the woods yet, but hopefully we can use my body for science for future troubleshooting.

Link to comment
Share on other sites

atomicmoon

Latest is, Kodi refuses to play any videos populated by Emby. Say's that they aren't there.
I can watch all videos through Kodi's file browser with no issues.

Somewhere, Emby isn't getting the network credentials, and unless I'm blind, the option to enter them is not in the beta add-on.

I'll keep messing around until I've got it, or my sanity wears out.

 

I got yelled at by my boss, aka my fiancee, to "stop messing with stuff!"
So, setting up stable 17.6 and Emby add-on, but I'm going to continue "messing with stuff" on my backup server.

Edited by atomicmoon
Link to comment
Share on other sites

Angelblue05

Check your paths, the add-on doesn't control playback when using native playback mode. As long as the path provided is what Kodi expects, then it should work.

 

Best suggestion is to try to navigate to the media folders in kodi (usually addons > install from zip > smb > compare the path there, to what is in Emby. 

 

That's why default add-on playback is good, because it bypasses your path setup. You can even get direct play with add-on mode. Also, it's the easiest way to figure out your possible path issues, as it doesn't require you to repair your library if you change the optional network path value on your server.

Link to comment
Share on other sites

atomicmoon

I'm giving Emby Con another try. My biggest complaint before was it took forever to populate my library root folders on the Fire TV.

It's actually just as fast as the Emby add-on on the MiBox so right now I'm in a good spot. Everything works and I'm looking forward to seeing kodi leia out of beta.

  • Like 1
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...