Currently Being ModeratedMar 28, 2012 12:19 PM (in response to Dips5565)
A NAS is a self-contained server in its own right. Typically Windows users connect directly to the NAS via SMB protocol and Macs via AFP protocol although in theory Macs can connect via SMB as well. The NAS device can either define its own interna list of login names and passwords or it can be connected to a Windows Active Directory system.
It is also possible to in theory have (in this case) a Mac server connected to the NAS, and for the Mac server to 're-share' it to the clients. In this case the Mac and Windows clients would connect to the Mac server and not directly to the NAS. In this case the login names would be defined on the Mac server. The Mac server can act as both an AFP and SMB server.
Many NAS devices had problems initially when Lion was released as Lion introduced changes to the AFP protocol. Most if not all have upgraded their software to fix this but I don't know about Iomega. However if you are connecting to the Lion Server from a Mac client this would not affect you. There was also some issues initially with Lion having a new implementation of SMB, this meant some problems connecting to Windows machines, newer Lion updates have much improved this so make sure you have upgraded your server to 10.7.3.
What you should be doing is -
- Have the Mac server setup with user accounts for each user
- Have the Mac server connect to the NAS via iSCSI
- Have the Mac server re-share the NAS volume via both SMB and AFP
- Have the clients login to the Mac server using their individual user accounts and make sure they are not trying to connect to the NAS directly. You may find it helpful to turn AFP and SMB off on the NAS to stop this.
What iSCSI initiator are you using on the Mac server? Again when Lion first came out there were problems, make sure you have upgraded to a Lion compatible version.
Currently Being ModeratedMar 29, 2012 1:51 AM (in response to John Lockwood)
Many thanks for your reply. You have provided me with alot of information.
All makes sense, however just one question. Users at the moment are connecting to a windows server in general for sharing and authentication etc...
Only a few users require access to the NAS via the Mac server. Currently they all access the share via one user account. This works however when users try to make changes to a document or folder it comes up with an error regarding permissions. Is it possible to just set a few users up on the Mac server for access to the NAS? Would that work rather than actually binding AD to the Mac server?
Currently Being ModeratedMar 29, 2012 2:48 AM (in response to Dips5565)
The Iomega NAS can be bound to AD, this would then let you use the Windows logins to login to the NAS. However if curently they are all using the same single account to login then they should all have the same permissions and be able to access the files with no problems. If the connection is being lost and needing to be restablished then that is not a permissions issue but more likely a problem with the iSCSI setup. If the connection is reliable but permissions are going wrong then that is something else and since you are using just one account I am note sure what the cause is.
A possible ideal approach would be for both the Mac server and the NAS to be bound to the AD, then clients can login and everything will be using the same accounts.
Other than that, I would look at the NAS setup itself and see what the overall permissions are,see if there is an option to set the default to be Read/Write. Also try making sure that at least a single account matching the one you are using to login to the Mac server exists and is identical spelling and password. The clients will be logging in to the Mac server with that, and the Mac server will then be using that to assign ownership on the NAS, however if it does not exist on the NAS possibly this then results in a non-working ownership. If the NAS and Mac server were all using AD this would of course not happen.