FSM setup

  • Thread starter Thread starter Gene
  • Start date Start date
G

Gene

I have Macs (OS9 and OSX) using AFP to connect to a 2000
server running File Services for Macintosh. How do I set
permissions so that my users see only their shared folder
in the chooser, and not all the rest of the shared folders
that they don't have permissions to access. I've tried the
GUI for FSM and Macfile, but haven't hit the right setup
yet.

Thanks,
Gene
 
Gene said:
I have Macs (OS9 and OSX) using AFP to connect to a 2000
server running File Services for Macintosh. How do I set
permissions so that my users see only their shared folder
in the chooser, and not all the rest of the shared folders
that they don't have permissions to access. I've tried the
GUI for FSM and Macfile, but haven't hit the right setup
yet.
Click to expand...

Hi Gene!

When you open the Chooser, you select the server. When you log into the
server you select a Mac Volume. A Mac Volume is not simply a shared
folder. It is equivalent to a Windows share. All Mac volumes, like all
Windows shares (except those hidden by "$" appended to the end of the
name) are visible to all users. Mac Volumes and Windows Shares are the
doors to your server and don't necessarily need to be hidden unless
you're trying to create secret doors.

What you're probably use to seeing in Windows is an automatic drive
mapping to a user's personal folder where only that person has access.
However, if other users were to browse the Windows share, they would be
able to see the same folder but not be able to access its contents.
Drive mapping is not a feature available to Mac users.

For Mac users you can simply create one Mac volume with multiple folders
and restrict access to only the Owner of each folder to prevent folks
from peering into someone else's folders.

Hope this helps! bill
 
-----Original Message-----


Hi Gene!

When you open the Chooser, you select the server. When you log into the
server you select a Mac Volume. A Mac Volume is not simply a shared
folder. It is equivalent to a Windows share. All Mac volumes, like all
Windows shares (except those hidden by "$" appended to the end of the
name) are visible to all users. Mac Volumes and Windows Shares are the
doors to your server and don't necessarily need to be hidden unless
you're trying to create secret doors.

What you're probably use to seeing in Windows is an automatic drive
mapping to a user's personal folder where only that person has access.
However, if other users were to browse the Windows share, they would be
able to see the same folder but not be able to access its contents.
Drive mapping is not a feature available to Mac users.

For Mac users you can simply create one Mac volume with multiple folders
and restrict access to only the Owner of each folder to prevent folks
from peering into someone else's folders.

Hope this helps! bill
--
William M. Smith
(Microsoft Interop MVP)
.
Bill,
Click to expand...
I created separate Mac volumes and named them with the $
at the end, Macfile permissions 11100000000, but the Macs
still see them all. Maybe there's a reg hack? For business
reasons, our Mac users must only see their own share, and
not know that others exist. I haven't had any trouble
keeping people out of others' shares, but I can't prevent
them from seeing them on the Chooser. This 2000 server is
replacing a Mac for ftp and AFP access. FTP works fine, as
the ftp software only shows the correct shared directory
to the user. The Mac we're using restricts the chooser
display to the user's valid files, and I was hoping that
SFM could do the same. This will be a showstopper on
implementing the new server, so I need a way to hide those
other Mac shared volumes on the Chooser.
Appreciate your help

Gene
 
I have a Mac OS 8.6 client who can't connect to a Windows 2000 server. This
was previously working. Now when he attempts to connect to the server in
Appleshare (chooser), it stalls for abot 3 minutes while authenticating,
then displays a "The connection to this server has been unexpectedly broken"
message. Any help would be greatly appreciated.

Thanks in advance,

-Jason
 
Bill,
Click to expand...
I created separate Mac volumes and named them with the $
at the end, Macfile permissions 11100000000, but the Macs
still see them all. Maybe there's a reg hack? For business
reasons, our Mac users must only see their own share, and
not know that others exist. I haven't had any trouble
keeping people out of others' shares, but I can't prevent
them from seeing them on the Chooser. This 2000 server is
replacing a Mac for ftp and AFP access. FTP works fine, as
the ftp software only shows the correct shared directory
to the user. The Mac we're using restricts the chooser
display to the user's valid files, and I was hoping that
SFM could do the same. This will be a showstopper on
implementing the new server, so I need a way to hide those
other Mac shared volumes on the Chooser.
Appreciate your help[/QUOTE]

Hi Gene!

Inherently, there is no way to hide Mac volumes like you can hide
Windows shares with the "$" appended to the end.

From my experience with an AppleShareIP server, however, I was able to
keep folks from seeing an administrative volume by simply setting my
permissions to not allow users to have access. In a sense, if users
didn't have permission to access the volume, the server didn't show the
users the volume in the volume list after login. I believe my
permissions were something like:

Owner: Administrator
User/Group: myself
Everyone: None

The same may apply for a Windows volume, but I can't say for sure.

Hope this helps and good luck! bill
 
Jason Lehrhoff said:
I have a Mac OS 8.6 client who can't connect to a Windows 2000 server. This
was previously working. Now when he attempts to connect to the server in
Appleshare (chooser), it stalls for abot 3 minutes while authenticating,
then displays a "The connection to this server has been unexpectedly broken"
message. Any help would be greatly appreciated.
Click to expand...

Hi Jason!

Do a quick test by Option+double-clicking the server in the Chooser
list. If this connects then you are connecting via Appletalk and you
have a problem with IP either on your server or on your Mac.

Another test is to use the Server IP Address button in the Chooser and
entering the IP address of the server. If this connects then you're
having a problem with the switch between browsing the server in the
Chooser via Appletalk and then switching to IP.

Also, do your server's Event Logs show anything useful?

bill
 
Back
Top