Subject: Re: [netatalk-admins] netatalk-1.4b2+asun2.0a18.2 - IP works, eth ertalk doesn't?
From: Casey Bisson (cbisson@oz.plymouth.edu)
Date: Tue May 26 1998 - 11:33:18 EDT
My first experience with Netatalk was with a Dell 486 and DEC EtherWorks III
ethernet card under FreeBSD. I experienced the same unfathomable problems (can
connect via IP, cannot connect via appletalk), and tried(and failed with) the same
solutions. It was all particularly annoying because MacOS and WinNT machines could
serve AppleShare fine from the same subnet. We read through pages of sniff logs
and forwarded them to our router manufacturer for help, and we couldn't identify
any reasonable cause for the problem.
In the end, I tried a different machine (Dell pnetium 166) a different ethernet
card (3com 10/100) and newer install of FreeBSD (2.2.5.? to 2.2.6.?) and it worked
fine with Netatalk 2.4b3 + asun18 (or 17). Nothing else changed, and it worked.
If you ever do identify why it doesn't work, I'd like to know.
Casey Bisson
Information Technology
Plymouth State College
Sean Page wrote:
> Hi, Andras,
>
> No, there are no other routers, it is a very small test network
> consisting of only the FreeBSD server (sitting between the Appletalk
> network on ethernet and the Internet) and one mac workstation running OS
> 8. Both of them are on the same hub on the inside network. It's very
> strange. Even when I use the -seed option, the Mac can't see the server
> in the chooser.
>
> Tried making the atalkd.conf file read only (great suggestion by the
> way!), but that didn't work either. I also tried manually changing the
> net address on the mac to be the same as the server (different node, of
> course) and that also didn't help. I'm starting to think there is
> something more fundamentally wrong. Any more suggestions?
>
> Sean.
>
> > ----------
> > From: Andras Kadinger
> > Sent: Thursday, May 21, 1998 5:13 PM
> > To: Sean Page
> > Subject: Re: [netatalk-admins] netatalk-1.4b2+asun2.0a18.2 - IP
> > works, ethertalk doesn't?
> >
> > Hello Sean,
> >
> > Sean Page wrote:
> > >
> > > I have installed netatalk-1.4b2+asun2.0a18.2 on FreeBSD 2.2.5 (with
> > > netatalk kernel patches) and I'm at my wits end. I can connect to
> > the
> > > server via IP no problem at all, works great, but can not see it on
> > the
> > > local network via the chooser no matter what I do.
> > >
> > > My atalkd.conf auto configures to:
> > >
> > > ed0 -phase 2 -net 65280-65534 -addr 65280.198
> > > ed1 -phase 2 -net 65280-65534 -addr 0.0
> > > And I tried to reconfigure it to:
> > >
> > > ed0 -phase 2 -net 65280-65534 -addr 65280.198
> > > ed1 -phase 2 -net 100-200 -addr 100.1
> > > to no avail. ed0 is the interface to the outside world, ed1 is the
> > > internal network. I am also running NAT, if that makes a
> > difference...
> > >
> > > Any advise on what I can try would be greatly appreciated!
> >
> > Are there other routers on Your network?
> >
> > Although I am on Linux, I could force atald to use my settings in some
> > cases by making atalkd.conf read-only. Try it, it might help.
> >
> > What do Macs show in their AppleTalk control panel in Administrator
> > mode?
> >
> > Sincerely,
> > Andras Kadinger
> > bandit@freeside.elte.hu
> >
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:32:45 EST