lunt@shadow.bellcore.com (Steve Lunt) (08/15/90)
When trying to restart the kerberos server on my machine, I get an
error message "Can't bind socket" (errno 48: address already in use). When I
do an rpcinfo -p, I find:
program vers proto port
100026 1 udp 750 bootparam
But port 750 is the port reserved for kerberos in /etc/services:
kerberos 750/udp kdc # Kerberos authentication--udp
I can't determine where bootparamd gets assigned port 750, but is there another
port to which I can assign the kerberos server so that it will not clash with
bootparamd? Is there thought to reassigning the kerberos service to another
port? I'm running SunOS 4.0.3 on a SPARCstation.
-- Steve
Steven J. Lunt | lunt@ctt.bellcore.com | RRC 1L-213
Computer Security Technology |-------------------------| 444 Hoes Lane
Bellcore | (201) 699-4244 | Piscataway, NJ 08854cmcmanis@Eng.Sun.COM (Chuck McManis) (08/15/90)
>I can't determine where bootparamd gets assigned port 750, but is there another >port to which I can assign the kerberos server so that it will not clash with >bootparamd? Is there thought to reassigning the kerberos service to another >port? I'm running SunOS 4.0.3 on a SPARCstation. Boot params like most RPC services that want a privledged port expect to be run _after_ you run any preassigned services. So start up kerberos first and then start boot params. Boot params doesn't care what port it gets (as long as it is privledged) since the portmapper will tell clients how to contact it. --Chuck
smb@ulysses.att.com (08/15/90)
When trying to restart the kerberos server on my machine, I get an error message "Can't bind socket" (errno 48: address already in use). When I do an rpcinfo -p, I find: program vers proto port 100026 1 udp 750 bootparam But port 750 is the port reserved for kerberos in /etc/services: kerberos 750/udp kdc # Kerberos authenticat ion--udp You're running afoul of Sun's portmapper. You have to fire up Kerberos first. For that matter, if you kill and restart bootparam, I think you'd get a different port. I forget exactly what range the portmapper will use; the real would have been to use a port number not in that range for Kerberos. Perhaps for V5?
db@witzend.East.Sun.COM (David Brownell) (08/15/90)
>I can't determine where bootparamd gets assigned port 750, but is there another >port to which I can assign the kerberos server so that it will not clash with >bootparamd? Is there thought to reassigning the kerberos service to another >port? I'm running SunOS 4.0.3 on a SPARCstation. If it's not rpc.bootparamd, it could be something else. Shouldn't Kerberos be using a registered port number (n < 512)? Don't tell me ... "fixed in v5"! ;-) David Brownell db@east.sun.com. "What's the network equivalent of 'the rough section of town'?"
sjl@doc.imperial.ac.uk (Steve J Lacey) (01/23/91)
Hi,
Just a quick question. Are the port numbers used by kerberos
registered?
They clashed with the numbers we use for aufs and so had to be
moved.
Steve.
-----
Steve J Lacey, Systems Group. (In my opinion, my opinions are just that.)
Department of Computing, Imperial College of Science, Technology and Medicine,
180 Queen's Gate, London SW7. Phone : 071 589 5111 x5085, Fax : 071 581 8024
Email : sjl@doc.ic.ac.uk, ..!ukc!icdoc!sjl, sjl@athena.mit.edu
--- All lines lead to Mornington Crescent ---jon@MIT.EDU (Jon A. Rochlis) (01/24/91)
Just a quick question. Are the port numbers used by kerberos registered? No. They clashed with the numbers we use for aufs and so had to be moved. I don't think this is true. Kerberos uses UDP 750, TCP 751 and 754. The old KIP ports are 769-776 and the registered KIP ports are in the 200's. (Various kerberized applications use other ports but none conflict with KIP) Also, if AUFS and Kerberos did conflict it wouldn't matter unless you intend to run an AUFS server on the same machine you run a Kerberos server. That would be a foolish thing to do. You don't want to run any services on your KDC machine that you don't need. -- Jon