Ticket Options
Question Details
TICKET ARCHIVE -> Afp And Osx Server
Tinto - May 17, 2005 - 7:05 am
I have an OSX server running 10.3.5 that exports a volume via AFP for our Mac clients(OSX 10.3.8) and via samba for our Win2ksp4 clients. I have created a mount point on this exported volume, with which I mount a Linux volume. The reason I did this is to make the Linux volume and the exported volume appear seamless to our users.
This works perfectly on the Windows clients, but it's a different story on the Mac clients. On the Macs, the mount point does not appear via the Finder nor via the Terminal. I was wondering what the reason for this and if there is a workaround.
I have tried mounting the Linux volume using afp, smb and nfs but to no avail. Thanks for your help in advance.
This works perfectly on the Windows clients, but it's a different story on the Mac clients. On the Macs, the mount point does not appear via the Finder nor via the Terminal. I was wondering what the reason for this and if there is a workaround.
I have tried mounting the Linux volume using afp, smb and nfs but to no avail. Thanks for your help in advance.
Go3iverson - May 17, 2005 - 2:12 pm
What are you using to share your volume for Linux? NFS?
--------
Michael Dhaliwal, ACSA
www.district13computing.com
--------
Michael Dhaliwal, ACSA
www.district13computing.com
Tinto - May 18, 2005 - 5:37 am
I've tried sharng the linux volume with NFS, Samba and afp but with the same outcome.
Go3iverson - May 18, 2005 - 6:04 am
Ok and what variety of Linux is attempting to connect to this share? Sorry, I should have asked earlier! 
--------
Michael Dhaliwal, ACSA
www.district13computing.com
--------
Michael Dhaliwal, ACSA
www.district13computing.com
Tinto - May 18, 2005 - 6:14 am
Redhat 9
Go3iverson - May 18, 2005 - 6:49 am
Ok, so the Linux volume is being shared to both Linux clients and OS X clients as well? What format is this volume in? (UFS, HFS+, etc)...
To check on your NFS sharing, check to be sure that the share is actually being published to your clients. Use showmount -e serverName/IPHere to be sure its seen properly by your OS X clients. The next step would be to attempt to mount it via command line, which would look something like sudo mount -t nfs ServerIP:Path/To/Share /local/mountpoint
--------
Michael Dhaliwal, ACSA
www.district13computing.com
To check on your NFS sharing, check to be sure that the share is actually being published to your clients. Use showmount -e serverName/IPHere to be sure its seen properly by your OS X clients. The next step would be to attempt to mount it via command line, which would look something like sudo mount -t nfs ServerIP:Path/To/Share /local/mountpoint
--------
Michael Dhaliwal, ACSA
www.district13computing.com
Tinto - May 18, 2005 - 7:26 am
Thanks for your help.
I don't think you quite understand what I'm trying to do and what is going wrong. My fault as I probably didn't explain it well enough.
I have a OSX server. It's sharing a local HFS+ volume (called HRAShare) via AFP to the Mac clients and the same volume via smb to the windows clients.
I also have a separate linux server that has a local volume that I would like shared to our Mac clients and to our windows clients too.
The aim is that for users on the mac and windows clients, the linux volume will seem like just another folder on the OSX server, within the OS X shared volume - HRAShare.
To avoid linux server authentication problems and to make the OSX volume and linux volume appear as a single filesystem to the clients, I have mounted the linux volume on the OSX server on a mount point that is fairly deep within the OSX server's shared volume, HRAShare.
Now with the Windows clients, this works perfectly well. The linux volume does indeed appear to be just another folder on HRAShare with the permissions I set totally intact. However, with the Mac clients, the mount point folder does not appear at all, either via the finder or the terminal. So, you cannot access the linux volume on the mac clients. Accessing the linux volume from the OSX server is perfectly fine though.
I hope this makes sense now...
I don't think you quite understand what I'm trying to do and what is going wrong. My fault as I probably didn't explain it well enough.
I have a OSX server. It's sharing a local HFS+ volume (called HRAShare) via AFP to the Mac clients and the same volume via smb to the windows clients.
I also have a separate linux server that has a local volume that I would like shared to our Mac clients and to our windows clients too.
The aim is that for users on the mac and windows clients, the linux volume will seem like just another folder on the OSX server, within the OS X shared volume - HRAShare.
To avoid linux server authentication problems and to make the OSX volume and linux volume appear as a single filesystem to the clients, I have mounted the linux volume on the OSX server on a mount point that is fairly deep within the OSX server's shared volume, HRAShare.
Now with the Windows clients, this works perfectly well. The linux volume does indeed appear to be just another folder on HRAShare with the permissions I set totally intact. However, with the Mac clients, the mount point folder does not appear at all, either via the finder or the terminal. So, you cannot access the linux volume on the mac clients. Accessing the linux volume from the OSX server is perfectly fine though.
I hope this makes sense now...
Go3iverson - May 18, 2005 - 10:05 am
Ahhhh, I knew something wasn't adding up here!
So here are a few things to look at...
First, be sure that the NFS export is mapping root to root and that the export is restricted to the single OS X Server acting as a client. You'll then want to create a reshares directory at the root level of your OS X Server. You can do this in the terminal very easily with the command:
sudo mkdir /nfs_reshares
Now, you'll want to create subdirectories in /nfs_reshares for each volume that you'll want to share out over AFP. Again, keep that terminal window open and use the following command:
sudo mkdir /nfs_reshares/
Obviously, substitute for the name you wish to use for sharing purposes.
On the OS X Server that's sharing this volume out over AFP, you'll want to create a static mount for the NFS export. For this, you'll want to use NetInfo manager, located in Server HD -> Applications -> Utilities. Create a new subdirectory and add in the following information:
name::
vfstype: nfs
dir: /nfs_reshares/
Make sure to lock up your Netinfo Manager when your done. In the confirmation dialogue, be sure to select the Update This Copy option.
At this point, you can do one of two things. You can reboot your OS X Server, as you've created a static mount record in the local Netinfo database. This is a nice test to be sure that the record was created properly. You can also use the terminal to mount the record manually. To do this, you'd use the following command:
sudo mount_nfs: /nfs_reshares/
Now you can use Workgroup Manager to properly share out the volume over AFP. All of that in a mere 100000 easy to understand steps, right?
--------
Michael Dhaliwal, ACSA
www.district13computing.com
So here are a few things to look at...
First, be sure that the NFS export is mapping root to root and that the export is restricted to the single OS X Server acting as a client. You'll then want to create a reshares directory at the root level of your OS X Server. You can do this in the terminal very easily with the command:
sudo mkdir /nfs_reshares
Now, you'll want to create subdirectories in /nfs_reshares for each volume that you'll want to share out over AFP. Again, keep that terminal window open and use the following command:
sudo mkdir /nfs_reshares/
Obviously, substitute
On the OS X Server that's sharing this volume out over AFP, you'll want to create a static mount for the NFS export. For this, you'll want to use NetInfo manager, located in Server HD -> Applications -> Utilities. Create a new subdirectory and add in the following information:
name:
vfstype: nfs
dir: /nfs_reshares/
Make sure to lock up your Netinfo Manager when your done. In the confirmation dialogue, be sure to select the Update This Copy option.
At this point, you can do one of two things. You can reboot your OS X Server, as you've created a static mount record in the local Netinfo database. This is a nice test to be sure that the record was created properly. You can also use the terminal to mount the record manually. To do this, you'd use the following command:
sudo mount_nfs
Now you can use Workgroup Manager to properly share out the volume over AFP. All of that in a mere 100000 easy to understand steps, right?
--------
Michael Dhaliwal, ACSA
www.district13computing.com
Tinto - May 18, 2005 - 10:31 am
Thanks for your answer but we have already pursued this solution and have came up against some limitations with AFP exports on an OSX server. For example, we can't seem to mount more than one Group folder at a time, which seems to me a very strange limitation. We are already exporting HRAShare via AFP to our users and if we add another Group with another group folder (ie the Linux volume), we're given the choice of which Group to use upon login in.
Go3iverson - May 18, 2005 - 10:53 am
Ok, so the option of which group to use at login...are you saying that your using this AFP reshare as a group folder via MCX data then?
--------
Michael Dhaliwal, ACSA
www.district13computing.com
--------
Michael Dhaliwal, ACSA
www.district13computing.com
Tinto - May 18, 2005 - 11:12 am
MCX data?
We tried your solution as workaround to our initial problem but came up against a brick wall in that we can't seem to export the Linux NFS mounts via AFP using the Workgroup manager as well as exporting HRAShare via AFP. I must be missing something as you *must* be able to have users mount more than one AFP share upon login in. It seems ridiculous that you can't.
We tried your solution as workaround to our initial problem but came up against a brick wall in that we can't seem to export the Linux NFS mounts via AFP using the Workgroup manager as well as exporting HRAShare via AFP. I must be missing something as you *must* be able to have users mount more than one AFP share upon login in. It seems ridiculous that you can't.
Go3iverson - May 18, 2005 - 1:11 pm
I must be continually misunderstanding you.
When you say "mount more than one AFP share upon login", does that mean upon login to the machine itself? I'm assuming so because you wouldn't expect to receive multiple shares upon login to a specific server, you'd expect to mount each share as needed.
If your trying to set this up as an automount for your clients, you might want to use an Open Directory server and either create automounts for the shares in your LDAP or, if your using Kerberos authentication, simply use MCX settings (managed client) to include multiple AFP shares to mount on login as a managed startup item.
--------
Michael Dhaliwal, ACSA
www.district13computing.com
When you say "mount more than one AFP share upon login", does that mean upon login to the machine itself? I'm assuming so because you wouldn't expect to receive multiple shares upon login to a specific server, you'd expect to mount each share as needed.
If your trying to set this up as an automount for your clients, you might want to use an Open Directory server and either create automounts for the shares in your LDAP or, if your using Kerberos authentication, simply use MCX settings (managed client) to include multiple AFP shares to mount on login as a managed startup item.
--------
Michael Dhaliwal, ACSA
www.district13computing.com
Tinto - May 19, 2005 - 5:02 am
I have to thank you for your help. I'm sorry if I sounded so exasperated towards the end yesterday.
I guess the confusion comes as that I was having two different problems.
So, I'll explain my initial problem again.
I have an OSX server which shares a volume to Mac and Windows clients.
On the server itself, the volume's path is as follows:-
/Volumes/HRAShare
On the Mac clients, HRAShare mounts via afp when a user logs in and the path is as follows:-
/Volumes/HRAShare
This share is managed by the Workgroup Manager tool on the OSX server and mounts for each user because it's the group folder of the group that everyone belongs to.
On the Windows clients, the share is mounted via smb and the path to HRAShare is as follows:-
S:\HRAShare
Now, the Linux volume, LinuxShare. This volume is mounted here on the OSX Server and all is fine:-
/Volumes/HRAShare/LinuxShare/CanSeeContentsOfLinuxVolume
On the Windows clients, everything works fine and the path is:-
S:\HRAShare\LinuxShare\CanSeeContentsOfLinuxVolume
On the Mac clients though, problem. Going to
/Volumes/HRAShare via the finder or the terminal and I simply cannot see the LinuxShare. It doesn't exist despite all being well on the OSX server. This is the reason I posed this question on this website. Is this just a limitation of afp?
Looking for a workaround, I discovered Apple's "Resharing NFS mounts via AFP" document. I followed the instructions and all was fine except when it came to exporting LinuxShare via AFP. There seems no way of mounting both HRAShare and LinuxShare upon logging into a Mac client using OSXServer's WorkGroup Manager tool. I would like both Volumes to be available to users upon logging into a Mac client as it's simply easier for users...all their data is stored on these Volumes with none on local disks.
I think I have found a workaround to this. I'm going to mount the LinuxShare by adding the mount commands to the .profile in each user's home directory.
Thanks again for your time and help.
I guess the confusion comes as that I was having two different problems.
So, I'll explain my initial problem again.
I have an OSX server which shares a volume to Mac and Windows clients.
On the server itself, the volume's path is as follows:-
/Volumes/HRAShare
On the Mac clients, HRAShare mounts via afp when a user logs in and the path is as follows:-
/Volumes/HRAShare
This share is managed by the Workgroup Manager tool on the OSX server and mounts for each user because it's the group folder of the group that everyone belongs to.
On the Windows clients, the share is mounted via smb and the path to HRAShare is as follows:-
S:\HRAShare
Now, the Linux volume, LinuxShare. This volume is mounted here on the OSX Server and all is fine:-
/Volumes/HRAShare/LinuxShare/CanSeeContentsOfLinuxVolume
On the Windows clients, everything works fine and the path is:-
S:\HRAShare\LinuxShare\CanSeeContentsOfLinuxVolume
On the Mac clients though, problem. Going to
/Volumes/HRAShare via the finder or the terminal and I simply cannot see the LinuxShare. It doesn't exist despite all being well on the OSX server. This is the reason I posed this question on this website. Is this just a limitation of afp?
Looking for a workaround, I discovered Apple's "Resharing NFS mounts via AFP" document. I followed the instructions and all was fine except when it came to exporting LinuxShare via AFP. There seems no way of mounting both HRAShare and LinuxShare upon logging into a Mac client using OSXServer's WorkGroup Manager tool. I would like both Volumes to be available to users upon logging into a Mac client as it's simply easier for users...all their data is stored on these Volumes with none on local disks.
I think I have found a workaround to this. I'm going to mount the LinuxShare by adding the mount commands to the .profile in each user's home directory.
Thanks again for your time and help.
IF THIS IS YOUR QUESTION AND YOU WISH TO RESPOND, LOGIN HERE FIRST.
