• Believing that it was actually a user credential issue on my Windows 8.1 machine, I went ahead and created a whole new account in Windows, making sure to not include any spaces in the username (my primary account contains a space, and I thought that may have been the original culprit). I correctly setup sharing and applied the proper permissions of this new account to the directories. I have applied 'Full Control' permissions for this newly created account, as well as 'Everyone', to both the Share permissions and the file/folder security permissions.
  
  
• I've enabled the 'Guest' account on my Windows machine.
  
  
• I've tried the process after completely turning off the Windows Firewall.
  
  
• I've completely cleared ALL my Window's machines Sharing permissions, and started over Sharing from scratch.
  
  
• I've checked:
  Control Panel - Administrative Tools - Local Security Policy - Local Policies - Security Options
  
  Network security: LAN Manager authentication level
  Send LM & NTLM responses
  
  Minimum session security for NTLM SSP
  Disable Require 128-bit encryption
  
  
• I've installed the 'ES File Explorer' app onto my Fire TV. Using the credentials of the new account, I am able to successfully connect to the exact same directory that my backups would be transferring to via the Backup add-on, as well as the Thumbnails directory. I am also able to write and overwrite files in both directions. This leads me to believe that my permissions and credentials are intact.
  
  
• Now having the ability to copy files back and forth, I've been able to inspect my 'passwords.xml' and 'sources.xml' files in my Kodi \userdata folder. The content in these files correctly reflect the proper credentials and smb paths.
  
  
• Using the 'Fire TV Utility App' on my workstation, I am able to successfully run its backup feature to transfer the same files from the AFTV Kodi installation to my workstation.
  

Quote:ERROR: static bool XFILE::CFile::Copy(const CURL&, const CURL&, XFILE::IFileCallback*, void*) - Failed write to file smb://192.168.79.100/Pixar/extrafanart/rrAdTMAH41reM6HKJDdu3HpW2Lf.jpg

Quote:ERROR: static bool XFILE::CFile::Copy(const CURL&, const CURL&, XFILE::IFileCallback*, void*) - Failed write to file smb://BATCOMPUTER/AmazonFireTV/KodiBackups/Main/201503022359/xbmcbackup.val

Quote:00:16:27 T:1725350960 WARNING: SMBFile::OpenForWrite() called with overwriting enabled! - smb://USERNAME[email protected]/Movies/extrathumbs/thumb2.jpg
00:16:27 T:1725350960 ERROR: static bool XFILE::CFile::Copy(const CURL&, const CURL&, XFILE::IFileCallback*, void*) - Failed write to file smb://192.168.79.100/Movies/extrathumbs/thumb2.jpg
00:16:27 T:1725350960 DEBUG: CSMBFile::Close closing fd 10000

(2015-03-03, 19:09)dr.joaomarcelo Wrote: I had this problem with smb using windows 8.1. The biggest problem was actually not being able to save the subtitles to the movie folder. I tried everything like you did and in the end i gave up and started using NFS for sharing my files. This way i have no more issues.

Seems like an issue with kodi android version and windows smb, perhaps only windows 8. I have no issues with kodi running in another windows machine.

(2015-03-03, 22:57)DruTheFu Wrote:

(2015-03-03, 19:09)dr.joaomarcelo Wrote: I had this problem with smb using windows 8.1. The biggest problem was actually not being able to save the subtitles to the movie folder. I tried everything like you did and in the end i gave up and started using NFS for sharing my files. This way i have no more issues.

Seems like an issue with kodi android version and windows smb, perhaps only windows 8. I have no issues with kodi running in another windows machine.

When originally adding my sources, I attempted to add a NFS source instead of via SMB, but I was not presented with any NFS drives to choose from, so went with the SMB route. Did you have to install a NFS client on your Windows machine? If I mount the Shares as NFS, will I lose the ability to leverage SMB as a fallback method?