Once again the list is brilliant when I am dull... DNS looks like it was indeed the culprit. I didn't seem to have this problem with my OpenBSD 3.6 ftp server. Does anyone know off the top of their head if there has been a change? I'll have to find out if I set up the origonal server to be able to do reverse lookups and just don't remember now.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > stuartv > Sent: Tuesday, March 13, 2007 8:31 AM > To: [EMAIL PROTECTED] Org (E-mail) > Subject: ftpd problems > > > I am getting ready to replace an aging FTP server with an OpenBSD 4.0 > server. The old server runs OpenBSD 3.6 and has always > worked beautifully. > Now, while setting up and testing the new OpenBSD 4.0 server > I am having > some issues. I am using the exact same setup as I did on the > 3.6 server. > > Here is my line in inetd.conf: > > ftp stream tcp nowait root /usr/libexec/ftpd > ftpd -Unll -u 006 > > At first, I was able to login quickly and easily. Then, a couple days > later, I am unable to login at all using the windows command line ftp > command. I get "Connected to <ip address>" and after a few minutes > "Connection closed by remote host". When I try from one of > my OBSD test > boxes I get the same "Connected to <ip address>" and have to > wait a few > minutes for it to finally get a login screen. And I mean > literally at least > 2 minutes. At first I didn't know it would even finally come > up with a > login because I gave up long before 2 minutes were up. I > suspect that the > difference between the windows client and the OBSD client is > their timeout > value. > > Does anyone know why it would be taking so long to get a > login (and how to > fix it)? This server will be used by our customers and > they won't be > happy with that kind of performance. > > Stuart van Zee > [EMAIL PROTECTED]
