Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

questions, set up, connecting client computers to server

I am a novice.

I have a small business (dental office) with 11 macs (and 4 at home). Up until recently my network has consisted of stand alone macs and I use file sharing, screen sharing, etc. to do basic network stuff.

As our database grows, I need a more sophisticated network.

I have recently employed some network people to set up Snow Leopard Server. However, they are experts with *_windows server_* networks and have never set up a mac network. There isn't anyone local that I can find who has ever set up a mac network.

So, we began the "easy" set up today and our heads are spinning.

The server seemed to set up correctly, but when it comes to connecting the exisiting client computers to the server, we haven't had much luck and there doesn't seem to be any clear guidance on this.

My assumption is that I should be able to set up users on the server that could then log in on any of the client computers and their preferences, desktop, etc. would appear before them, no matter what computer they were on in the office.

Am I correct in that assumption?

If so, where can we go to find the help we need to get this set up correctly?

Obviously it would be better for them to be asking these questions, since they know the vocabulary and the technical stuff.

What I envision is setting up 3 work groups and several users. My front office staff members could move between three computers, logging in with their log in, and get their preferences, folders, and desktop. All documents would be stored on the server. I would have remote VPN access to the network from my home, having the ability to access our practice management software, patient records, x rays etc. from anywhere in the world, perhaps even my iPhone?

Are these things possible with Leopard Server? If so, where's the missing manual?

Again, our main challenge seems to be figuring out the login of a client computer into the server, or a login that is "hosted" by the server. At this moment, all user accounts remain to be only local accounts.

We have gone into accounts and clicked the "join" button. Some of the computers have even received an "invitation" from the server, and we have attempted to "login" with the user names and passwords we set up on the server, but we don't get what we envision. The computer seems to be "connected" some how, but having a custom account that shows up across computers (like a windows server network) doesn't seem to be happening yet.

We are missing a piece of the puzzle. I realize this post is not very neat, if there is any information I can provide to clear things up, let me know.

Thanks.

iMac intel, Mac Pro, mac mini, macbook pro, Mac OS X (10.6.4)

Posted on Jul 16, 2010 8:37 PM

Reply
25 replies

Jul 20, 2010 2:37 PM in response to David W. Lucas

BTW, to further elaborate.
Again I am coming at this from a PC point of view and trying to draw a parallel.
In the PC domain, when you login to the workstation, you have a choice to either login locally or login to the domain. If you login locally, you would not necessarily have access to network resources. However, if you login to the domain, the server authenticates you and you have access to network resources and local workstation resources. Your domain profile is different from your local profile.
So with the PC, when you login, you see username, password and a drop down box to either login locally or login to the domain. I was expecting to see this as an option on the MAC workstation before logging on. Is this possible? If not, how and when does authentication to the server take place.

Jul 20, 2010 6:19 PM in response to Daniel Peck

The Wazmac tutorial I posted the link to has very good step-by-step detaqils for doing what you want to do. I'm not trying to avoid your question, but I don't want to type everything Warren already did 😉

You mentioned you set up the server. Some potential gotchas, or maybe stuff you wouldn't guess need to be done...
When setting up the server, use the setup assistant to name the server and put in the DNS address, subnet mask, router. Once the setup is complete, configure DNS and start it, unless that's being done elsewhere on the LAN. Once DNS is running, you can test it with
'sudo changeip -checkhostname'

If that's good, you can next turn on the OD service, and promote the server to a OD Master. Next, turn on AFP, use WGM to create groups, make a share for user homes (the directory for roaming profiles in Windows parlance), assign proper privileges using serveradmin and turn on automount for the share. The default is for network user homes - but go through all the settings to make sure they make sense.

