Subject: Re: Some macs intermittently can't see server/printers
From: andrew morgan (morgan@orst.edu)
Date: Tue Mar 28 2000 - 19:38:18 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.
>
> A "nbplkup =" shows the following:
>
> HP Laserjet 4050 TN:LaserWriter 71.93:129
> hal:AFPServer 71.93:130
> Tektronix Phaser 740:LaserWriter 71.93:128
> hal:netatalk 71.93:4
> hal:Workstation 71.93:4
> xxxx xxxxxxxxx Computer: Power Macintosh 56.104:252
> xxxx xxxxxxxxx Computer:Workstation 56.104:4
> macbeth:AFPServer 65280.59:128
> macbeth:netatalk 65280.59:4
> macbeth:Workstation 65280.59:4
> 8BIM_001_169827_PSW550R7?:An unknown user 65403.175:250
> 8BIM_001_169827_PSW550R7:8BIM_001_169827_PSW550R7 65403.175:250
> :ARA - Personal Server 65403.175:2
> <Unnamed>: Power Macintosh 65403.175:252
> MAC: Power Macintosh 41201.173:252
> MAC:Workstation 41201.173:4
> :ARA - Client-Only 65280.149:2
> <Unnamed>: Macintosh PowerBook 65280.149:252
> Phaser 740:LaserWriter 65379.99:128
>
> 1> How do I create a zone, and have it show up?
Only a machine seeding the network can create a zone. Also, all Appletalk
routers must agree on the net range and zone names.
> 2> How do I properly seed a network at the same time? Neither -router, -seed,
> nor both will apparently do this here.
You must use the -router option to seed the network on a single interface.
> 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?
Andy
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:30:20 EST