Currently Being ModeratedJan 24, 2014 5:28 PM (in response to Fezjez)
Not much in your post to go by...
In general, just because a device it attached to the server that doesn't automatically make it available to clients. You have to identify the volume(s) to share over the network via the Server admin apps.
However, since one volume works and another doesn't, I kind of assume you know this, and have done it for one, which begs the question of why you haven't done it for the other.
The other missing data is how you're trying to access the volumes... what protocol are you using from the client? AFP? FTP? NFS? something else? That can also make a difference.
Currently Being ModeratedJan 27, 2014 2:07 AM (in response to Camelot)
Thanks Camelot. Unfortunately I didn't set up the server. We have a LAN with ethernet connection (just 4 computers plus server). The hard drive that currently has the problem, used to be shared without problems, via the server. However the volume was re-named, and set up by an admin guy who we get in to help occasionally. It's since then we've had the problems.
My knowledge is a bit limited in this area. I haven't looked at server admin yet (which I guess, should have been the first place to look). I will feed back once I have.
Currently Being ModeratedJan 27, 2014 2:27 AM (in response to Camelot)
OMG that was so easy to sort! It was just a matter of going ionto server admin and clicking the "share" button. Thanks for pointing me in the right direction Camelot.