Jan Willem Stumpel said: > This is a follow-up to the thread "Local Net - delays in telnet > login" of last month. > > So it seems the identification "saturn --> 192.168.2.2" cannot be made > locally (i.e. on jupiter) although the identification > "192.168.2.2 --> saturn" can. What is wrong with my "address > lookup set-up"?
this is usually caused by tcp wrappers(most often controlled from /etc/hosts.deny and /etc/hosts.allow). the best solution I think is to run a local nameserver and provide forward and reverse resolution for your local network. A workaround may be to do something such as: ALL: 192.168.2. in your /etc/hosts.allow and/or remove ALL: PARANOID from /etc/hosts.deny. that format above may not be exactly right its been years since I've seriously played with tcp wrappers. but I still reccomend setting up a DNS .. another workaround at least for telnet may be to just not use tcp_wrappers(which is fine as long as your firewalled), edit /etc/inetd.conf and remove the reference to tcpd, and restart it, that may work too(haven't tried it, and I've been using xinetd for a while which has it's own tcp wrappers support..) nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
