I have 2 interfaces. eth0 is my internet conection. eth1 is my local LAN. I tried stiking eth1 on a line by itslef, as you said, but it didn't make a change. Then I tried eth0, just for trying, same thing.
On both cases the /etc/atalk/atalkd.conf remained unchanged, after rebooting atkd.
Also, I don't understand why the zip_getnetinfo goes to eth0 all the time. Is this relevant?
Thanks for your help,
----- Original Message ----
From: Rory Campbell-Lange <rory@...>
To: Erasmo Acosta <eacosta@...>
Sent: Wednesday, June 28, 2006 4:13:37 PM
Subject: Re: [Netatalk-admins] "nbp_rgstr: Connection timed out" Starting Netatalk on Fedora4
On 28/06/06, Erasmo Acosta (eacosta@...) wrote:
> I just built and installed Netatalk 2.03 on FedoraCore4. When I try to start it, using "service atalk start", I get the following error message:
> [root@... netatalk-2.0.3]# service atalk start
> Starting AppleTalk services:
> Starting atalkd: [ OK ]
> Registering neo:Workstation: nbp_rgstr: Connection timed out
> Can't register "neo:Workstation"@*
> Registering neo:netatalk: nbp_rgstr: Connection timed out
> Can't register "neo:netatalk"@*
I believe this is relevant (from http://netatalk.sourceforge.net/netatalk-1_5-faq.txt):
Q23: The daemons aren't starting, things aren't showing up in the Chooser,
and I get a message like this in the logs: afpd[####]: Can't register
This is sometimes a result of missing NIC information in the atalkd.conf
file. Put your network interface (something like le0, eth0, fxp0, lo0)
alone on a line in atalkd.conf, and reboot. When atalkd starts, it will
populate the file with a line such as...
stick 'eth0' on a line by itself and restart netatalk; see how you get on.