Conference smurf::buildhelp

1667.0. "kerberos routing problem with ronyon/flume?" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Fri Aug 11 1995 16:17

Date Of Receipt: 	 9-AUG-1995 17:57:11.83
From: 	SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE  09-Aug-1995 1754"
To: 	glidden@DEC:.zko.flume
CC: 	admin@DEC:.zko.flume, binder@DEC:.zko.flume, odehelp@DEC:.zko.flume,
	mcmullen@dec:.zko.super
Subj: 	kerberos routing problem with ronyon/flume?

Mark, can you take a look at this?  The user is, I'm guessing from
what I see, on flume trying to use ode, from server ronyon (man pool),
and (I think) it's hitting the error of kerberos taking different routes
from the kerberos server and the ode server to the client.  
Error message:
 no authorization to access the server: Incorrect network address (krb_rd_req)
 kxct: Kerberos error: Unknown protocol version number (kerberos)

Using the new -d debug switch on the new kinit, I can see that, at this
moment, flume's authenticating to buffer:

flume-60 % /usr/sde/ode3.0/tools/alpha_OSF1/bin/kinit -d 
Kerberos Initialization
Kerberos name: Joshua_Friedman
lrealm is ZONE
krb_udp_port is 60930
Getting host entry for kerberos1.zk3.dec.com...Got it.
Sending message to 16.140.112.22...Sent
Waiting for reply...received packet from 16.140.112.22
Received it
Clen is 88
Password: 

flume-61 % nslookup kerberos1
Server:  flume.zk3.dec.com
Address:  16.140.112.3

Name:    buffer.zk3.dec.com
Address:  16.140.112.22
Aliases:  kerberos1.zk3.dec.com

 

Buffer's not doing anything wierd for routing that I can see:
 
buffer# traceroute ronyon
traceroute to ronyon.zk3.dec.com (16.140.112.222), 30 hops max, 40 byte packets
 1  ronyon (16.140.112.222)  7 ms  1 ms  1 ms

buffer# traceroute flume
traceroute to flume.zk3.dec.com (16.140.112.3), 30 hops max, 40 byte packets
 1  flume (16.140.112.3)  1 ms  90 ms  1 ms


------- Forwarded Message

Return-Path: [email protected] 
Delivery-Date: Wed, 09 Aug 95 16:39:08 -0400
Return-Path: [email protected]
Received: from DECnet-Mail11.flume.zk3.dec.com by flume.zk3.dec.com; 
(5.65v3.2/1.1.8.2/16Jan95-0946AM)
	id AA09097; Wed, 9 Aug 1995 16:31:31 -0400
Date: Wed, 9 Aug 1995 16:31:30 -0400
Message-Id: <[email protected]>
From: [email protected] (Sarah & Julia's Dad)
To: [email protected], [email protected]
Cc: MCMULLEN
Subject: Errors trying to bco and blog

From:	CALIPH::binder "vitam gustare"  9-AUG-1995 16:25:27.45
To:	super::mcmullen
CC:	
Subj:	Re:  Errors trying to bco and blog; Joyce's watchmail refers ODE to you

Joe, I don't know what the problem is.  You're in the ACLs.  Please
send a query to odehelp or jmf (Josh Friedman).

Sorry I can't help you.

- -dick
======================================================================
From:	FLUME::mcmullen "Joe McMullen "  9-AUG-1995 15:31:27.16
To:	demers@DEC:.zko.flume
CC:	mcmullen@DEC:.zko.flume
Subj:	Errors trying to bco and blog

Joyce, I tried to blog and bco socket.2, with these results: (this is after
doing ki)

flume:ptman> bco socket.2

[ ./BASE/OSF/man2/socket.2 ]
no authorization to access the server: Incorrect network address (krb_rd_req)
kxct: Kerberos error: Unknown protocol version number (kerberos)

No longer using cached authorization
bco: The following rcs command failed:
authcover exists ./BASE/OSF/man2/socket.2,v
[ unable to access source control information in file: 
"./BASE/OSF/man2/socket.2
,v"  ]
flume:ptman> blog socket.2

[ ./BASE/OSF/man2/socket.2 ]
no authorization to access the server: Incorrect network address (krb_rd_req)
kxct: Kerberos error: Unknown protocol version number (kerberos)

No longer using cached authorization
no authorization to access the server: Incorrect network address (krb_rd_req)
kxct: Kerberos error: Unknown protocol version number (kerberos)

No longer using cached authorization
no authorization to access the server: Incorrect network address (krb_rd_req)
kxct: Kerberos error: Unknown protocol version number (kerberos)

No longer using cached authorization
blog: The following rcs command failed:
authcover rlog -r ./BASE/OSF/man2/socket.2,v


------- End of Forwarded Message