You mention it is/was a work account. Also that it is a managed account. Would you happen to be connecting up to an Active Directory or other directory account? If so, your directory server could be specifying that your account try and connect up with a network share on login. If your connection is wireless or something that passes login credentials in order ...
You will still need local and Active Directory administrator account for this to work, but here's the exact steps I took to fix this issue.
Login with local administrator account
Go to System Preferences > Users & Groups
Press Login Options > Unlock > Press Edit near Network Account Server > Open Directory Utility > Unlock > Select Active Directory and ...
I have encountered the same issue with our Mountain Lion image for our Macbook Pro machines when they are connected to our (2008 R2) Domain. When connected they are able to Administer, but when disconnected the ability to Administer is removed. I even enabled administration by the Domain Users Security Group, but this did not help.
What I do to correct this ...
According to the postgres output, you need to run the postgres server as the same user that creates the database with initdb.
mr-clean:~ smurf$ initdb /usr/local/var/postgres -E utf8
The files belonging to this database system will be owned by user "smurf".
This user must also own the server process.
That means the same user will need to launch the ...
Interestingly, I found a solution for my issue after some testing. In the hope that it helps someone else, this is what I found.
My initial, and many subsequent logins on the device were just Username & Password, and this just stopped working. When I tried domain\username and password it sailed through, asked me to update my keychain, and I was logged ...
I have done the same thing a number of time for the same reasons.
In what follows I assume you are running macOS High Sierra or later. If that were not the case, some paths and preference pane options might be different.
What I have found is that using the same Apple ID on both the old and the new machine/install already goes a long way. Just make sure to ...
Alas I never did figure out the cause of this. Due to the nature of where the machine was, I could only work on it for a few minutes at a time in a "test - didn't work - go away and try the fix from a SSH terminal in another room" sort of way.
For the poor unfortunate soul who finds this in the future, the only thing that seemed to fix it was installing a ...
Autosave is not working, you might not have sufficient permission on that volume. You should try rebuild the permissions or take the folder ownership using chown -R.
"… does not support permanent storage" means Versions is not working because the volume is not HFS+, it must be NTFS or FAT and you are using a protocol such as smb.
Apps who aren't using ...
For the record, Airdrop only works if you have one of these Macs, and a supported iOS device:
"To send items to an iPhone, iPad, or iPod touch, or to receive items from those devices, you need a 2012 or later Mac model with OS X Yosemite or later, excluding the Mac Pro (Mid 2012)."
iPhone 5 or later
iPad (4th generation) or later
iPad mini or ...
The inherent problem with using command line tools like scp or sftp is that even after you get your external IP address, you need to configure your firewall/router to allow that traffic to get to your computer. But do you control (own) that firewall/router? If you don't, then how do you make the connection?
Have you tried Skype?
I once used Skype to ...
You will need to figure out if it is a logical or physical issue. Protocol incompatibility is a common cause of these failures, maybe the router reset and configured itself into an incompatible protocol ("802.11 n Only" for example). Sometimes the network connections utility itself is the problem, to discard this you can type airport -s in the "Terminal" app ...
Sounds like there are multiple entries with your user account in the access control list of the share.
Unless you're experiencing performance/functionality issues, I recommend contacting the person who administers that share, letting them know about what you found, then ignore it. :)
If you're experiencing performance/functionality issues, find out if ...
You do need to do some Directory Services magic because normally /etc/passwd doesn't really exist on a Mac and is being created each time you access it from the records in Open Directory.
To remove your users from the terminal, run:
dscl . -delete /Users/username
Where username is the user you want to remove.
Otherwise, you should be able to do this from ...
I have a Mavericks server with this issue, I have found that if a client is using Mountain Lion or earlier, it resets fine. But Mavericks or El Capitan... no dice. So bizarrely, it may in part be a client issue. Hope that helps you get to the bottom of it.
It's possible that you need to set the Authentication Search Path inside of Directory Utility -> Search Policy -> Authentication...Make sure "Search" says "Custom Path", and that your Active Directory domain is listed below.
If you do not see your AD domain in the list, you can authenticate to Directory Utility by clicking the lock in the lower-left corner, ...
If you see something similar to:
sshd: Authentication refused: bad ownership or modes for directory /Your/Home/Path
You have a home directory permission problem.
change to that user if not already one and execute:
chmod go-w ~/
chmod 700 ~/.ssh
chmod 600 ~/.ssh/...
It was Little Snitch :-(
I found the solution here https://discussions.apple.com/thread/4676595?start=0&tstart=0
First I put LS into silent mode, allowing all connections, but did not help. Then I disabled it completely and login worked.
Then at the new user login it reported that there were connections attempts during logon, I examined these, set them ...