You can then go back to Workgroup Manager (used to make users, groups, and manage apps, printers and other user/group/computer settings. When you create a user, under the home tab, your share that you created should show up as a location for the network home.

Your

clients need to be set to use a DNS server (in the setwork system pref) that has records for your server - this can be the server itself unless as I mentioned before, DNS is being done elsewhere. The simplest way is to use the server itself in a small LAN. You can then bind the Mac to the OD Master (the server) in the accounts system pref. There is also a login option in the accounts system pref that can enable/disable automatc login - you want to disable that. In the same place, you can choose between a blank username and password field for login, or display a list of users. I've always used the blank user/login option, so i can't comment on using the user list option, although I know it was sometimes problematic in previous versions.

There may be a way to use the same account name locally and on the network and choose between, as you're used to in Windows, but again, if you have a network account and a local account with the same name, the local account will be used when you login. If there are files that already exist locally, you'll need to copy those to the network home once it is created. If you really want users to have a local and a network profile (the network home/settings/files will follow them to any Mac bound to the server) the simplest way would be to have one local account, say smith, and a network account, like smithj.

Jeff

Check out the wazmac notes and try that - it should work for your setup.

Jul 20, 2010 6:32 PM in response to Jeff Kelleher

Thank You Jeff.

We will restart our adventure with all of the knowledge and resources you and Camelot and the others have provided for us. I am VERY appreciative of the time you have put in to this. We may still have some small questions as this plays out, so I'll leave the discussion open for now.

We really don't need local user accounts except, in the rare occasion, to service a particular client machine.

The goal for me (from my laymen's point of view) is to have user accounts (with preferences etc.) that can be accessed from any computer in my office. And then I wanted all our data in one place for easy back up and security and recovery.

The MacPractice software works regardless of having a real network set up or not. It sort of has it's own server in background app and database. What I needed was a way to centralize files, accounts, and build in flexibility and security and stability. We started having issues with our network, but I started with 3 computers and have gradually built it up to 10+ and it will probably continue to grow.

Eventually I may elect to host our companies website and email from the server too.

Thanks again!

Jul 21, 2010 9:09 AM in response to Jeff Kelleher

Thanks Jeff,
We will take our newly acquired knowledge and work on the network today.
FYI, I did setup the server as the DNS server. DHCP is being handed out by the router, so we reconfigured the router's DHCP to have primary DNS pointed to the server. (I normally setup DHCP on the server, so we may change that later). Then the server is configured to forward DNS request to the ISP primary and secondary DNS for Internet requests. DNS is working great.
FYI, I found out the hard way to NOT give your server and domain a FQDN that ends in .local, as I have done hundreds of time for Windows Networks. Apparantly, Snow Leopard reservers .local for other purposes.
I don't know what OD is? When I set the server up I made it a PDC. Looks like I need to go through the tutorials.
Again, thanks for all the help. You guys have been great!!!

Jul 21, 2010 11:45 AM in response to David W. Lucas

I'd go with DHCP on the server as well.

OS X uses the zeroconfig standards, so .local is out. I don't think you're supposed to use it with Windows either, but you can get away with it on Windows.

OD is Open Directory - the same basic idea as Active Directory, only Apple's version. You mentioned making the server a PDC - do you mean Open Directory master? You'll want to make it an OD master once DNS is working.

Jul 21, 2010 1:07 PM in response to Jeff Kelleher

Jeff,
I can't tell you how many networks and network techs use the .local on Windows networks. I have worked on at least 100 different networks in my area and all of them use .local as the domain name. As a matter of fact, I can't recall seeing a network that didn't. Most of the networks in a domain setup are 150 PC's or less and only 2-4 domain controllers. The majority are small business networks though. 1 SBS and several workstations. Anyhow, I will do some research. Change is the only constant in my world.
After you mentioned OD and I looked it up, I realized that we made a mistake setting this up as a Primary Domain Controller. I realize now that is literally making the server a domain controller so PC can join the domain. We are correcting that this afternoon. I also agree about the DCHP. We have done a lot more research and printed out everything we think we need to complete the job. Again I appreciate all the help, MAC experts, are few and far between.

Jul 26, 2010 2:29 PM in response to Jeff Kelleher

Hi Jeff,
I see your point. I will keep that in mind in the future. I don't have any clients who have a mixed MAC / PC environment and so far none plans on heading in that direction. Daniel is 100% MAC.
Looks like we got everything setup ok. Daniel is busy this week learning and working out the bugs and coming up with a list of things to do for us, if he can't resolve them himself.
Anyways, thanks again for all your help. You all have been great.

questions, set up, connecting client computers to server

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.