Problem connecting with Netatalk 2.0

[Jim Arnold]

I upgraded netatalk from 1.5 to 2.0 and now cannot
connect to my FreeBSD box.

I've altered the netatalk.sh file to this:

netatalk_enable=${netatalk_enable-"YES"}
atalkd_enable=${atalkd_enable-"YES"}
papd_enable=${papd_enable-"NO"}
cnid_metad_enable=${cnid_metad_enable-"NO"}
afpd_enable=${afpd_enable-"YES"}
timelord_enable=${timelord_enable-"NO"}

When I start netatalk I do get this warning - 

spike# /usr/local/etc/rc.d/netatalk.sh start
dc0: multicast may not work correctly.

- but it then starts up

jim     72165  0.0  0.7  4044 1740  ??  I     9:41AM  
0:00.01 /usr/local/sbin/afpd -s
/usr/local/etc/AppleVolumes.system -f
/usr/local/etc/AppleVolumes.default

root    72163  0.0  0.6  4036 1564  ??  I     9:41AM  
0:00.01 /usr/local/sbin/afpd -s
/usr/local/etc/AppleVolumes.system -f
/usr/local/etc/AppleVolumes.default

When I connect from my Mac (10.3.5) I get the dialog
box to enter in my login and password
for the volume on the FreeBSD box, but the box to
select the volumes I want to mount is empty.
I do have a tilde at the end of the
AppleVolumes.default file.

I tried to use NFS and it worked without a hitch,
except transferring files to the FreeBSD box via NFS
is
MUCH slower than using netatalk. I still have another
box running the older netatalk so I could time a file
copying to each system and was surprised to see how
slow NFS is compared to using Netatalk.

Any ideas what I'm missing?

Thanks,
Jim


		
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com