> Is there nothing listening on *any* port 88/UDP ? or is it just on a
different IP?

Nothing on port 88/UDP for any IP, if I'm understanding lsof correctly.
Likewise nothing on any port 389/UDP:

leo@blackbox:~$ sudo lsof | grep UDP
named     1114            bind  512u     IPv6               8584      0t0       
 UDP *:domain
named     1114            bind  513u     IPv4               8589      0t0       
 UDP localhost:domain
named     1114            bind  514u     IPv4               8591      0t0       
 UDP blackbox:domain
named     1114            bind  515u     IPv4               9501      0t0       
 UDP 192.168.122.1:domain
samba     1214            root   22u     IPv4               8899      0t0       
 UDP *:netbios-ns
samba     1214            root   23u     IPv4               8900      0t0       
 UDP *:netbios-dgm
samba     1214            root   24u     IPv4               8901      0t0       
 UDP 10.37.55.255:netbios-ns
samba     1214            root   25u     IPv4               8902      0t0       
 UDP blackbox:netbios-ns
samba     1214            root   26u     IPv4               8903      0t0       
 UDP 10.37.55.255:netbios-dgm
samba     1214            root   27u     IPv4               8904      0t0       
 UDP blackbox:netbios-dgm
dnsmasq   1243 libvirt-dnsmasq    5u     IPv4               8936      0t0       
 UDP *:bootps
dnsmasq   1243 libvirt-dnsmasq    6u     IPv4               8942      0t0       
 UDP 192.168.122.1:domain
leo@blackbox:~$

This is the same as the sudo lsof | grep UDP output provided in comment
#5 - except that for some reason these IP/port combinations now no
longer get (specific) listeners:

samba 1298 root 24u IPv4 7075 0t0 UDP 192.168.122.255:netbios-ns
samba 1298 root 25u IPv4 7076 0t0 UDP 192.168.122.1:netbios-ns
samba 1298 root 26u IPv4 7077 0t0 UDP 192.168.122.255:netbios-dgm
samba 1298 root 27u IPv4 7078 0t0 UDP 192.168.122.1:netbios-dgm

Again, this is when the machine has been started with the Ethernet cable
plugged in: the lsof results when the system has been started with the
cable plugged *out* are in comment #13.

(Also compare the sudo lsof | grep *TCP* output after a cable-in boot
(comment #5) and a cable-out boot (comment #13): there are also TCP
ports without listeners in the cable-in case.)

> Is there any output in the log file?

Nothing is written to /var/log/samba/log.samba when kinit is run, and
nothing relevant is written to /var/log/syslog either. This is true
regardless of whether the machine was last started with the Ethernet
cable plugged out (and thus has samba processes listening on 88/UDP) or
not. There *are* system-startup-time error messages in
/var/log/samba/log.samba , and they are different depending on whether
the Ethernet cable was plugged in or not. I'll upload those next, along
with the corresponding /var/log/syslog entries.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/976138

Title:
  kerberos setup fails, with broken krb5.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/976138/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to