Re: [SLUG] Slow initial telnet.
I think you will find that this applies to ftp as well. If you remove resolv.conf and ftp to the ip address lightning quick. Add a DNS server into resolv.conf that doesn't exist telnet, ftp slow as but they eventually connect. Pete -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug
Re: [SLUG] Slow initial telnet.
George Vieira wrote: Hi all, I know this is an oldie question but my initial telnet connections take forever to connect. It connects and then you wait for a minute before getting the logon message. I know the oldie answer was to remove `named` as the server was trying to resolve the IP address but named isn't running on this system. Also adding the names to the host file works but isn't the answer for me as this server is going to a site which will have remote WAN connections. When you say adding the names to the host file do you mean just /etc/host or the whole set including hosts.allow and hosts.deny. Surely you'd just blank out hosts.deny and put ALL: ALL (or just in.telnetd: ALL) into hosts.allow? Then it allows everyone to connect to telnet. If this is what you meant by adding the names to the host file then ignore this, but I had this problem once before and this solved it. Come to think of it. Another problem I had was with an old version of Slackware where it seemed to have some sort of corruption in the telnet daemon. It would also do the same thing as if you had a dodgy hosts.allow/.deny set but it would actually zombie the telnet processes and you could not get rid of them with any kill option. You actually had to reboot the machine to get it to connect again. This was from Slakware 3.4(or 3 if there was one.. old one anyway). A quick download and install of an updated version of the daemon and things were fine. Paul There is no /etc/resolv.conf as it's an isolated database server and has no connections to any other server.. Is there a way to get the TCP wrapper or whatever it is that's trying to resolve these machines to ignore resolving and just allow the connection quickly..? thanks, George Vieira Network Administrator http://www.citadelcomputer.com.au PGP Fingerprint : 43DC 92AC 1A82 27B2 E97B 52F1 B60F 301A 38A9 A10C PGP KeyID: 0x38A9A10C -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug -- --- Paul Robinson Web Developer / Programmer Centre for Flexible Learning Macquarie University NSW 2109, Australia Voice: +61 2 9850 8424 Email: [EMAIL PROTECTED] --- -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug
RE: [SLUG] Slow initial telnet.
No the problem is not a allow/deny problem as it eventually lets you in but takes forever. I just found out one of the other guys had put an entry in the /etc/resolv.conf which had a 10.10.0.X address for our DNS server in it which may have caused the delay as nslookup doesn't like 10.x.x.x or 172.16.x.x or 192.168.x.x addresses to resolve from, when I used an internet valid IP it works well from my experience.. I removed the entry and it starts up real damn quick.. weird that it MUST resolve these addresses. Must find a way to ignore them.. thanks anyway... it works for now. thanks, George Vieira Network Administrator http://www.citadelcomputer.com.au PGP Fingerprint : 43DC 92AC 1A82 27B2 E97B 52F1 B60F 301A 38A9 A10C PGP KeyID: 0x38A9A10C -Original Message- From: Paul Robinson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 17, 2000 8:19 AM To: George Vieira Cc: Sydney Linux Users Group in Sydney (E-mail) Subject: Re: [SLUG] Slow initial telnet. George Vieira wrote: Hi all, I know this is an oldie question but my initial telnet connections take forever to connect. It connects and then you wait for a minute before getting the logon message. I know the oldie answer was to remove `named` as the server was trying to resolve the IP address but named isn't running on this system. Also adding the names to the host file works but isn't the answer for me as this server is going to a site which will have remote WAN connections. When you say adding the names to the host file do you mean just /etc/host or the whole set including hosts.allow and hosts.deny. Surely you'd just blank out hosts.deny and put ALL: ALL (or just in.telnetd: ALL) into hosts.allow? Then it allows everyone to connect to telnet. If this is what you meant by adding the names to the host file then ignore this, but I had this problem once before and this solved it. Come to think of it. Another problem I had was with an old version of Slackware where it seemed to have some sort of corruption in the telnet daemon. It would also do the same thing as if you had a dodgy hosts.allow/.deny set but it would actually zombie the telnet processes and you could not get rid of them with any kill option. You actually had to reboot the machine to get it to connect again. This was from Slakware 3.4(or 3 if there was one.. old one anyway). A quick download and install of an updated version of the daemon and things were fine. Paul There is no /etc/resolv.conf as it's an isolated database server and has no connections to any other server.. Is there a way to get the TCP wrapper or whatever it is that's trying to resolve these machines to ignore resolving and just allow the connection quickly..? thanks, George Vieira Network Administrator http://www.citadelcomputer.com.au PGP Fingerprint : 43DC 92AC 1A82 27B2 E97B 52F1 B60F 301A 38A9 A10C PGP KeyID: 0x38A9A10C -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug -- --- Paul Robinson Web Developer / Programmer Centre for Flexible Learning Macquarie University NSW 2109, Australia Voice: +61 2 9850 8424 Email: [EMAIL PROTECTED] --- -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug
Re: [SLUG] Slow initial telnet.
On Tue, 17 Oct 2000, George Vieira generated: There is no /etc/resolv.conf as it's an isolated database server and has no connections to any other server.. How can you telnet to it if it has no connections? Is there a way to get the TCP wrapper or whatever it is that's trying to resolve these machines to ignore resolving and just allow the connection quickly..? telnet with the IP address instead of the machine name and it won't have to resolve the name. Otherwise make sure your nameservers are listed correctly in /etc/resolv.conf and they are working and accepting connections from this database server. -- No, I was looking for warez. The pornography was just a useful byproduct. -- Dave Coote -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug
RE: [SLUG] Slow initial telnet.
What I meant by connections is that there will be no communication between this server and any other servers, eg.. no gateway, no dns server, nothing.. it's a stand alone server with an IPchains rule to not accept any connections except the workstations allowed. I opened this up for testing and it's not IPCHAINS (obviously coz I eventually connect OK after 30 seconds or so). I do telnet with the IP address, it's the linux box that's trying to resolve my IP address connection before giving me my login screen. As I mentioned before, I removed the /etc/resolv.conf file and it's lightening fast. It's quite possible that it's syslogd trying to resolve as it does say it in the man pages and it tries 10 times before spitting the dummy. thanks, George Vieira Network Administrator http://www.citadelcomputer.com.au PGP Fingerprint : 43DC 92AC 1A82 27B2 E97B 52F1 B60F 301A 38A9 A10C PGP KeyID: 0x38A9A10C -Original Message- From: James Wilkinson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 17, 2000 9:59 AM To: Sydney Linux Users Group in Sydney (E-mail) Subject: Re: [SLUG] Slow initial telnet. On Tue, 17 Oct 2000, George Vieira generated: There is no /etc/resolv.conf as it's an isolated database server and has no connections to any other server.. How can you telnet to it if it has no connections? Is there a way to get the TCP wrapper or whatever it is that's trying to resolve these machines to ignore resolving and just allow the connection quickly..? telnet with the IP address instead of the machine name and it won't have to resolve the name. Otherwise make sure your nameservers are listed correctly in /etc/resolv.conf and they are working and accepting connections from this database server. -- No, I was looking for warez. The pornography was just a useful byproduct. -- Dave Coote -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug
RE: [SLUG] Slow initial telnet.
I've found that this whole problem is a local name lookup problem. The file /etc/hosts stores things that can be quickly looked up. I've found by adding lines in here that say what the current hostname is of the machine and the correct ip address(s) - all of them, then it makes it alot faster. The DNS client will probably look at /etc/hosts first then try the server and setting in /etc/resolv.conf - unless you have changed the order - forgotten where. dave I removed the entry and it starts up real damn quick.. weird that it MUST resolve these addresses. Must find a way to ignore them.. -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug
RE: [SLUG] Slow initial telnet.
The problem is this site is bit and there is also going to be a remote site logging in too.. I don't want to sit there entering host names for simple workstation activity. Fine if it's a known server but not worried about workstations. thanks, George Vieira Network Administrator http://www.citadelcomputer.com.au PGP Fingerprint : 43DC 92AC 1A82 27B2 E97B 52F1 B60F 301A 38A9 A10C PGP KeyID: 0x38A9A10C -Original Message- From: David Kempe [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 17, 2000 11:58 AM To: George Vieira Cc: Sydney Linux Users Group in Sydney (E-mail) Subject: RE: [SLUG] Slow initial telnet. I've found that this whole problem is a local name lookup problem. The file /etc/hosts stores things that can be quickly looked up. I've found by adding lines in here that say what the current hostname is of the machine and the correct ip address(s) - all of them, then it makes it alot faster. The DNS client will probably look at /etc/hosts first then try the server and setting in /etc/resolv.conf - unless you have changed the order - forgotten where. dave I removed the entry and it starts up real damn quick.. weird that it MUST resolve these addresses. Must find a way to ignore them.. -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug
RE: [SLUG] Slow initial telnet.
On Tue, 17 Oct 2000, George Vieira wrote: I removed the entry and it starts up real damn quick.. weird that it MUST resolve these addresses. Must find a way to ignore them.. Your real fix is in /etc/nsswitch.conf Here you set several lines to "files [NOTFOUND=return]" - especially the hosts (DNS lookup) line... tom. Consultant AUSSECPhone: 61 4 1768 2202 339 Blaxland Rd., Ryde NSW 2112 Email: [EMAIL PROTECTED] -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug
RE: [SLUG] Slow initial telnet.
Great, thanks heaps. That was the real answer I was looking for... thanks to all others too.. George Vieira Network Administrator http://www.citadelcomputer.com.au PGP Fingerprint : 43DC 92AC 1A82 27B2 E97B 52F1 B60F 301A 38A9 A10C PGP KeyID: 0x38A9A10C -Original Message- From: tom burkart [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 17, 2000 2:12 PM To: George Vieira Cc: Sydney Linux Users Group in Sydney (E-mail) Subject: RE: [SLUG] Slow initial telnet. On Tue, 17 Oct 2000, George Vieira wrote: I removed the entry and it starts up real damn quick.. weird that it MUST resolve these addresses. Must find a way to ignore them.. Your real fix is in /etc/nsswitch.conf Here you set several lines to "files [NOTFOUND=return]" - especially the hosts (DNS lookup) line... tom. Consultant AUSSECPhone: 61 4 1768 2202 339 Blaxland Rd., Ryde NSW 2112 Email: [EMAIL PROTECTED] -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug
