Subject: Re: [netatalk-admins] routing problem
From: Jeffrey Thompson (jeffrey@theway.fba.org)
Date: Wed Jul 30 1997 - 10:33:35 EDT
>atalkd listens for other routers on the wire. Normal mac clients
>shouldn't respond, so there won't be a problem. Please let me know if
that's
>wrong.
Mac clients will not respond, however, other appletalk routers will,
such as routers, netware servers routing appletalk (3.1x servers
providing appletalk services), HP directjet cards, will all respond to
the router query for existing network info
on the network. However, if appletalk routing devices agree on the
network number/range, zone names, and default zone for the network then
bringing up a new router should not be a problem.
I thought macs broadcasted their address every so often? It should be
the case that atalkd would listen for mac clients that may want to use
it's services. My problem is, when mac clients are turned on, after
atalkd starts, that the mac clients can't use the atlakd service. But
that's not what happens with our AppleShare server. It simply doesn't matter
if your mac is on or not, the AppleShare server listens for additional
clients coming online. Since I can't rely on an atalkd connection, it makes
atalkd all but unusable in a mac network.
>Also, I don't think you have to have the macs off before booting the
>server/router. You just have to restart them after the router comes up
>before they will do appletalk correctly.
Strange. Why does AppleShare not act this way?
I'm contemplating switching to Columbia Appletalk Server, CAP.
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:25:52 EST