Just to verify - your xinetd is listening on ports 21 and 23? If it is not listening on these ports, it has no way of knowing that it should fork telnetd or wu-ftpd. I am not real familiar with xinetd (I run Debian, using inetd), but it sounds like it may not be listening on the proper ports, or the configuration files for wu-ftpd and telnetd may not be set up to allow access. Are there ftpusers, hosts.allow, hosts.deny files that need to be configured? Darrell On Thu, Dec 06, 2001 at 06:56:13PM -0700, MEHTA,HIREN (A-SanJose,ex1) wrote: > I did ran strace on my xinetd process which was listening on the ports. > My understanding is that when somebody connects using ftp, xinetd will > do some more stuff and again start listening on the ports. But in my case, > when I started ftp/telnet from windows client to the linux machine, the > xinetd > was still sitting on listening on the ports. So I guess, it is not even > forking > the in.wuftpd/telnetd processes. The configuration files for wuftpd will be > read by wuftpd when it is started. But in my case, wuftpd itself does not > seem be starting. > > When I did ftp from the same machine, it worked fine without any problem > and I could see xinetd getting out of listening and finally forking > in.wuftpd. > > This is my local net. How do I verify whether there is any firewall or not ? > > Somehow it looks like xinetd does not come to know that some client is > trying > to start a session. Any explainations ? > > Hiren Mehta > Software Design Engineer > Agilent Technologies > >> From: Darrell A Escola [mailto:darrell@descola.net] >> Sent: Thursday, December 06, 2001 5:41 PM >> >> The standard port for telnet is 23, for ftp is 21 - your windows clients are >> most likely talking to these ports. > - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
