From jj@ldjpc.apana.org.au  Wed Mar 29 10:31:47 1995
Received: from yarrina.connect.com.au (yarrina.connect.com.au [192.189.54.17]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA24085 for <FreeBSD-gnats-submit@freebsd.org>; Wed, 29 Mar 1995 10:31:45 -0800
Received: from ldjpc.apana.org.au (ldjpc.apana.org.au [192.203.213.254]) by yarrina.connect.com.au with ESMTP id EAA19357
  (8.6.10/IDA-1.6 for <FreeBSD-gnats-submit@freebsd.org>); Thu, 30 Mar 1995 04:31:07 +1000
Received: (from jj@localhost) by ldjpc.apana.org.au (8.6.9/8.6.9) id WAA01015; Wed, 29 Mar 1995 22:03:22 +0930
Message-Id: <199503291233.WAA01015@ldjpc.apana.org.au>
Date: Wed, 29 Mar 1995 22:03:22 +0930
From: Lucas James <jj@ldjpc.apana.org.au>
Reply-To: jj@ldjpc.apana.org.au
To: FreeBSD-gnats-submit@freebsd.org
Subject: Network seems to be funny 
X-Send-Pr-Version: 3.2

>Number:         284
>Category:       kern
>Synopsis:       Network gives permission denied
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    markm
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Mar 29 10:40:02 1995
>Closed-Date:    Thu Feb 8 08:22:34 PST 1996
>Last-Modified:  Thu Feb  8 08:27:55 PST 1996
>Originator:     Lucas James
>Release:        FreeBSD 2.1.0-Development i386
>Organization:
>Environment:



>Description:

after a reboot:
Telnet to the local machine gives permission denied (even as root)
kerberos doesn't work.
innd doesn't work et.al.

(a telnet to the nntp port also give permission denied.)

>How-To-Repeat:

jj@ldjpc> telnet ldjpc
Trying 192.203.213.254...
telnet: Unable to connect to remote host: Permission denied
jj@ldjpc> telnet ldjpc nntp
Trying 192.203.213.254...
telnet: Unable to connect to remote host: Permission denied
jj@ldjpc> su
su: kerberos: unable to su: Retry count exceeded (send_to_kdc)
Password:
root@ldjpc# telnet ldjpc nntp
Trying 192.203.213.254...
telnet: Unable to connect to remote host: Permission denied
root@ldjpc# 

>Fix:

This doesn't appear to be a kerberos problem since telnet to the nntp
port also fails.  Is it possible that there is still a kerberos interaction
problem?

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: pst 
State-Changed-When: Wed Feb 7 16:20:12 PST 1996 
State-Changed-Why:  
Is this still present? 


Responsible-Changed-From-To: freebsd-bugs->wollman 
Responsible-Changed-By: pst 
Responsible-Changed-When: Wed Feb 7 16:20:12 PST 1996 
Responsible-Changed-Why:  
Kerberos & Networking experts... do you thing. :-) 
I saw no obvious networking problem.  Telnet doesn't need to be setuid. 
Responsible-Changed-From-To: wollman->markm 
Responsible-Changed-By: wollman 
Responsible-Changed-When: Thu Feb 8 08:13:33 PST 1996 
Responsible-Changed-Why:  
This looks like it's either an installation error or a Kerberos 
problem.  Kerberos problems belong to markm and/or gibbs. 
State-Changed-From-To: feedback->closed 
State-Changed-By: markm 
State-Changed-When: Thu Feb 8 08:22:34 PST 1996 
State-Changed-Why:  
This is nearly identical to a problem I had when first setting up kerberos. 
A combination of a wrong kerberos setup and errors in my inetd.conf 
had me running around in circles for a few days.  

Unfortunately there is not enough info in this PR to conclusively 
state what happened. 


>Unformatted:



