Network accounts!

am trying to setup network accounts in a server with file sharing, but i need to know which services i have to configure before creating the account?
so am gonna start setting up the following:
1) DNS setup.
2) Open Directory (Master).
3) AFP.
my question is about the DNS, to setup the DNS.. there must be a domain?, what if there's no domain and i just wanna create a local DNS .. is that possible?!, how can i do that?!..

Just create your own local domain then, mydomain.net/.com/.whatever

Similar Messages

Cannot login with Network account.

Hi,
I am an experimented Mac user, but quite new with Snow Leopard Server.
I've just purchased the brand new MacMini Server.
I have configured my server with the name server.local and installed OpenDirectory as Master.
I wanted to try the network login, so I created a Test1 account in Open Directory. Then from my iMac I joined my server.local through System Preferences/Accounts/Options/... then I log off and try to use the newly created account test1.... I asked the system to change the password from first loggin... which works, but then I receive a message saying that I cannot log in for the moment... I tried everything but I just can't use the network account.
Any hints?
Cheers.

You should avoid .local at all costs when configuring an OS X Server.
.local is reserved for zeroconfig/Bonjour, and will cause conflicts.
There's an excellent tutorial for new users here
http://www.wazmac.com/serversnetwork/fileservers/osxserver_setup/osxserver106setup.htm
Jeff

Cannot login to network account (leopard client and server)

Up until now, I have used local accounts on my leopard server. I want to start experimenting with OD prior to implementing. I created a new user account in the /LDAPv3/127.0.0.1 domain, and have bound my leopard client to the server using directory utility. On the login screen, "Network Accounts Available" has a green button to the left of it. When I try and login to the server account, the login window just shakes. At first, I could enter the password and then it would prompt me for a new password. Trying to enter a new password would not allow me to login. I went back to server admin and disabled the "require new password" setting, (as well as the other good security policies)...
I have also reset the password in WGM, and made sure to disable all the security stuff there too...
Lastly, I have deleted the server in directory utility, rebooted, then added it back in, and rebooted again...
I still cannot login to the server account, the login screen just shakes
Does anyone have an idea of what settings and or logs I can check to try and narrow down what is going on?
Thanks in advance....

to close out the thread, I have working dns on my network, but I did not have dns enabled on my server. I enabled the dns service and entered just the info for my server, then assigned my server and client to use the server's ip addy as the primary dns server. Next, I created the home directory.
Once both steps were done, I was able to log in from my client to my server based account...
FYI-I found a document on afp548.com called "leopard server: advanced setup, rsync backup and automated reporting" that walks you right thru the process...Here is the link, it's a very useful doc....
http://www.afp548.com/filemgmt_data/files/Leopard%20Server%20Quickstart%20Guide. pdf
thanks again boomboom_uk and woVi, your suggestions were spot on....

One iMac cannot login to network accounts

We have a small network with Lion (10.7.5) Server running on a Mac Pro and a variety of 8 iMacs and Mac minis that use the server for file sharing and network accounts. The client Macs are running a mix of Mountain Lion (10.8) and Mavericks (10.9). They have all 'joined' the 'Network Account Server' using the 'Login Options' section of the Users & Groups preference pane. And, except for one iMac, all the clients can log into network (or mobile) accounts from the server -- both ones that have previously been logged into on that machine and ones that haven't. However, one of the iMacs will not log into a network account. There are a few local accounts and logging into them is no problem. But every time we try to log into a network account on this iMac, the login dialogue just does the 'invalid login' shake. It seems not to check the login credentials with the server.
As far as I can tell, this iMac is set up the same as all the others. It is certainly joined the Network Account Server and there is a green dot by the server name in the Users & Groups preference pane. I have removed and re-added the server from there a few times, and I've even reinstalled Mavericks on this iMac (it is running 10.9.2). I haven't been able to find anything that has helped to solve this problem. Does anyone know why one iMac would refuse to use the network logins from the server when the others work? Or what I can do to gain further information?
Many thanks.

On your client machine login screen, type in ">console" (without quotes) in the username field and hit enter. Try and login with your network account username and password. What error messages do you get in console?
Taylor

