Mac cannot save on Windows 2016 but could on Windows 2012. Windows Server. When end users maps to smb://WindowsServerIP/Shared and edit Microsoft Documents.
I work with a lot of Windows servers. This means connecting to a VPN and then mounting a share via Samba (SMB). Alas, Keychain won’t autofill saved passwords for Windows servers where the username is prefixed with a domain, like auth stephanieleary.
The current best practice for managing lots of these shares is, from what I can tell from hours and hours of Googling and consulting an Apple training rep:. Create an alias once you’re connected to the share. Disconnect. Delete any previously saved passwords you have in Keychain for that server. Reconnect to the alias and have Keychain save THAT password. But even this does not work reliably. As you can imagine, once you start working with four or five of these things, it becomes challenging to remember the appropriate combination of VPN, server/share, domain username, and password.
Today, after YEARS of struggling (intermittently) with this, I finally remembered something: you can save usernames in the connection string. And — this I knew — you can save connection strings as favorite servers in the Finder’s Go → Connect to Server window. UNIX geeks are probably laughing at me right now. One more quick search confirmed that I can save not only the username, but also that pesky domain prefix and, yes, the password too. Here’s the syntax: smb://domain;username:password@server/share (From.) This is nowhere near as secure as Keychain, since it makes the password visible to anyone who sits down at the computer and opens up the Connect to Server window. For my purposes, that’s OK — no one else uses my laptop. This just goes on the list of passwords I’ll have to reset if the laptop is ever lost or stolen.
And my list of connections wasn’t secure anyway, because I had to save them all in a text file that I could pull up every time I needed to switch servers. In fact, I found you can get Keychain to remember the password reliably. In the “best practice” steps that you gave (thank you!), add a step 0, derived from your technique (thanks again!): 0.
“Connect to Server” smb://domain;username@server/share To start with a clean slate, you should probably open Keychain Access and delete the network passwords for the server. (step -1) It appears that the alias includes the URL exactly as given when you mounted the volume (look at the contents of an alias file to see). So if you mount the volume with the username, as above, and then create an alias, it’ll contain the right username and will be able to retrieve the password from the Keychain.
( that made me think of this.) Thanks for your tip. Like you, I’ve been annoyed by this for ages. I just couldn’t figure out why my aliases were working fine on one computer and not on another. This is a book for professional web designers and developers who already know HTML and CSS, and want to learn to build sites with WordPress. The book begins with a detailed tour of the administration screens and settings, then digs into server-side topics like performance and security. The second half of the book is devoted to development: learning to build WordPress themes and plugins.
This is the second, much-revised and updated edition of Beginning WordPress 3, with a more accurate title. Everything’s been updated for WordPress 3.6.