[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 12/06/07, Simon Waters <simon@xxxxxxxxxxxxxx> wrote: > Aaron Trevena wrote: > > > > I get 'no route to host' after logging in just fine - and also some > > errors about reverse dns failures. > > One of the FTP servers on Redhat use to default to requiring that > clients have a reverse DNS entry. It was a simple edit of the config > file to disable that requirement. I've no idea why it was left as a default. I've been trying to find it and unset it, but no joy - I'm not onsite at the client for a while now so I can't look at the files. > As for no route to host -- no idea. Maybe a firewall in the way? Sounds > like two different problems -- sort the reverse DNS first. Could be two problems - sometimes ftpd leaves an error about reverse dns not matching and sometimes it doesn't - very annoying. > Also is the no route error occurring when the data channel would be > opened? i.e. On a fetch or "dir" command. If so try passive mode FTP. Yup, but passive mode is the default of the clients I used - when I switched from passive to active it just hung. I also opened the ftp data channel to no avail. > I think usually an entry in /etc/hosts for the clients IP address will > deal with the lack of reverse DNS. It should be logging all this nicely > in /var/log, so you should see what IP address it saw, and other such > complaints. You'd think so :( In the end I said to use scp or sftp instead, particularly with keys set up as it's for an automated job. A. -- http://www.aarontrevena.co.uk LAMP System Integration, Development and Hosting -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html