Cannot login to network accounts from client computer

Hi. I'm setting up my first OS X Server setup for home use...I'm not creating a very complicated setup, but I've been working through the setup one step at a time.
Right now, I'm just running the DNS, File Sharing, and Open Directory services. I setup a couple of Network User accounts, and I wanted to try using one of the accounts to log in to a Mac client (running Mountain Lion) on the network. When the machine first comes up, I get a message that says 'Network Accounts Unavailable,' and if I try to log in, I get the error message saying 'You are unable to log in to the user account "xxxxx" at this time. Logging in to the account failed because an error occurred.'
If I stop and restart the Open Directory service, I get the following messages in the Open Directory Log:
2013-02-15 09:11:01.017801 EST - Unregistered node with name '/LDAPv3/127.0.0.1'
2013-02-15 09:16:19.139744 EST - Registered subnode with name '/LDAPv3/127.0.0.1'
Not sure if this is the source of the problem, but these are the only messages that are coming up if I turn the Open Directory off and then on again.
If anyone has any experience with this, or any suggestions, I'd greatly appreciate it!
Thanks!
If it helps:
Running OS X Mountain Lion (10.8.2) with Server (v2.2.1)
Client Machine is a VMWare Fusion VM Running Mountain Lion (10.8.2)

On your client machine login screen, type in ">console" (without quotes) in the username field and hit enter. Try and login with your network account username and password. What error messages do you get in console?
Taylor

Cannot login into network accounts when there is no network connectivity

Hey guys
quick question here if anyone can help.
What has been done: backuped user's home folder, binded the mac to AD, logged in as the user's AD name, copied everything from the backup into the new user's home folder, users can work flawlessly.
What is wrong is when they leave the office, after a few hours they cannot login anymore to their AD username. Is there something i missed?
The network accounts do not appear in system preferences.
Thanks

On your client machine login screen, type in ">console" (without quotes) in the username field and hit enter. Try and login with your network account username and password. What error messages do you get in console?
Taylor

Can't Login With Network Account After Upgrade To Yosemite Server 4

I've been putting off this troubleshooting for a while now, and after trying everything I could find, decided to post.
- After upgrading my server to Yosemite with Server 4, and my MacBook to Yosemite, I can no longer login with any network accounts.
- I was on clean installs of Mavericks before the upgrade.
- I'm using SSL for the OD, with a GoDaddy cert, the same one that was working on Mavericks.
- I've tried removing the laptop's binding using the Users and Groups preferences dialog, which does not remove the laptop's entry from Open Directory, so I manually deleted the record on the server.
- I then choose to Join again, and it looks as though everything goes through, but I still cannot login with a network account. Also, when rejoining, it does not create a binding on the server.
- If I use the Directory Utility->Services->LDAPv3, and add it that way, entering the FQDN and checking Encrypt..., Use for auth and Use for contacts, it asks me for the directory admin username and password, and does in fact create the binding on the server, but I still cannot login. What's strange about that method, is that it forces the use of the IP address of the server, rather than the FQDN, like I entered it, which would of course have problems, because the certificate's common name is the server's FQDN. It does not allow me to change from using the IP address, graying out that field.
- I've also tried destroying the OD and restoring from archive to no avail.
It looks like many users have hit dead ends with this, with some having success by completely formatting and setting up a new iteration of the server, but I will not be doing that. However, I'll be happy to try any other suggestions.
Thanks for your time,
   -- Mike

     Okay, I've finally resolved the issue, thanks to the Apple Enterprise tech support team. I'm thinking they wouldn't mind if I share this information, but I can't guarantee that this will work on your system or, worse yet, degrade your system further. However, that's fairly unlikely, just make sure you have plenty of backups before you begin any troubleshooting session.
     So I was told to perform the following instructions, which I did, line for line. The part about closing Server.app seems a given, but I'm not sure why they want you to open Server.app at the the end (maybe taken out of context from some other instructions?). I did it anyway, but you should be able to begin testing, on a client workstation, right after rekerberizing is complete. I did, however, need to reboot my client, login as local admin, and then binding would proceed, and network users are able to login again. The engineer also let me know to expect an error, something like the following: "2015-03-11 21:58:38 +0000 Error synchronizing removal of attribute draft-krbPrincipalACL from record 72519e4c-7ac7-15e4-bd42-10adb1944cbc: 77013 result: 16 No such attribute" - this is apparently normal, and did in fact happen in my experience.
So here's the fix:
- Quit Server.app (don’t just close the window)
- On the Open Directory Server, execute these Terminal commands:
- sudo mkdir /var/db/openldap/migration/
- sudo touch /var/db/openldap/migration/.rekerberize
- sudo slapconfig -firstboot
- Open Server.app
And that's it. I did nothing else on my OD server, just logged out. Immediately tried binding on my MacBook client, it failed, I rebooted, tried again, it worked quickly, and I'm able to login with network user accounts again.

I am trying to figure out how to merge my AD network account.

I am trying to figure out how to merge my AD network account with my Mac account. The main reason for this is wanting to log into my admin account on the Mac, and have it also log into my network account so I do not have to log into differing accounts depending on wether I am on the network or not. And I am going to be running VMware fusion with windows on top, so having one account would be essential to this.
Thanks.
P.S. I am brand new to Apple, not by choice. ;-)

Basically I want to link a network account to a local account, so that I always log into the same account, even if I do not have network access....

Cant login multiple network accounts on the same client?

Setup:
I have created a simple Lion Server on a new i7 Mac Mini. I have configured Open Directory in Master mode and have setup 4 user accounts. I have enabled the File Sharing service and checked the "Make available for home directories" option on the "Users" file share. I have configured each of the 4 user accounts to use this location as the home folder. I have connected my client machines (all OSX Lion) to the Network Account Server.
Problem:
I can log one user into the client machine, but when using "Fast User Switching" and logging on as the second user I get the following error:
"You are unable to log in to the user account "guestaccount" at this time. Loggin to the account failed because an error occured"
In the console if I search for that user account the related error message is:
11-07-31 12:30:54.993 PM authorizationhost: ERROR | -[HomeDirMounter mountNetworkHomeWithURL:attributes:dirPath:username:] | PremountHomeDirectoryWithAuthentication( url=afp://inntaserver01.local/Users, homedir=/Network/Servers/inntaserver01.local/Users/guestaccount, name=guestaccount ) returned 16
Any thoughts as to why the Home Folder "mounter" failed in this scenario?

Historically you have never been allowed to use Fast User Switching to log in multiple network logins on the same client machine. This certainly applied with Tiger, Leopard, and Snow Leopard. I have not yet personally tried this with Lion.
I believe that the underlying reason for this not being allowed is down to how AFP volumes are mounted. The AFP mount becomes 'owned' by the user that triggers the login. With a network login the first user becomes the owner and this means subsequent attempted network logins are denied access to that share and hence cannot access their home directories.
With Tiger, Leopard, and Snow Leopard servers, one could configure network home directories to be shared via NFS instead of AFP. NFS gets treated a lot different in terms of mounting, and is done more at a system level than a user level. While again I have not personally tried Fast User Switching with NFS shared home directories, this approach is specifically recommended by the authors of AquaConnect (a Macintosh Terminal Server solution) in order to allow multiple logins on the same Terminal Server. This seems to be for the same underlying reason. Using NFS does certainly work for use with AquaConnect and also works for the competing iRAPP Terminal Server product as well.
Unfortunately, Lion Server while it can be made to run an NFS server, will not let you configure using NFS for sharing home directories. I have actually reported this as a 'bug' in Lion server.
Neither the authors of AquaConnect or iRAPP have actually tested this scenario with Lion server yet, but AquaConnect do plan to investigate it. It could make it considerably more difficult to use their products.
So in summary, using NFS to share network home directories in theory would avoid the problem and can be done with a Tiger/Leopard/Snow Leopard server, but cannot be done with a Lion server. It is possible however to mix Lion with older server versions. This might for some people be a possible workaround.
PS. A bonus side-effect of using NFS shared home directories was that this allowed badly written software like Adobe's applications which are otherwise notorious for having major issues with network logins and home directories to work without errors. As an example Adobe Acrobat Pro introduced a bug in version 7.0 which prevented it being able to print-to-PDF (one of the major reasons to buy Acrobat Pro). It tooks two years for them to eventually fix this in Acrobat Pro 8.1 (I know because I spent that two years nagging them to fix it and was a beta tester). Unfortunately they then reintroduced the bug in Acrobat Pro 9.0. Fortunately I discovered this side-effect got round the issue although a clunkier workaround was also possible for Snow Leopard clients by redirecting certain folder paths.

Migrate a Local User Account to a Network Account Shell Script

http://support.apple.com/kb/HT5338?viewlocale=en_US&locale=en_US
If you are looking for an easy way to migrate local users to network users without losing data, then try this script.
Follow steps 1-10 in the support link above before running this script.
1) Open /Applications/Utilities/Terminal.App
2) Type vi myscriptname.sh
3) type "i" to edit the document
4) Copy and paste the following text in the terminal window
#!/bin/bash
echo "Go to http://support.apple.com/kb/HT5338?viewlocale=en_US&locale=en_US"
echo "Complete steps 1-10 before continuing"
echo -n "Enter 'USER' and press enter:"
read USER
echo -n "Enter 'SERVER' and press enter:"
read SERVER
sudo scp -Epr /Users/$USER root@$SERVER:/Users/
sudo mv -f /Users/$USER /Users/$USER.old
ssh root@$SERVER sudo chown -R $USER:staff /Users/$USER
5) hit (ESC) then colon : and type wq! and hit return to save the document
6) In Terminal type: chmod +x myscriptname.sh
7) in Finder, Right Click or Control+Click myscriptname.sh and select open with
8) Select "Show All Applications" and Navigate to /Applications/Utilities/terminal.App
9) in Finder, Right Click or Control+Click myscriptname.sh and select get info / Open with and click "Change All" to open all .sh files in Terminal
10) Double Click myscriptname.sh
11) For USER enter the name of the network account
12) For SERVER enter your server name (server.example.com)
13) Enter the Admin Pass for the Local Machine, Then the Server, Then the server again
14) The user folder will be renamed to user.old (bob.old)
15) When you login as the network user account OS X Server Will copy your data to the local machine with Portable home directories
16) Once you verify all the info is there you can delete the user.old folder from the /Users/ folder (bob.old)

replace sudo scp -epr with sudo rsync -auvth if you do not want to waste space copying hardlinks

How can I uniquely identify computers on the same network/account specifically for airdrop use? When I change name on one computer under contacts if changes on all computers.

How can I uniquely identify computers on the same network/account specifically for airdrop use? When I change name on one computer under contacts it changes on all computers. I would like to change icon and name for each computer.

you would need to setup a VPN and tunnel into your office.
FYI..the default ports are 3283 and 5900.

How do I make a new network account visible to a client at login?

I have just installed a new Leopard Server machine. It is an Open Directory master and I have created a number of new accounts with network home folders. On my client machines I have identified that OD server using the Directory Utility program. Yet when I log in from any of my Leopard client machines I only see local accounts, not the network accounts.
What am I missing?
Ian.
--

Did you set up your accounts on the server to be mobile or network home accounts?
I believe they are network home accounts. For example, for the user fred I have a folder on the server hard disk called /Volumes/disk1/Users/fred, which I created as the home folder when I created the user account.
There is a folder called "fred" visible at /Network/Servers/penguin.example.com/Users/fred/ from the client computers.
DId you set your sharepoints up to be automount?
I believe so. In the above example the folder /Volumes/disk1/Users is marked as a share with "Enable automount" selected and marked "Use for User home folders".
Did you bind your computer in DIrectory Utility?
Well, on each of the client computers I have used the Directory Utility program to connect to the OD server. Does that constitute binding?
Is DNS resolving properly?
Definitely. I can ping all of the computers, including the new server, from any of the computers on the network.
I should have mentioned that I had done these things - sorry about that. Anyway, I'm stumped. Anything else to try?
Ian.
--

Can't login on iMac to Local Network accounts on server

I'm a volunteer at the Marjorie P Lee retirement community. We had two iMacs that were available for residents to use. We recently bought two more iMacs and a Mac Mini Server. The goal is to make it possible for residents to use any of the computers and have their files available.
I have set up the server and did the updates so the machine is running 10.9.4 and the latest update of the server software. I have enabled Open Directory and created a couple of Local Network User accounts for testing. I also enabled file sharing and Time Machine backups.
One of our older iMacs is running OS X 10.6.8. On this iMac, I went to the Users & Groups pane and under Login Options I connected to the Network Account Server. I got the green dot indicating that the connection was successful. I then enabled network logins. This worked; I am now able to login on this iMac to the local network accounts on the server.
I did exactly the same thing on one of our brand new iMacs. Again I got the green dot indicating a successful connection to the server. Unfortunately I have been unable to login to the local network accounts from this machine. When I try to login, the password shakes as though I had entered the wrong password.
What do I need to do to fix this?
Thanks for any help you can provide.
~~Dan

Most likely your Imac is using g or n to broadcast wirelessly while your router is using b. Solution update your router.
Greetings from Northern Ontario, Canada

Lion Server network accounts not working on some computers.

Hello all -
I'm currently having an issue with network accounts working on some Macs but not others. I have a Mac Mini and a MacBook Pro. The Mac Mini works fine and I can login and sync my network account with the server just fine. However, I cannot connect to it from my MBP.
When I try and connect I get an error that says "You are unable to log in to the user account "xxxx" at this time. Logging in to the account failed because an error occurred."
If I login through console (by typing in ">console" in the username field) I get an error that says the user does not have a home directory...
I have searched numourous other forums but I have not found a solution that seems to solve this problem. I have unbound and re-bound my client to the open directory and I have restarted file sharing. Neither has solved the problem. I have a feeling the issue originates somewhere on the MBP since I can log in to the Mac Mini without any problems.
Anymore suggestions?

Thanks for your suggestion, SolidWood. Unfortunately it didn't help.
After a 90 minute phone call with AppleCare, this issue has finally been resolved. Here is what the solution was. Turns out it was pretty simple but it took a while to find it.
First we created a test user and left the home folder set to Local Only in the Server App. I was successfully able to login with the test user on both clients but since there were no mobility preferences set, it was pretty basic.
Then, we removed the Users sharepoint from file sharing, turned off file sharing to disconnect any users, and restarted the server. Then we created a new folder on the Server HD with a random name. We chose Darron. We created a new sharepoint in file sharing (with it still turned off), and shared the new folder called Darron. Double click on the sharepoint and scroll to the bottom and check the box that says "Make available for home directories over AFP". Then we restarted file sharing.
Then we opened Workgroup Manager, clicked on the problem user in the left sidebar, clicked on the Home option at the top, and there were three things listed:
     (None)
     afp://servername.com/Users
     afp://servername.com/Darron
Then we removed the Darron sharepoint from file sharing, and found that it was still listed as a home directory under the problem user.
This was the root of the problem. The system didn't know which path to use as the home directory.
Sooooo...
In the server app, we opened the Directory Utility (Tools in the menubar, Directory Utility). Clicked on Directory Editor. Authenticate to the directory using the diradmin login. Changed view settings to match this below:
In the left column, there were two paths listed for home mounts. We deleted both of them, saved changes, and closed directory editor.
Then, we restarted workgroup manager and both paths had been deleted from the users home listings. This was begining to solve the problem.
In the Server App, we recreated the users sharepoint, made it available for home directories, and restarted file sharing and workgroup manager. Now only one path is listed for the home folder for all the users.
This solved my problem of not being able to login on the MBP. The system synced the home folder and all was well. On the Mac Mini, I had to delete the problem account, un-bind from the network server, re-bind, and recreate the account. Now both clients are sycning perfectly and all is well.
Thank God I bought AppleCare! Thanks to everyone else for their help and suggestions.
As a recap, the problem of not being able to login to the MacBook Pro was caused by having multiple paths to the multiple home folders. These rogue paths were added somewhere in the troubleshooting process to try and recreate the home directories before I called AppleCare. To solve this, we had to remove the directory listings from accounts using Directory Editor, remove and recreate the users sharepoint in file sharing. The syncing problem on the Mac Mini was also created when multiple paths were introduced. The system didn't know which files to use.
Taylor

