Subject: Re: [netatalk-admins] netatalk-1.4b2+asun2.1.0 afpd name registering problems
From: Bill Studenmund (skippy@macro.stanford.edu)
Date: Tue Sep 01 1998 - 16:38:51 EDT
On Sat, 22 Aug 1998, Neil McAllister wrote:
> To simplify, let's say I have a network with two zones, "Zone 1" and
> "Zone 2". I want to start up two separate servers (using afpd.conf),
> and I'd like one to appear in Zone 1, and the other to appear in Zone
> 2. Both Zones are available on the same network segment, via a
> standalone Appletalk router. Zone 1 is the default zone the netatalk
> server finds itself in, so for the first afp server all I need to do is
> have a line in afpd.conf like:
>
> "First Server" -notcp -guest [... etc.]
>
> The second server needs to be "forced" to go into the other zone, so I
> do it like this:
>
> "Second Server:AFPServer@Zone 2" -notcp -guest [... etc.]
[snip]
> OK, this problem is largely cosmetic. (Though, being a Mac user, I'd
> like it patched up for that reason alone. ;-) But I have noticed
> another thing that seems sort of strange, and I have a weird hunch it's
> related.
>
> When I tried to connect to Second Server from a Mac client in Zone 2 via
>
> Appleshare/IP, and log in using a correct username and password,
> netatalk authenticates me properly. But as soon as I select a volume on
>
> Second Server and hit OK, it reports a strange error about the
> connection being refused, that I should contact my administrator, and in
> parenthesis something about Appleshare software not being installed.
> It's damn odd! And somehow, I have a suspicion it can be traced back to
> netatalk returning an incorrect server name to the Chooser (including
> the full Zone address info in the server nbp name, when it shouldn't).
Perhaps I'm way off, but doesn't the -notcp option preclude IP support?
Also, I know that if you are trying to run two afpd daemons both w/ IP
support, you have to tell one of them to use a non-standard IP port. If
I'm wrong about -notcp, then maybe the standard port is getting asigned to
the first server, but the second server still thinks it's got the standard
port. Thus when you come in using AppleTalk for the login, when it tries
to roll you over to the IP port, it gets the #1 server, which has never
heard of you. :-)
Take care,
Bill
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:33:13 EST