|
There are two potential problems that I can think of: 1. The address you are coming from is probably being filtered by a security program called TCPD. Look in file etc/inetd.conf. There is one line for each service managed by inet. The format of this file is: Service Name Comment ... ... end of the line lists a program to run, what to call the program and any arguments to pass to the program. Find the TCPD program and if it is being used examine two files in etc directory, hosts.allow and hosts.deny. These list all the addresses that are being allowed and denied. 2. The other option is that the address you are coming from has no valid reverse lookup and is thus denied. Check your DNS configuration on the linux box. That could explain wh ythe PC worked and the 400 didn't. Without a valid reverse DNS lookup the linux box will deny the connection for security reasons. Hope this helps. James Turnbull AS/Tech Consulting Matthias Oertli wrote: > I was looking for security problems without any success. I can telnet to the > linux box from any other machine on the same subnet without a problem. > To be sure I brought tcp/ip on the 400 down and assigned it's IP address to a > PC from which I could again successfully telnet to the 400. > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.