ChrisP replied at Fri Nov 28, 2014 04:21
Just to clear an ambiguity: Kodi CAN use authenticated SMB connection,
The way to define it is a bi ...
That was never the issue. I've always used authenticated SMB connections from all versions of XBMC/Kodi.
The real issue is that when the "playercorefactory.xml" file is used to make XBMC call an external player for playback, this only works for locally stored files or files shared without authentication, since XBMC/Kodi never includes authentication in the SMB links passed to the external player.
That is what SMBwrapper was all about. It would create its own "playercorefactory.xml" linking itself as external player. But when XBMC called it for playback, SMBwrapper would then dig into the password file of XBMC and build a complete authenticated SMB link, and pass that along to the real external player, as chosen in SMBwrapper settings. But SMBwrapper only worked for XBMC but not for Kodi, and even with XBMC I had problems making it work.
XBMCwrapper is a later project inspired by SMBwrapper, and updated to use the new access paths of Kodi, but apparently it was not written to do the same job as SMBwrapper, but was intended mainly to deal with online streaming protocols that XBMC failed to pass correctly to external players. So while XBMCwrapper has a similar purpose as SMBwrapper, it deals with other protocols. At least that is what its docs state, and its author has posted in one forum that fixing it for SMB is impossible (which I strongly disagree with).
Best regards: dlanor