2011-10-26, 15:40
As I don't have any SMB shares myself I can't test but I discussed the issue with some other team members and here is how it works:
1. You enter an SMB share as a source
2. XBMC retrieves the username and password and stores them in a password manager
3. XBMC only stores the actual SMB path (no username/password) as the source
Next time XBMC tries to access a sub-path of that SMB path it checks the password manager for known username/password pairs and if it finds a match, uses those. Otherwise it asks the user for the authentication details.
There seems to be a problem though as this does not work with ip-address based SMB paths and only with hostname-based SMB paths.
1. You enter an SMB share as a source
2. XBMC retrieves the username and password and stores them in a password manager
3. XBMC only stores the actual SMB path (no username/password) as the source
Next time XBMC tries to access a sub-path of that SMB path it checks the password manager for known username/password pairs and if it finds a match, uses those. Otherwise it asks the user for the authentication details.
There seems to be a problem though as this does not work with ip-address based SMB paths and only with hostname-based SMB paths.