After upgrading from 6.3 to 6.4 I can no longer telnet to my server from from my internal network. Firewall is turned off. I'm masquerading on a SDSL link and have no problem with internet access. Any Ideas -- 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/
Can you get at telnet from the outside world? If not... First check to see if telnet is enabled. In /etc/inetd.conf near the top, you'll see a line that looks like telnet stream tcp nowait root /usr/sbin/tcpd in.telnetd Make sure it's uncommented (i.e. it doesn't have a '#' in front of it.) If it was commented and you have to uncomment it, then do rcinetd restart as root to enable it. If that's as it should be, then as root, type the command lsof -i and see if you see a line that looks like inetd 3086 root 6u IPv4 7449 TCP *:telnet (LISTEN) then that means that telnet is running, and something funky is going on, and I'll try to think of more ideas if that's the case. I'll assume you know how good an idea it is to disable telnet connections from the outside world, so I won't go there. :) -tara On Fri, Jun 02, 2000 at 05:00:59PM -0400, Jim Bruer wrote:
After upgrading from 6.3 to 6.4 I can no longer telnet to my server from from my internal network. Firewall is turned off. I'm masquerading on a SDSL link and have no problem with internet access. Any Ideas
-- 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/
-- 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/
/etc/inetd.conf LOOKS OK
If that's as it should be, then as root, type the command lsof -i and see if you see a line that looks like inetd 3086 root 6u IPv4 7449 TCP *:telnet (LISTEN)
This is as close as I get: in.identd 289 root 4u IPv4 240 TCP *:ident (LISTEN) in.identd 291 root 4u IPv4 240 TCP *:ident (LISTEN) in.identd 292 root 4u IPv4 240 TCP *:ident (LISTEN) in.identd 293 root 4u IPv4 240 TCP *:ident (LISTEN) -- 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/
Jim Bruer wrote:
/etc/inetd.conf LOOKS OK
If that's as it should be, then as root, type the command lsof -i and see if you see a line that looks like inetd 3086 root 6u IPv4 7449 TCP *:telnet (LISTEN)
This is as close as I get: in.identd 289 root 4u IPv4 240 TCP *:ident (LISTEN) in.identd 291 root 4u IPv4 240 TCP *:ident (LISTEN) in.identd 292 root 4u IPv4 240 TCP *:ident (LISTEN) in.identd 293 root 4u IPv4 240 TCP *:ident (LISTEN)
did you check what about /etc/hosts.deny /etc/hosts.allow? (see man 5 hosts_access) Juergen -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\ -- 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/
On Sat, 03 Jun 2000, juergen.braukmann@ruhr-west.de wrote:
Jim Bruer wrote:
/etc/inetd.conf LOOKS OK
If that's as it should be, then as root, type the command lsof -i and see if you see a line that looks like inetd 3086 root 6u IPv4 7449 TCP *:telnet (LISTEN)
This is as close as I get: in.identd 289 root 4u IPv4 240 TCP *:ident (LISTEN) in.identd 291 root 4u IPv4 240 TCP *:ident (LISTEN) in.identd 292 root 4u IPv4 240 TCP *:ident (LISTEN) in.identd 293 root 4u IPv4 240 TCP *:ident (LISTEN)
did you check what about /etc/hosts.deny /etc/hosts.allow? (see man 5 hosts_access)
Juergen
/etc/hosts.deny /etc/hosts.allow LOOK OK as well. This is a real puzzler. I can telnet out to the world but not on the internal network. Don't know if this is related but, I can get mail from my Postfix (imap) server using Kmail but not with Netscape messenger. -- 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/
On Fri, Jun 02, 2000 at 11:03:58PM -0400, Jim Bruer wrote:
/etc/inetd.conf LOOKS OK
If that's as it should be, then as root, type the command lsof -i and see if you see a line that looks like inetd 3086 root 6u IPv4 7449 TCP *:telnet (LISTEN)
This is as close as I get: in.identd 289 root 4u IPv4 240 TCP *:ident (LISTEN) in.identd 291 root 4u IPv4 240 TCP *:ident (LISTEN) in.identd 292 root 4u IPv4 240 TCP *:ident (LISTEN) in.identd 293 root 4u IPv4 240 TCP *:ident (LISTEN)
All right, do you have any lines in lsof -i that start with "inetd"? If you don't, check to see if the process is running with "ps ax | grep inetd". -tara -- 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/
On Sat, 03 Jun 2000, you wrote:
On Fri, Jun 02, 2000 at 11:03:58PM -0400, Jim Bruer wrote:
/etc/inetd.conf LOOKS OK
If that's as it should be, then as root, type the command lsof -i and see if you see a line that looks like inetd 3086 root 6u IPv4 7449 TCP *:telnet (LISTEN)
This is as close as I get: in.identd 289 root 4u IPv4 240 TCP *:ident (LISTEN) in.identd 291 root 4u IPv4 240 TCP *:ident (LISTEN) in.identd 292 root 4u IPv4 240 TCP *:ident (LISTEN) in.identd 293 root 4u IPv4 240 TCP *:ident (LISTEN)
All right, do you have any lines in lsof -i that start with "inetd"? If you don't, check to see if the process is running with "ps ax | grep inetd".
-tara inetd is doesn't appear to be working and an attempt to start/restart looks a bit flaky
bash-2.03# rcinetd start Starting INET services (inetd) done bash-2.03# rcinetd start Starting INET services (inetd) failed bash-2.03# rcinetd restart Shutting down INET services (inetd) done Starting INET services (inetd) failed bash-2.03# -- 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/
On Sat, Jun 03, 2000 at 04:05:57PM -0400, Jim Bruer wrote:
On Sat, 03 Jun 2000, you wrote: inetd is doesn't appear to be working and an attempt to start/restart looks a bit flaky
bash-2.03# rcinetd start Starting INET services (inetd) done bash-2.03# rcinetd start Starting INET services (inetd) failed bash-2.03# rcinetd restart Shutting down INET services (inetd) done Starting INET services (inetd) failed bash-2.03#
That is probably your problem then. Is there anything special in /var/log/messages from your attempts to stop/start inetd? If you get inetd to indicate that it has successfully started, do an lsof -i again and see what you get. -tara -- 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/
participants (3)
-
jim＠bruer.org -
juergen.braukmann＠ruhr-west.de -
tla＠akamai.com