Is there a way to merge/migrate my local home folder to a network account

My family has a number of Macbooks and a couple of iMacs and we've been thinking we'd like centralized storage for our media collection and other files and I'd like an easier way to deal with these machines to keep them updated, etc. Also we swap laptops and desktops depending on who needs to do what at a particular moment. Is there a way to migrate an existing home folder on a macbook to an account on the server. What I would like to be able to do is to be able to log into any computer in my home and have it look like "my" computer, with files, settings etc... Since I am new to the server world I am confused by the terminology re: network accounts and mobile accounts. Is there a good guide someone could recommend to get me started. Thanks.

Hi Yodalogger,
I hope you have yourself sorted. I've been through alot of pain with lion server, it's very buggy at best.
Your best bet is SolidWood's suggestion of network accounts if you are constantly on the same network. I use this at home and it works very well. For simplicity, you can use WorkGroup Manager for this as it's more intuitive!
If, you need a mobile account, this is what I did.
I migrated local macbook accounts to server machine (migration assistant).
I renamed the /User home folders on macbook to _backup. For safety.
I deleted local accounts from macbook. Keep your _backup home folders! Also, you will need to have a local Admin account in place. Make sure you do not delete it.
On Server. You will have local accounts created for all your migrated macbook accounts. Just remove the accounts in system preferences but ensure you leave the /User home folders in place when prompted.
On server. I created the new users (old mackbook accounts) and groups in the server app. This doesn't create or overwrite your existing home folders. So go ahead and name them exactly the same as before and make sure the accounts match your home folder's names.
On server, using profile manager, I set up mobility etc., for the device. That is, you need to enroll your macbook with the server and configure services for it in profile manager. You can add a placeholder for this in profile manager to configure stuff.
A handy tip to alleviate all the automatic push settings pain and heartache is to set the general payload to manual. You can then wip up the profile manager from your macbook to install the profiles manually. (easily done).
On Macbook, login with local admin account.
On Macbook, go to system prefs and accounts, set up your open directory stuff in the login options.
On Macbook, log out of admin. Back at the login screen, you should see your admin account and 'Other.' Give it a few minutes or so to figure this out. It needs to contact the server etc. for info.
Once you have 'Other' click on it and login with one of your new network accounts. This will log you in as a network account - you should see all your usual settings that previously existed on your macbook when it was a local account.
At this point, you whip up profile manager. http://yourserver.local/profilemanager Change yourserver to the name of your server.
Login to profile manager with your admin account. I do this as I will be downloading a few profiles that only admin has access to.
So, you need to download a trust profile, your device profile, and a profile for remote management if you have set this up. You may have seen various download buttons knocking around the the interface. In downloads double click these to install (if it doesn't do this automatically).
Log out of everything.
Log back in with one of your network accounts. This time you should be prompted to create a mobile account. Say yes and let it sync your home folders from server to macbook.
Once each mobile account is created, you can then further define user/group settings in profile manager. You download these by logging into http://yourserver.local/mydevices as the user and download the appropriate settings.
I think thats it. Sorry, if its not detailed enough - I'm presuming you know yourself around a mac! I have to say the process is straightforward but Lion Server is not. I do not get consistent results with it and I'm still trying to tame it...
By far the easiest option is network accounts. Mobile accounts need more attention.
I hope this helps (and anybody else!)
Paul.

Mobile Account Preferences visible on Menubar for Network Accounts

On Mobile Accounts (setup with Profile Manager), acting as network account (home folder in server), the mobile account preferences are shown on the menubar. In addion, it says "last home sync" incomplete. Both are wrong according to my understanding.
However it makes sense - and it if the case - if the account is really working as mobile account with local home folder on a e.g. macbook.
Does anyone has the same issue?

I have the same issue. No fix yet.
One of my machines has joined the network and seems to be ok in almost every way...clearly with the exception of this way.
I will post if / when I find a solution.
W

Network accounts!

Similar Messages

Maybe you are looking for