From owner-freebsd-questions Tue Feb 17 21:32:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA23020 for freebsd-questions-outgoing; Tue, 17 Feb 1998 21:32:41 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from mirageport.com (mirageport.com [204.134.94.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22979 for ; Tue, 17 Feb 1998 21:32:14 -0800 (PST) (envelope-from cowan@mirageport.com) Received: from hercules.mirageport.com (hercules.mirageport.com [204.134.94.35]) by mirageport.com (8.8.8/8.8.8) with SMTP id WAA08816; Tue, 17 Feb 1998 22:33:20 -0700 (MST) Message-ID: <053c01bd3c2e$90381a80$235e86cc@hercules.mirageport.com> From: "Cowan Bowman" To: "Timothy Toroni" , Subject: Re: Connect & prompt times. Date: Tue, 17 Feb 1998 22:32:11 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: Timothy Toroni To: freebsd-questions@FreeBSD.ORG Date: Tuesday, February 17, 1998 10:13 PM Subject: Connect & prompt times. >I'm running FreeBSD RESLEASE-2.2.5 on a 486dx33 with 8meg of memory. I >also have an 3c509(?)... the epX device. > >The computers in question are: >normandy.torpedogames.com 10.0.0.101 >iwojima.torpedogames.com 10.0.0.104 > >I am running the DNS server on normandy and it works great, my win95 >machine is able to to use it fine. > >The problem is that when I telnet or ftp to the computer(s) it connects >immediately but then sits for over a minute. Once I get the login >prompt I can login fine. When I run netstat it also takes over a >minute, what's up? >When this happens I have the /etc/resolv.conf as: >domain torpedogames.com >nameserver 10.0.0.101 Check to see if reverse DNS is setup correctly. >If I rem out the nameserver line or put an invalid IP address in then it >connects and displays the login prompt immediately however the DNS no >longer works. What can I do to fix this? What's really causing this? > >Also, another question. What do I have to edit so I can login as root >via telnet? As a temporary fix I added another user to the wheel group >in /etc/group then su to root after logging on as the user but I assume >there has to be a better way. I've looked around in the >/etc/login.access but couldn't get anywhere. Setting up another user in /etc/group then a su to root is the secure way to do it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message