Subject: Re: Some macs intermittently can't see server/printers
From: Martin Espinoza (mespinoz@onlinepartners.com)
Date: Wed Mar 29 2000 - 11:36:09 EST
This seems to have been the info that saved me. I thought I'd reshare
it.
Incidentally, only the Printer (thank god, since I have no idea how to
change its appletalk address) actually got a new Appletalk address which
is in my desired range automatically. I actually had to go to each of the
macs and set their address MANUALLY in the appletalk control panel. I
hate macs more every day :)
> > My atalkd.conf has mutated to the following (Which still doesn't generate
> > a zone that anything can see. One mac saw it for one bootup and then never
> > saw it again.)
> >
> > eth0 -router -phase 2 -net 0-65534 -addr 71.93 -zone "Internal"
...
> > 3> Why are some people, mostly running the latest and greatest MacOS,
> > sometimes unable to see my fileserver and the printers on it, whilst
> > other people (some on MacOS9, some on MacOS8.6) can see them all fine?
>
> My guess is that atalkd is trying to seed the network with your netrange,
> but there are machines on the network with numbers like 65280 and 41201
> which are conflicting. Also, I wouldn't try to seed the network with such
> a large netrange. Really, how many macs do you plan to put in this
> network? I would recommend turning off all the other Appletalk devices on
> the network or finding a time when they are all off. If there are no
> other Appletalk devices on the network, then atalkd should have no reason
> to use something other than your settings. Then kill atalkd and
> create the following atalkd.conf:
>
> eth0 -router -phase 2 -net 1-10 -addr 1.1 -zone "Internal"
>
> Start atalkd and see what ifconfig, getzones, and nbplkup show. If that
> looks okay and your atalkd.conf hasn't been overwritten, then bring up a
> single mac client and see what net/addr it gets.
>
> It is interesting that some devices are on net 71 and 56, which usually
> implies an Appletalk router is seeding the network with a network range,
> while other devices are using 65280, which is usually the network a mac
> uses when there is no Appletalk router. Maybe this is confusing the macs
> so that they won't see the server?
Not only that, but some of them were on equally oddball numbers which were
NOT 65280 (which makes them MORE oddball, I guess.)
Incidentally, is this intended to be the same as the behavior of DHCP
which gives you a link-local address when it can't find a server? That's
certainly what it looks like. Pity some of the macs did it, and some didn't,
and netatalk never did.
---------------------------------------------------------------------------
mespinoza@onlinepartners.com -- LAN/MIS Administrator
"You are what you do when it counts." -- John Steakley, Armor
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:30:21 EST