krb5kdc: No such device - Cannot bind server socket to port 88

Jim Pharis binbrain at gmail.com
Wed Jun 22 16:59:29 EDT 2005


My kdc will not start. I get an error message in my kdc log file...

krb5kdc[11331](info): listening on fd 7: udp 192.168.0.1.88
krb5kdc[11331](info): listening on fd 8: udp 192.168.0.1.750
krb5kdc: No such device - Cannot bind server socket to port 88 address
fe88::20f:1fff:feb2:b9c7%253

ifconfig shows that address associated eth1. I statically assigned
192.168.0.1 to that address. (no network). If I bring eth1 down I get
a message set up 0 sockets.

I can check the ports opened by nmap'ing myself. The port isn't
allocated.

I tried binding to that port with a python script and I have no
problem opening it.

Has anybody seen this before? By the way, I did create the principle and
stash files and they are pointed to correctly in the kdc.conf and
krb.conf files.  admin-server seems to start correctly and opens the
port.

I'm running Ubuntu Hoary. Is the KDC trying to bind to the ip6 address?
I have seen threads of other people with this problem but none of them
lead to any insight into how one might fix it.

TIA, Jim Pharis

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://mailman.mit.edu/pipermail/kerberos/attachments/20050622/836ac350/attachment.bin


More information about the Kerberos mailing list