Date: Mon, 6 Oct 1997 08:57:16 -0500 (CDT) From: john@vapornet.com To: FreeBSD-gnats-submit@FreeBSD.ORG Subject: ports/4708: broken netatalk Message-ID: <199710061357.IAA00570@nitromethane.vapornet.com> Resent-Message-ID: <199710061400.HAA29811@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 4708 >Category: ports >Synopsis: netatalk is broke. no authorization. >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-ports >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Oct 6 07:00:01 PDT 1997 >Last-Modified: >Originator: John Preisler >Organization: VaporNet Inc. >Release: FreeBSD 2.2-STABLE i386 >Environment: freebsd server serving via nfs, samba, and netatalk. No appletalk zones, two other macs on the LAN. >Description: after recompiling latest sources, I noticed the macs could no longer log into the netatalk server. Further investigation shows Oct 6 08:41:02 nitromethane afpd[292]: Can't register nitromethane:AFPServer@* Oct 6 08:41:04 nitromethane papd[294]: can't register nitromethane:LaserWriter@* it cant register itself on the network. I've tried netatalk both from the home site and from the ports collection and neither currently works. I have netatalk in the kernel, and appletalk [ddp] shows up in the routing tables. atalkd still remains up, but afpd and papd die right away once they cant register themselves on the appletalk network. This means that macs can see the server on the network but cant establish a connection to log in. >How-To-Repeat: try and launch the netatalk tools; fails every time. >Fix: unfortuneatly, I have no fix. I will be happy to test whatever whnever however though. >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710061357.IAA00570>