Subject: Re: Some macs intermittently can't see server/printers
From: Patrik Schindler (poc@pocnet.net)
Date: Tue Mar 28 2000 - 20:11:56 EST
On Tue, 28 Mar 2000, Martin Espinoza wrote:
> 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"
>
> Mind you, I put "-net 0-128" in the file, and it decided it should have
> bigger values and overwrote it, which seems to me to be Very Bad Behavior.
> If netatalk was my child, I'd send it to the corner for time out.
If you read in syslog, you'll find more information when netatalk starts
why it has chosen such a netrange.
I do now know the -router parameter yet but of you want a defined zone,
you'll have to use seeding. Seeding was known to be a not-work (for
logical reasons) in early versions of netatalk.
You can use an entry for a dummy device (dummy.o) to force seeding (like
I did). These days I utilize two NICs, so I don't use that anymore.
> Which is the zone I've been trying to create. Of course, my atalkd.conf
> no longer seems like it should be generating it, but there it is.
>
> Just for laughs, here's an ifconfig -a.
The Kernel drops AppleTalk adresses only if you unload appletalk.o (DDP
Support) or if you configure your NIC down and all over up again.
> 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?
Are you sure that these Macs AppleTalk Stack agreed with your net range
you defined?
Sometimes shutting AppleTalk down firing up again helps on such machines.
Sometimes they'll need a restart.
Sometimes you'll even have to delete the AppleTalk Prefs, restart and set
up the AppleTalk connection anew.
:wq! PoC
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:30:20 EST