OK, let me explain. I've been sick for a week and came out to the office tonight to see how things are going. Everythinged fine, and I needed to update a static html page on our secondary server. I opened CuteFTP on my Win2k workstation and the first thing I noticed...is that it loged in way to fast. Funny, you say. Well, not funny. We're running ProFTPd on both our RedHat servers, mostly because wuftpd gives me nightmares, being hard to configure and having lots of security holes. I should point out that we've been using ProFTPd for several months, long before the Ramen stuff started. I use postfix in place of sendmail on our main server for similar reasons, unfortunately, we're running sendmail still on the second server (the one I'm having trouble with) cause we were having some trouble with bulk mailing on postifx, and we had to get the job done. We're not running any RPC or NFS stuff, nor any printing services (no LPD, no CUPS, no LPRng) Anyway, on both our servers ProFTPd has always taken a really long time to authenticate. I don't know why, I've turned off reverse hostname lookups, but it always takes about 9 seconds between "socket connected" and actually loging in. Our working server still takes about nine seconds. In the past I've done all kinds of things to shorten the login time but nothing seems to help. So anyway, to, I go to log onto the second server and it authenticates like greased lightning, faster then wuftpd, faster then our NT servers, faster then anything I've ever logged onto. And no one admins these boxes besides me, in fact the box in question hardly even has any users. So then next thing I found is that none of the Virtual users can log in any more, though all of the shell users (users authenticated with PAM) still can - like greased lightning. I get error 503, login not correct. I tried every single virtual user - 12 or so - and none of them work. I am very, very sure I am using the ri! ght passwords. (for those of you who don't know, proftpd lets you set up a virtual user file with username/password combos so that you can use authentication and jailing for users who don't actually exist as far as the main system is concerned - it's an entirely self-contained thing. Anyway, I cannot think of a single thing short of a trojan that would prevent the virtual users from working all the sudden. But I ran an md5sum on the binarie and it's exactly the same size as the one on our working server. And I can't find a single thing wrong with the system! There is one other thing: I can't get to any of the user's home html directories anymore, even though again, no one's touched apache. you know what I mean, where you put in www.your_server.com/~some_local_username/. ~jw has always worked but not anymore. I checked the httpd.conf and UserDir is still set to public_html and is not commented out. Log files look fine, I did a port scan and no unusual ports are open, everything seems very normal except the virtual FTP users and Apache home directories. Does anyone have any ideas what might be going on here? I can't think of anything to check. Help would be greatly appreciated. ---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com Central Texas IT http://www.centraltexasit.com _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
