Telnet localhost funktioniert nicht
Hallo zusammen, habe mir telnetd installiert und hatte erwartet das ich jetzt auch ein Telnet auf localhost machen kann. Aber auf Port 23 lauscht keiner. An welcher Schraube muß ich denn noch drehen? In der inetd.conf ist er sauber eingetragen Gruß Gregor --- Unser Firmenname hat sich geaendert! Hays Logistics GmbH ist nun K + P Logistik GmbH. Bitte aendern sie ihre E-Mail Kontakte auf die neuen E-Mail Adressen! Our company name has changed! Hays Logistics GmbH is now K + P Logistik GmbH. Please change your e-mail contacts to the new e-mail-addresses!
Re: Telnet localhost funktioniert nicht
Hallo Gregor, telnetd trägt sich in die /etc/inetd.conf ein. Benutzt du den inetd oder den xinetd? Solltest du letzteren benutzen mußt du entweder den Dienst manuell für xinetd eintragen, oder du trägst in die /etc/default/xinetd folgendes ein: XINETD_OPTS=-inetd_compat Dann arbeitet xinetd im Compatibilitäts Modus. Zum Konvertieren von inetd-Einträgen gab es mal ein Skript aber ich hab leider vergessen wie das heißt und wie es funktioniert. Das alles kann man auch nachlesen unter: /usr/share/doc/xinetd/README.Debian Gruß Stefan Am Donnerstag, 10. Juni 2004 19:52 schrieb Schumacher, Gregor: Hallo zusammen, habe mir telnetd installiert und hatte erwartet das ich jetzt auch ein Telnet auf localhost machen kann. Aber auf Port 23 lauscht keiner. An welcher Schraube muß ich denn noch drehen? In der inetd.conf ist er sauber eingetragen Gruß Gregor --- Unser Firmenname hat sich geaendert! Hays Logistics GmbH ist nun K + P Logistik GmbH. Bitte aendern sie ihre E-Mail Kontakte auf die neuen E-Mail Adressen! Our company name has changed! Hays Logistics GmbH is now K + P Logistik GmbH. Please change your e-mail contacts to the new e-mail-addresses! -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Telnet localhost funktioniert nicht
Moin, On Thu, Jun 10, 2004 at 07:52:13PM +0200, Schumacher, Gregor wrote: [...] welcher Schraube muß ich denn noch drehen? In der inetd.conf ist er sauber eingetragen und inetd hat auch die Konfiguration neu gelesen? Lass doch mal /etc/init.d/inetd reload laufen ... Gruss -- hgb -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: telnet localhost slow, telnet 127.0.0.1 ok
[EMAIL PROTECTED] writes: If I run telnet localhost 22 then I have to wait 15-30 seconds before it connects; with telnet 127.0.0.1 22 it connects at once. I have the same results using other open ports. Does telnet -4 localhost give the same delay? If not, then the problem is IPv6 support. Even though all your resolution configuration files are set up correctly, telnet is using getaddrinfo() to grab *both* IPv4 and IPv6 addresses for localhost. The former gets looked up in the hosts file, but the latter goes out to your nameserver. If you want, you can add localhost to the ::1 line in /etc/hosts like so: ::1 ip6-localhost ip6-loopback localhost and that'll allow you to do telnet localhost without delay. That may cause problems with other programs, though, which might try to use IPv6 addresses in preference to IPv4 addresses without falling back if they can't connect to the IPv6 address. And, if the nameserver you're using always chokes on IPv6 queries (not just for localhost), then telnet anyhostname will always give the same delay, and you're better off aliasing telnet to telnet -4. -- Kevin [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: telnet localhost slow, telnet 127.0.0.1 ok
* Shyamal Prasad ([EMAIL PROTECTED]) [030816 13:59]: Rupert == RUPERT LEVENE [EMAIL PROTECTED] writes: Rupert Shyamal Prasad [EMAIL PROTECTED] wrote: Rupert == RUPERT LEVENE [EMAIL PROTECTED] writes: Rupert Antony Gelberg [EMAIL PROTECTED] wrote: On Sat, Aug 16, 2003 at 12:25:16AM +0100, [EMAIL PROTECTED] wrote: Running strace telnet localhost 22 shows that it's trying to resolve the hostname localhost by querying the nameserver. I thought that shouldn't happen with my setup, though. Does your /etc/host.conf contain order hosts,bind Rupert Yes, it does. I did not see the original post, but the other thing you must have is that /etc/hosts must resolve local host to 127.0.0.1 too Rupert Yes, I have this. Here is another list of things I think Rupert could be relevant. Hi Rupert, The mystery deepens since I looked at your configs and compared with mine, and they are the same. The thing is, uh, when I run strace I see the same thing happen. I can see a query going to my local name server. I bet this has to do with that localhost doesn't have any dots, and ndots defaults to 1. So the first thing it tries to look up is localhost.domain where domain is either the domain or the first item of search in resolv.conf. Can you tell from strace's output if this is correct? try using telnet localhost. or adding something like localhost.localdomain in your /etc/hosts and see if using that name instead avoids the delay. Incidentally, ssh does not do this odd lookup and works exactly how I'd have expected telnet to. That is weird. I haven't looked at the code yet, to compare how each does their resolving. Perhaps ssh is using getaddrinfo and telnet is using gethostbyname, or they're setting different RES options, or something. good times, Vineet -- http://www.doorstop.net/ -- http://www.eff.org/ Defending freedom in the digital world pgp0.pgp Description: PGP signature
Re: telnet localhost slow, telnet 127.0.0.1 ok
RUPERT LEVENE wrote: Indeed. Netcat and galeon appear to do the right thing too, while telnet, lynx and links all suffer from a delay. (I first noticed the problem using lynx). My guess at the moment is that the combination of a slow machine and a slow nameserver is exposing an odd bug in these programs. Although I would be surprised if this were the case since telnet and lynx have such a long pedigree... And you're sure these aren't socks clients? -- Mental ([EMAIL PROTECTED]) The Torah... The Gospels... The Koran... Each claimed as the infallible word of GOD. Misquoted, misinterpreted, misunderstood, and misapplied. Maybe that's why he doesn't do any more interviews. - sinfest.net CARPE NOCTEM, QUAM MINIMUM CREDULA POSTERO. GPG public key: http://www.neverlight.com/pas/Mental.asc pgp0.pgp Description: PGP signature
Re: telnet localhost slow, telnet 127.0.0.1 ok
Mental Patient [EMAIL PROTECTED] wrote: RUPERT LEVENE wrote: Indeed. Netcat and galeon appear to do the right thing too, while telnet, lynx and links all suffer from a delay. (I first noticed the problem using lynx). My guess at the moment is that the combination of a slow machine and a slow nameserver is exposing an odd bug in these programs. Although I would be surprised if this was the case since telnet and lynx have such a long pedigree... And you're sure these aren't socks clients? I'm afraid I don't know anything at all about socks :-). Please could you explain why this may affect the resolution of localhost using a nameserver rather than /etc/hosts, and what may be done to work around it? I'm not running a firewall here, if that's at all relevant -- it's a NAT setup behind an adsl router (which is also acting as a proxy nameserver). Rupert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: telnet localhost slow, telnet 127.0.0.1 ok
Antony Gelberg [EMAIL PROTECTED] wrote: On Sat, Aug 16, 2003 at 12:25:16AM +0100, [EMAIL PROTECTED] wrote: If I run telnet localhost 22 then I have to wait 15-30 seconds before it connects; with telnet 127.0.0.1 22 it connects at once. I have the same results using other open ports. Running strace telnet localhost 22 shows that it's trying to resolve the hostname localhost by querying the nameserver. I thought that shouldn't happen with my setup, though. Does your /etc/host.conf contain order hosts,bind Yes, it does. Sorry I forgot to include that file -- here it is. order hosts,bind multi on Rupert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: telnet localhost slow, telnet 127.0.0.1 ok
Rupert == RUPERT LEVENE [EMAIL PROTECTED] writes: Rupert Antony Gelberg [EMAIL PROTECTED] wrote: On Sat, Aug 16, 2003 at 12:25:16AM +0100, [EMAIL PROTECTED] wrote: Running strace telnet localhost 22 shows that it's trying to resolve the hostname localhost by querying the nameserver. I thought that shouldn't happen with my setup, though. Does your /etc/host.conf contain order hosts,bind Rupert Yes, it does. Sorry I did not see the original post, but the other thing you must have is that /etc/hosts must resolve local host to 127.0.0.1 too, along the lines of 127.0.0.1 localhost Make sure this is the *first line* that resolves localhost. If you've checked /etc/host.conf you've probably done this too, but it never hurts to ask. Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: telnet localhost slow, telnet 127.0.0.1 ok
Shyamal Prasad [EMAIL PROTECTED] wrote: Rupert == RUPERT LEVENE [EMAIL PROTECTED] writes: Rupert Antony Gelberg [EMAIL PROTECTED] wrote: On Sat, Aug 16, 2003 at 12:25:16AM +0100, [EMAIL PROTECTED] wrote: Running strace telnet localhost 22 shows that it's trying to resolve the hostname localhost by querying the nameserver. I thought that shouldn't happen with my setup, though. Does your /etc/host.conf contain order hosts,bind Rupert Yes, it does. I did not see the original post, but the other thing you must have is that /etc/hosts must resolve local host to 127.0.0.1 too Yes, I have this. Here is another list of things I think could be relevant. Rupert /etc/hosts 127.0.0.1 localhost 192.168.0.205 deb150desktop /etc/resolv.conf nameserver 192.168.0.1 /etc/hostname deb150desktop /etc/nsswitch.conf # /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # If you have the `glibc-doc' and `info' packages installed, try: # `info libc Name Service Switch' for information about this file. passwd: compat group: compat shadow: compat hosts: files dns networks: files protocols: db files services: db files ethers: db files rpc:db files netgroup: nis /etc/hosts.conf order hosts,bind multi on deb150desktop:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:4F:4C:03:38:75 inet addr:192.168.0.205 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:29528 errors:0 dropped:0 overruns:0 frame:0 TX packets:26981 errors:0 dropped:0 overruns:0 carrier:0 collisions:13 txqueuelen:100 RX bytes:3027177 (2.8 MiB) TX bytes:8676934 (8.2 MiB) Interrupt:11 Base address:0x300 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:634 errors:0 dropped:0 overruns:0 frame:0 TX packets:634 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:224937 (219.6 KiB) TX bytes:224937 (219.6 KiB) deb150desktop:~# host localhost localhost has address 127.0.0.1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: telnet localhost slow, telnet 127.0.0.1 ok
Rupert == RUPERT LEVENE [EMAIL PROTECTED] writes: Rupert Shyamal Prasad [EMAIL PROTECTED] wrote: Rupert == RUPERT LEVENE [EMAIL PROTECTED] writes: Rupert Antony Gelberg [EMAIL PROTECTED] wrote: On Sat, Aug 16, 2003 at 12:25:16AM +0100, [EMAIL PROTECTED] wrote: Running strace telnet localhost 22 shows that it's trying to resolve the hostname localhost by querying the nameserver. I thought that shouldn't happen with my setup, though. Does your /etc/host.conf contain order hosts,bind Rupert Yes, it does. I did not see the original post, but the other thing you must have is that /etc/hosts must resolve local host to 127.0.0.1 too Rupert Yes, I have this. Here is another list of things I think Rupert could be relevant. Hi Rupert, The mystery deepens since I looked at your configs and compared with mine, and they are the same. The thing is, uh, when I run strace I see the same thing happen. I can see a query going to my local name server. I've never noticed this because (a) I don't use telnet and (b) my nameserver responds quickly enough that I don't notice any wierd delay. Now I'm really interested in the solution for your problem. Sorry I can't give you a solution ;-) Incidentally, ssh does not do this odd lookup and works exactly how I'd have expected telnet to. Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: telnet localhost slow, telnet 127.0.0.1 ok
Shyamal Prasad [EMAIL PROTECTED] wrote: Rupert == RUPERT LEVENE [EMAIL PROTECTED] writes: Rupert Shyamal Prasad [EMAIL PROTECTED] wrote: Rupert == RUPERT LEVENE [EMAIL PROTECTED] writes: Rupert Antony Gelberg [EMAIL PROTECTED] wrote: On Sat, Aug 16, 2003 at 12:25:16AM +0100, [EMAIL PROTECTED] wrote: Running strace telnet localhost 22 shows that it's trying to resolve the hostname localhost by querying the nameserver. I thought that shouldn't happen with my setup, though. The mystery deepens since I looked at your configs and compared with mine, and they are the same. The thing is, uh, when I run strace I see the same thing happen. I can see a query going to my local name server. I've never noticed this because (a) I don't use telnet and (b) my nameserver responds quickly enough that I don't notice any wierd delay. Now I'm really interested in the solution for your problem. Sorry I can't give you a solution ;-) Incidentally, ssh does not do this odd lookup and works exactly how I'd have expected telnet to. Indeed. Netcat and galeon appear to do the right thing too, while telnet, lynx and links all suffer from a delay. (I first noticed the problem using lynx). My guess at the moment is that the combination of a slow machine and a slow nameserver is exposing an odd bug in these programs. Although I would be surprised if this were the case since telnet and lynx have such a long pedigree... Rupert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
telnet localhost slow, telnet 127.0.0.1 ok
If I run telnet localhost 22 then I have to wait 15-30 seconds before it connects; with telnet 127.0.0.1 22 it connects at once. I have the same results using other open ports. Running strace telnet localhost 22 shows that it's trying to resolve the hostname localhost by querying the nameserver. I thought that shouldn't happen with my setup, though. I'm running debian woody... any ideas why this might be happening and how to solve it? Rupert /etc/hosts 127.0.0.1 localhost 192.168.0.205 deb150desktop /etc/resolv.conf nameserver 192.168.0.1 /etc/hostname deb150desktop /etc/nsswitch.conf # /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # If you have the `glibc-doc' and `info' packages installed, try: # `info libc Name Service Switch' for information about this file. passwd: compat group: compat shadow: compat hosts: files dns networks: files protocols: db files services: db files ethers: db files rpc:db files netgroup: nis deb150desktop:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:4F:4C:03:38:75 inet addr:192.168.0.205 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:29528 errors:0 dropped:0 overruns:0 frame:0 TX packets:26981 errors:0 dropped:0 overruns:0 carrier:0 collisions:13 txqueuelen:100 RX bytes:3027177 (2.8 MiB) TX bytes:8676934 (8.2 MiB) Interrupt:11 Base address:0x300 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:634 errors:0 dropped:0 overruns:0 frame:0 TX packets:634 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:224937 (219.6 KiB) TX bytes:224937 (219.6 KiB) deb150desktop:~# host localhost localhost has address 127.0.0.1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: telnet localhost slow, telnet 127.0.0.1 ok
On Sat, Aug 16, 2003 at 12:25:16AM +0100, [EMAIL PROTECTED] wrote: If I run telnet localhost 22 then I have to wait 15-30 seconds before it connects; with telnet 127.0.0.1 22 it connects at once. I have the same results using other open ports. Running strace telnet localhost 22 shows that it's trying to resolve the hostname localhost by querying the nameserver. I thought that shouldn't happen with my setup, though. I'm running debian woody... any ideas why this might be happening and how to solve it? Rupert Does your /etc/host.conf contain order hosts,bind ? A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
telnet localhost
Hi, After uprgating to hamm it is immposiible to telnet,talk to local host. All services are allowed via hosts.allow/hosts.deny but nevetheless I am getting: Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused What is wrong? As I remeber it was ok on bo :( TIA, Eugene Sevinian CRD, YerPhI, 375036, Armenia URL: http://crdlx5.yerphi.am/ Phone: 374-2-344873
Re: telnet localhost
Have you tried to telnet to your machine from a remote machine? If not check inetd.conf and make sure telnetd is running there. If it isn't put it in and then kill -HUP inetd's pid. If you have a default host.allow it should allow anyone so that is the problem and default hosts.deny is no problem either. On Fri, 9 Oct 1998, Eugene Sevinian wrote: Hi, After uprgating to hamm it is immposiible to telnet,talk to local host. All services are allowed via hosts.allow/hosts.deny but nevetheless I am getting: Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused What is wrong? As I remeber it was ok on bo :( TIA, Eugene Sevinian CRD, YerPhI, 375036, Armenia URL: http://crdlx5.yerphi.am/ Phone: 374-2-344873 -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: telnet localhost (still isn't working)
Hi again, I was advised to check inet.conf but it seems that everything is ok with telnet entry in that file. Here it is: telnet stream tcp nowait root /usr/sbin/tcpd /usr/sbin/in.telnetd Also there is a string 127.0.0.1 localhost in /etc/hosts and ALL: ALL in hosts.allow. ping to localhost is working, but telnet,ftp,talk aren't. Is there any idea? Thanks, Eugene. Hi, After uprgating to hamm it is immposiible to telnet,talk to local host. All services are allowed via hosts.allow/hosts.deny but nevetheless I am getting: Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused What is wrong? As I remeber it was ok on bo :( TIA, Eugene Sevinian CRD, YerPhI, 375036, Armenia URL: http://crdlx5.yerphi.am/ Phone: 374-2-344873 -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null Eugene Sevinian CRD, YerPhI, 375036, Armenia URL: http://crdlx5.yerphi.am/ Phone: 374-2-344873
