Re: [Netatalk-devel] How to setup atalkd.conf and afpd.conf on a mult ihomed host?

[Thomas K. <Tho...@ph...>]

On Mon, 29 Apr 2002 04:44:54 -0700, Ngo, Hoc wrote:

> b) if Mac client is on the second network
> The hostname "star" appears in the chooser.

This is part of AppleTalk communications.

> But when I click to connect over tcp/ip, it times out
> and then falls back to AppleTalk (OS 9).

The mac tries to connect to an ip address advertised by the server. Use
ServerInfo (<http://www.macula.se/serverinfo/>) to check which address(es)
will be pulished.

> What should I specify in atalkd.conf and/or afpd.conf so that,
> regardless of whether the Mac client is on the first or second network:
> 1) the server name appears in the chooser (OS 9)

This is set up properly on your system

> or network browser (OS X)?

OS X can resolve an afp server with AppleTalk, too. If you need support for
slp, then you can use either static registrations or compile netatalk to
publish itself dynamically via OpenSLP (search the archives of the
*netatalk-admins* list for support questions)

> 2) clicking to connect over tcp/ip will not time out.

If the IP address, your netatalk server advertises, is in the network range
of the first net, then you should check whether you can ping this address
from the other network. If this isn't working, you can't do that much inside
netatalk configuration files...

> Do I have to specify two servers in afpd.conf?
> "star:AFPServer@Zone One" -tcp -ddp -ipaddr 10.33.1.10 -port 548
> -ddpaddr 201.15
> "star:AFPServer2@Zone One" -tcp -ddp -ipaddr 192.168.1.10 -port
> 12000 -ddpaddr 204.15

No. Registering two AppleTalk entities in the same zone with the same name,
isn't that smart as the 'name to AppleTalk address' resolution won't work
properly. I believe, netatalk won't publish NBP entries, that are already in
use. 

If you publish the second server on "Zone two" this could work, though.

> I have tried several combinations but none of them worked.

I would suggest, trying to check whether you can ping 10.33.1.10 from inside
the 192.168.1.x subnet.

> The only time I get good tcp/ip connection is when the Mac client
> is on the same network as the first network interface card.

And that's the point ;-)

> Is it because the first IP address is associated with hostname and
> the second isn't?

IMO not. It's because, the address, the server sends out as an answer to a
client's FPGetSrvrInfo request, cannot be reached from inside the other
subnet.

Regards,

Thomas