I've just done this. I had Samba providing SMB access but we started a 3
month project and the users on the project were Mac users. I just installed
netatlk1.4b2+asun2.1.3-7.rpm, made a change to the start up script to make
sure it loaded appletalk.o and now I have both Mac and PC users accessing
the same share.
I didn't worry about encryption etc because it's all behind our firewall.
The problems I had were:
a) It was confusing at first whether I should use just the netatalk labelled
non beta (which doesn't have asuns extensions) or 1.4b2 with asuns
extensions
b) I had trouble compiling it but found an rpm
(netatalk-1.4b2+asun2.1.3-7.rpm) that installed onto RH6.2 very nicely.
(Being stubborn I also got it compiled but I didn't need it by that stage).
c) atalkd wasn't starting because the appletalk.o module wasn't loading. I
added a line to the /etc/rc.d/init.d/atalk script to load the module first.
d) Although I had read that Mac was limited to 8 char passwords I didn't
heed it and so had to cut down the passwords to 8 chars
e) Users on the Macs created a number of sub directories with names
containing slashes. The PC's could not see these. ie. don't use slashes in
names.
f) The Macs printed postscript dumps but I got it to work bu altering font
download options. ie. I told the Mac driver to download all the fonts and it
was fine (it was only a little Hp IIP.
g) Not having touched a Mac for about 5 years (thank God) I had trouble with
the dhcp. All my PCs just plug in and dhcp their ip. domains etc. The Macs
didn't seem to be picking these up so I just set them manually (it's only a
3 month project)..
h) I had to reconfigure my directory permissions so that the group was
forced for the Mac users. Samba handles this in it's config but netatalk
relies on the parent directory permissions and the current user id.
All seems to be working well and both Mac and PC users are now filling up
the storage space on the file server at a horifying rate.
good luck,
Wilson
----- Original Message -----
From: "Moritz Kaiser" <[EMAIL PROTECTED]>
To: "Andrew J. Hutton" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, July 11, 2000 1:14 AM
Subject: Re: Re-Exporting via SMB/NFS
> On Mon, 10 Jul 2000, Andrew J. Hutton wrote:
>
> > I would like to hear about anyone's experience getting Netatalk
> > volumes re-exported via SMB so that both Windows and Mac clients
> > can share access to the same files. Please cc: my personal mail
> It ist possible.
>
> Some caveats:
> Depending on the level of security you want in your LAN, you will have to
> select different authentication mechanisms. If you want encrypted
> SMB-Passwords, you need seperate password databases for netatalk and
> samba.
>
> If you have your netatalk configured to save the resource fork, every user
> will see the ".AppleDouble"-directories in his browser in Win **; also
> .AppleDesktop and other stuff. This will not lead to serious problems
> AFAIK.
>
> Samba offers a bigger variety for defining access rules and group
> permissions. You will have to figure out the sense of every measure for
> your purpose.
>
> If it is needed I can send you my smb.conf and other info.
>
> Regards,
> Moritz
>
> __________________________________________________________
> Moritz Kaiser
> Studentische Vertretung, Technische Universitaet Muenchen
> Europe / Germany
>
>
