Subject: Re: Working over TCP
From: Duncan Sinclair (sinclair@dis.strath.ac.uk)
Date: Fri Jan 05 2001 - 10:18:43 EST
Peter Gutowski writes:
>On Tuesday, January 2, 2001, Miguel Beccari <miguel.beccari@clikka.com> wrote:
>>netatalk is working fine......
>>
>>but not over tcp!
>The problem is probably not afpd but rather, your nameserver. The name
>as it appears in the chooser must resolve to an IP address on the local
>network. But it's still a bit more complicated than that, and I believe
>that the hostname or domain name of the linux box has some influence
>here. (You can also use the "Server IP address..." button to enter
>either the hostname or I23.456.789.012)
This seems to be a new urban myth. My Sun appears as "Department Server"
in my Chooser. I don't even think it would be possible to put this name
in the DNS. But TCP connections work OK for me.
I believe the Mac gets the IP number from the server either in the original
NBP (Chooser) information, or through an initial appletalk-based meeting of
minds. I think it's the second one...
There may well be factors concerning what IP number your server thinks
it has, compared with what the client thinks it is. For example, if
you have more than one IP number, perhaps if the server uses the wrong
one, the client will not be able to initialise a TCP connection and
fall back to AppleTalk. (As afp over tcp always worked for me, I not
an expert on the possible ways it can fail.)
Cheers,
Duncan Sinclair.
PS> Anyone know how the latest netatalk-1.5 pre-release is on Solaris?
Does it compile yet?
This archive was generated by hypermail 2b28 : Sun Oct 14 2001 - 03:04:30 EDT