Hi, I sent this message on november 12th 1999, but got no answer. I'm really in deep sh*t with this problem, and I hope someone can help me out here. Okay. Sit back, relax and read this. I need some help. I have this SuSE 6.0 box hooked up, serving a couple of small websites, serving mail, etc. Nothing much. The machine is a P-II 300 with 128MB memory (see table below) and a 4GB IBM FastSCSI-II harddrive, just in case someone asks. It's a fairly fast machine, nicely equipped with fast components, no out of the ordinary stuff. Mem: 127404K av, 124088K used, 3316K free, 24996K shrd, 59924K buff Swap: 130748K av, 20K used, 130728K free 29588K cached This is my main problem: Whenever I try to: telnet, pop3 or any other service that runs through inetd/tcpd, it sits and waits for up to ten seconds before returning a login prompt, gets my mail or whatever. This is an entry in my /etc/inetd.conf for telnet: telnet stream tcp nowait root /usr/sbin/tcpd in.telnetd Seems pretty standard. I've added an entry in /etc/services called telnet24 to be on port 24, and added this entry in my /etc/inetd.conf: telnet24 stream tcp nowait root /usr/sbin/in.telnetd in.telnetd When I telnet to port 24 it *immediately* shows me a logon screen. 'Okay' you may say, 'this is clearly a reverse-DNS-lookup-problem'. I have tried at least a dozen different nameservers, tried pinging other hosts (immediate lookup-results (but his is not reverse)), and all goes well. I've also tried connecting from more than 30 different hosts in the world -from Asia and Europe to Africa and Amerika) but all hosts give the same result: the 10 second wait. What the hell is wrong here?! This really is driving me crazy.. Clearly, tcpd does a hostname verification to see if this is *really* the host connecting before passing the connection through to the appropriate service. If that is the case (and if that's the cause), my question shifts to: 'how can I disable that check?'. I know almost all options in tcpd are made in compiletime. But surely: other hosts do very well and give me my prompt (they are in the same room; same Linux-version). Can I give parameters to tcpd in inetd.conf? And if yes: what's the one for disabling the checks? (man pages doesn't say) I know I can skip the tcpd and go straight to the service like I did with telnet24, but then there's my next of many questions: 'how does that infect my security?' I sincerely hope someone can help me out here, because this problem is keeping me awake. In fact: this specific host is the main server of a small ISP (about 150 users checking mail and so on), so not only I benefit from it. Note that sendmail does the same 10 seconds wait, while it isn't operating via inetd, but Apache runs fine, logging hostnames as it goes! So that's why I'm dubting that this is a reverse-DNS-lookup-failure. I'm looking forward to all your hints and tips, and I *really* hope our bundled knowledge can solve this quite irritating problem! (maybe it's time we upgraded to 6.3?) Greetings, Rogier Maas -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/