Re: My funny ftp...

[Barrie Bremner <nospam [at] ecosse.net>]

Right then...

> The reason FTP is different is that FTP uses two connections, one
> client -> server and the other server -> client under normal setups.
> What often happens in home nets is that for some reason the server
> can't figure out where the client is for the second connection. It's
> a routing table problem.

Routing table? There's a new one on me. I've config`d /etc/resolv.conf,
/etc/hosts, and that`s about it..

>
> I forget what the solution was when this happened to me, but the
> workaround was something like telnet from the machine whose FTP client
> hangs to the server before starting FTP (or was it the other way
> around?) which updated the internal routing tables of the kernel. The
> permanent solution was to make sure that the routing tables for the
> LAN were correct. In particular, I seem to recall that my ppp-server
> had to have two names in /etc/hosts, one for the ppp-connection ppp0
> and the other for the local intranet on eth0. FTP seems to be very
> tricky for setting up multi-homed (ie, multi-network-interface) hosts.

Well, dunno if this is gonna help or not, but arrakis (my machine)
provides a ppp connection for both machines - one thro IP masq, and also
NFS. Telnet and ftp from marlboro (flatmates machine...the one that
doesn`t like me) all work fine.

It is marlboro (192.168.0.2), which as far as it is concerned has only
eth0 as an interface, that has all the problems.

So, what should I do?

Baz.

----------
Barrie J. Bremner

Email: TheEnglishman [at] ecosse.net

Webpage: http://www.geocities.com/thefatenglishman

Telephone: UK 0131 313 3266

Fashion is a form of ugliness so intolerable that we have to alter it
every six months.

- Oscar Wilde

Start your own FREE mailing list at

© 2000 Microsoft Corporation. All Rights Reserved