This is baffling. I have a OS X 10.2.3 machine that can connect just
fine (as do you). The sniffer traces are more or less identical. Since
it looks like the OS X client is initiating the disconnect, can you
bring up the OS X console under Applications-Utilities-Console, and
see if any
On Sat, 2003-01-11 at 18:00, Jim Arnold wrote:
I am running netatalk-1.6.0_1,1 from the FreeBSD ports systems on two
boxes and connecting from Mac OS X 10.2.3.
Now when I connect from one box I get the following error on the mac:
Connection failed
An AppleShare system error occurred.
On Sat, 2003-01-11 at 19:12, Jim Arnold wrote:
The log isn't too helpful, but a sniffer trace might be. Can you
capture the client connection to the bad server with tcpdump, and send
me the raw capture file. I recommend the following command line:
tcpdump -s 1518 -w /tmp/outfile host
Do you have a custom volume icon on this server? If so, try deleting
it, then reconnection.
Nope. Nothing fancy. Just a straight install of Netatalk and I didn't
change any of the icons.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the
On Sat, 2003-01-11 at 20:40, Jim Arnold wrote:
Do you have a custom volume icon on this server? If so, try deleting
it, then reconnection.
Nope. Nothing fancy. Just a straight install of Netatalk and I didn't
change any of the icons.
When exactly do you see the message? Right after
When exactly do you see the message? Right after you login?
As soon as I hit the connect button after typing in the IP address of
the FreeBSD box or using
the afp address.
Can you
send your AppleVolumes.default
This just has the ~ (tilde) at the end so the home directory will get mounted
On Sat, 2003-01-11 at 21:56, Jim Arnold wrote:
When exactly do you see the message? Right after you login?
As soon as I hit the connect button after typing in the IP address of
the FreeBSD box or using
the afp address.
Can you
send your AppleVolumes.default
This just has the ~
This is baffling. I have a OS X 10.2.3 machine that can connect just
fine (as do you). The sniffer traces are more or less identical. Since
it looks like the OS X client is initiating the disconnect, can you
bring up the OS X console under Applications-Utilities-Console, and
see if any
