[ChicagoBob123]

Here is what I have, a FireTV stick with Kodi side loaded, and an Odroid C1 with Android both loaded with Kodi 14.
Both of these devices are ARM devices.
Both of these devices used to able to access my network drive loaded with moves which
consists of a Rasberry Pi running Samba. I started with the FireTV stick.
Everything worked just fine then for no reason the FireTV stick stopped connecting to network drive
stating connection timeout, but it could still connect to the internet run Netflix, Hulu and connected to another
drive I have on a Windows PC.

So, I switched from using the FireTV stick, thinking it was something weird about side loading Kodi, to an ODroid C1
with Android loaded. Same thing happened. After a while, for reasons I can not understand Kodi just stopped being able to connect
to the Rasberry Pi running Samba. Everything worked just fine for at least a month then nothing. It just quit complaining about connection
time out and yet it could get to the Windows PC share just fine. NetFlix and Hulu for the the ODroid C1 worked just fine as well.
My connection for both is via WiFi but the connection is strong.

Oh and my windows PC as well as all my Android phones can get to and play movies from the Rasberry Pi running Samba even while
all this connection timeout nonsense is going on.
One more ODD thing. I read someplace on a forum that if I left it along for a couple of days that it would work again which did happen
with the FireTV stick before it quit again. Absolutely maddening

My request to you is how do I track this issue down. Its making me crazy. When this was working it was such a joy now its just
another frustration.

[Ned Scott]

Are you using IP addresses or netbios names for the SMB paths? This might sound weird, but if you are using the names and not IP addresses, you might fix this by restarting all the computers on your network. SMB works by all the SMB-capable devices talking to each other and deciding on one of them being a master for routing the names to the proper machine. They do this based on a number of factors, such as uptime. By rebooting them that forces them to re-evaluate which machine is the master, as the current one might just be having weird issues.

[ChicagoBob123]

I am using an IP address. The address of the SMB path is static. Never changes.

[ChicagoBob123]

There must be something going on with SMB and Kodi. I reloaded Kodi and it all worked again. I am now running version 15 alpha and might revert to 14.1 because 15 alpha, which I only tried for about an hour, did not play everything I had yet.

[burowyako]

Did you ever resolve this issue? I'm experiencing the same issue when trying to play files from my NAS. I tried the IP address and the name of the device and get the same result. I can see the list of files but nothing will play when selected. Sometimes I get an error and sometimes I don't.

[ChicagoBob123]

No I did not. I loaded the nightly build 15 alpha and is been working so far.

[burowyako]

No I did not. I loaded the nightly build 15 alpha and is been working so far.

I installed the most recent nightly version and it didn't resolve my issue. Did you make any of the Advanced Settings XML changes by chance? If so, what?

I'd love to find a solution to my problem. Again, my file lists are available but the files won't play. Sometimes I get an error, other times nothing. I can play the same files from other media players without an issue.

[geopgin]

Same issue here running SPMC (14.1), still no resolution...other than reload?

[geopgin]

Okay, so I enabled debug for SMB and pulled the logs

adb pull /sdcard/android/data/com.semperpax.spmc/files/.spmc/temp/spmc.log 'c:\tmp\'

Code:

09:58:06 T:1758669384   DEBUG: int XFILE::CSMBDirectory::OpenDir(const CURL&, std::string&): Using authentication url smb://USERNAME:[email protected]/music
09:58:06 T:1758669384   ERROR: SMBDirectory->GetDirectory: Unable to open directory : 'smb://USERNAME:[email protected]/music'
                                            unix_err:'6e' error : 'Connection timed out'
09:58:06 T:1088803400   DEBUG: ------ Window Init (DialogOK.xml) ------
09:58:06 T:1088803400   DEBUG: Window DialogOK.xml was already loaded
09:58:06 T:1088803400   DEBUG: Alloc resources: 0.85m
09:58:06 T:1088803400    INFO: void XCURL::DllLibCurlGlobal::CheckIdle() - Closing session to http://bitbucket.org (easy=0x6c1936a8, multi=0x629ffac0)
09:58:07 T:1088803400   DEBUG: Keyboard: scancode: 0x17, sym: 0x000d, unicode: 0x0000, modifier: 0x0
09:58:07 T:1088803400   DEBUG: bool CApplication::OnKey(const CKey&): return (0xf00d) pressed, action is Select
09:58:07 T:1088803400   DEBUG: ------ Window Deinit (DialogOK.xml) ------
09:58:07 T:1088803400   ERROR: static bool XFILE::CDirectory::GetDirectory(const CURL&, CFileItemList&, const XFILE::CDirectory::CHints&, bool) - Error getting smb://192.168.0.100/music/
09:58:07 T:1088803400   ERROR: CGUIMediaWindow::GetDirectory(smb://192.168.0.100/music/) failed

I see that 'smb://USERNAME[email protected]/music' is the uri. My question is usr/pwd masked for logging purposes or normally would this show the actual usr/pwd? Also anyone know where usr/pwd is stored and if there in plain text?


Anybody know or can test with working?

[geopgin]

So trolled my system logs on the destination box (win7)and found

Code:

Log Name:      System
Source:        srv
Event ID:      2017
Task Category: None
Level:         Error
Description:
The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="srv" />
    <EventID Qualifiers="49152">2017</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-02-27T13:54:57.813789700Z" />
    <EventRecordID>135638</EventRecordID>
    <Channel>System</Channel>
    <Computer>Home-PC1</Computer>
    <Security />
  </System>
  <EventData>
    <Data>\Device\LanmanServer</Data>
    <Binary>0000040001002C0000000000E10700C0000000009A0000C00000000000000000000000000000000012000000</Binary>
  </EventData>
</Event>

I rebooted the destination box and everything worked. Found this which seems to be a permanent fix.

Also see that there are a lot of other threads on this, this one @sam_1421 came to the same conclusion.

[ChicagoBob123]

My destination box was accessible by other devices whats yours?
Also my destination box was Debian Linux not windows. Glad to hear your problems are gone.