Re: Netatalk works/doesn't work

[Alisdair McDiarmid <alisdair@wasters.org>]

On Sat, Nov 20, 1999 at 05:30:11PM -0900, Ethan Benson wrote:
> On 20/11/99 Alisdair McDiarmid wrote:
> 
> >Starting Appletalk Daemons (this will take a while):socket: Invalid argument
> >socket: Invalid argument
> >atalkd: can't get interfaces, exiting.
> >atalkd afpd papd.
> >
> >This causes the Mac on the network to fail to see the server in
> >Chooser (typing the IP address works okay). Bizarrely, the 486
>            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> 
> >doesn't have this problem, boots up cleanly and is seen in
> >Chooser.
> >
> sounds like AppleTalk is not compiled in your kernel (or the module 
> is not being loaded)  Mac Chooser will only see a server 
> automatically if the server is using appletalk, so you can either 
> reconfigure netatalk to not use appletalk at all getting rid of the 
> error, or you can make sure Appletalk is either compiled into your 
> kernel or being loaded as a module before netatalk loads.

This is exactly the problem - insmod appletalk fixed it perfectly.
Thanks!

> personally I would ditch appletalk and make the server TCP/IP only, 
> but if you have stubborn mac users who won't type a IP address then 
> this may not be an option..

It's more like Mac users who wouldn't know an IP if it ICMP
flooded their head. Much easier to just allow point and click.

Thanks a lot,
-- 
alisdair mcdiarmid                            alisdair@wasters.org
[funny how everything i swore i wouldn't change, is different now]