Subject: Re: nbp_rgstr: Connection timed out?
From: sat (satadru@umich.edu)
Date: Wed Apr 26 2000 - 07:21:58 EDT
I would suggest that you make sure that the appletalk network protocol is
available on your system either via module ( and loadedc) or already
compiled into the kernel.
The only other thing that I can think of is that if you're on a separate
network ( no appletalk zones; no macs) , you may have to run yourself as
an appletalk seed router, thought I could be wrong on that.
--On Wednesday, April 26, 2000 12:12 AM -0500 David Blache
<alterego@austin.rr.com> wrote:
> on 4/25/2000 8:14 PM, andrew morgan at morgan@orst.edu wrote:
>
>> On Tue, 25 Apr 2000, David Blache wrote:
>>
>>> Here we go again... ;)
>>>
>>> I've just installed Redhat 6.1 on an AMD machine. I grabbed my netatalk
>>> 1.4b2+asun2.1.3 sources, did a make gcc followed by a make install,
>>> copied the atalkd.conf, afpd.conf, and AppleVolumes.default & system
>>> files to the /usr/local/atalk/etc/ directory, and started
>>> /etc/rc.d/init.d/atalk. I get the following error:
>>>
>>> # starting appletalk deamons: atalkdnbp_rgstr: Connection timed out
>>> Can't register microcosm:Workstation@*
>>> nbp_rgstr: Connection timed out
>>> Can't register microcosm:netatalk@*
>>> nbprgstr papd afpd.
>>>
>>> I looks as though I may have some network stuff set up incorrectly? Or
>>> maybe this is as simple as fixing something in netatalk's Makefile(s)?
>>>
>>> Can someone give me a clue? Like I said, this is a brand-new redhat 6.1
>>> install, with netatalk 1.4b2+asun2.1.3 sources.
>>
>> Try adding:
>>
>> alias net-pf-5 appletalk
>>
>> to your /etc/conf.modules file.
>
> What does that do exactly? I'm kind of hesitant to do anything until I
> know more about what the problem is. I hope I'm not offending anyone. I
> just want to know what's wrong before I go messing with stuff.
>
> I should note that I do have two ethernet cards installed. But I've done
> little or no configuration for them.
>
> My network is set up so that my Linux box is a manually-configured device
> on the network, with eth0 having the IP: 10.1.0.3, and eth1 having the IP:
> 10.1.0.4. I just went into linuxconf, gave both eth0 & eth1 these
> respective IPs. And that's about the extent of any configuration I did
> for them.
>
> I can ftp and telnet to 10.1.0.3, so I know that that IP is working ok.
> But I have no idea about the other right now. And I don't know if this
> has any bearing on the problem. But I thought it would be better to be
> safe and mention it.
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:30:31 EST