(Illustration by Gaich Muramatsu)
Hi again, after updating to Coda 6.0.4 (Debian), my setup stopped working completely, and I saw lots of messages like 19:48:08 Callback message to 192.168.1.2 port 32983 failed RPC2_NOTCLIENT (F) on my server log. Some older articles on the mailing list hinted that these errors might be due to firewall conflicts. It turns out that I was accessing the server on its external IP even though my client was on the internal network. Coda 6.0.3 did not seem to care about this - at least for read access. With Coda 6.0.4, I have the following scenario (client on internal net) /coda/internal-ip - does not work /coda/external-ip - does not work /coda/name-of-internal-ip - works fine (even write access) /coda/name-of-external-ip - works partly, after /coda/name-of-internal-ip is connected (can list directory, other things don't work, maybe depends on what is cached) So it looks like I'm all set to start for real now... JohannesReceived on 2004-03-18 14:37:10