![]() If you look at post 39 there is a link to an article that shows unix command you can use to force the Mac to use SMB1 rather than the new SMB2 protocols Apple has implemented. A reminder may appear no more than once a day until disabled by checking the donation checkbox ( (It is assumed a donation has happened :) )). ![]() ![]() Sharing files from Mac running Mavericks 10.9 over SMB to Windows 8.1 works fine, both in terms of browsing in explorer and playback in native media app, but XBMC cannot see any items inside the shared directory… SMBUp (current version: 1.4.1) re-instates Samba as a service of your mac and provides a simple interface to manage the service. Initially I thought maybe it didn't like spaces between the names of the folders containing the movie files and after an hour of troubleshooting I realised that XBMC connecting to SMB shares hosted on Mavericks couldn't see any more than around 50 titles in a single folder. (, 22:42)stiwi Wrote: (, 14:44)Kokonutcreme Wrote: Īfter investigating possible causes I noticed a peculiar behaviour in XBMC where I could browse to the drive where I added the movies but there were 0 items in the specific directory. No more issues (other than Mavericks wanting to switch back to Apple's SMB when I reboot I have to turn it back off in preferences and start the SMBUp server again). To be safe, I actually set my entire 3TB media drive to recursive set all media files to have the Everyone setting set to READ. I ran into this problem when I switched my PPC PowerMac server running Leopard over to a new 2012 Mac Mini running Mountain Lion. I selected the entire directory folder and set it to recursive file permission change and set all groups/everyone to READ permissions. All the movies and photos that would not display in XBMC properly all somehow got their file permissions set wrong. Check the directory and files that aren't reading for "Everyone" READ permissions. I think Apple's SMB always fudged it or something. I had a similar problem and it's probably the same thing. Typically 0 is used, but any number less than the value of loginretries can be used.(, 14:44)Kokonutcreme Wrote: I was eventually able to restore my network connections between Windows and OS X but discovered after adding a couple of new movies to my collection that they weren't being scraped, I could browse to the directories via Windows Explorer and see the files so it wasn't because of the network connection. # chsec -f /etc/security/lastlog -s USERNAME -a unsuccessful_login_count=0 Once the user's account is locked, the user will not be able to log in until the system administrator resets the user's unsuccessful_login_count attribute in the /etc/security/lastlog file to be less than the value of loginretries. There have been too many unsuccessful login attempts please see If a user attempts to log in, but gives the wrong password, once they have made unsuccessful attempts equal to or greater than the number given in loginretries, any further login attempt would fail with this message: Where NUMBER would be a numeric signifying the maximum number of attempts to log in, and USERNAME is the account to be changed. This attribute would be set via the chuser command: ![]() The last successful login before the system locks the account. Have root or a user with a role containing the authorization "" set the new user's password.ĭefines the number of unsuccessful login attempts allowed after You entered an invalid login name or password. Information to the /etc/security/passwd file.Ī login attempt to this account would give this error: Until the passwd or pwdadm commands are used to add authentication Is set with the passwd or pwdadm command. Initializes the password field with an * (asterisk). The mkuser command does not create password information for a user. Notice initially the user has a * in the password field, rather than ! which is used to signify the password is stored in a shadow file (/etc/security/passwd in AIX) In the file /etc/passwd the entry for a new user "lockme": A new user account created with the /usr/bin/mkuser command will automatically be locked, and will have no initial password. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |