Jump to content

Configure Netatalk for AFP


Gatch
 Share

Recommended Posts

We are a graphic arts class in a Florida correctional institution. We have approximately 20 computers, both PC's and Mac's. Our server has been using Mandrake 8.2 for the last year and a half. It has worked very well as a file server and an "intranet" apache server. Netatalk AFP worked well in 8.2. When we switched over to Mandrake 9.2 and tested Mandrake10.0, we could not get AFP to work in netatalk so we reverted to TCP which works fine. Below are the active portions of our netatalk configuration files.

What do we need to reconfigure to make AFP work in Mandrake 9.2?

 

afpd.conf

# CONFIGURATION FOR AFPD

# default:

- -tcp -noddp -uamlist uams_clrtxt.so,uams_dhx.so -nosavepassword -admingroup adm

 

#These lines are not in the actual conf file: We turned off -ddp because it was not #working. The Mandrake 8.2 file started - -notcp –ddp when AFP worked.

#-tcp works well but we would like to have AFP working in Mandrake 9.2.

 

 

AppleVolumes.default

#

 

/home/local/samba-quickshare "quickshare" options:mswindows allow:@adm,@advusers rwlist:@adm,@advusers

/home "admin" options:mswindows allow:@adm rwlist:@adm

/home/local/archives "archives" options:mswindows allow:@adm rwlist:@adm

/home/local/tutorials/Mac "tutorials" options:mswindows allow:@adm,@users rolist:@users rwlist:@adm

~

 

netatalk.conf

# Appletalk configuration

# Change this to increase the maximum number of clients that can connect:

AFPD_MAX_CLIENTS=20

 

# Change this to set the machine's atalk name and zone.

# NOTE: if your zone has spaces in it, you're better off specifying

# it in afpd.conf

#ATALK_ZONE=@zone

ATALK_NAME=`echo ${HOSTNAME}|cut -d. -f1`

 

 

# Change this to set the id of the guest user

AFPD_GUEST=nobody

 

# Set which daemons to run (papd is dependent upon atalkd):

ATALKD_RUN=yes

PAPD_RUN=yes

AFPD_RUN=yes

TIMELORD_RUN=no

 

# Control whether the daemons are started in the background

ATALK_BGROUND=no

 

 

 

atalkd.conf

# This turns on transition routing between the le0 and le1

# interfaces on a Sun. It also causes atalkd to fail if other

# routers disagree about it's configuration of le1.

eth0 -phase 2 -net 0-65534 -addr 65280.71

 

Thanks!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...