[Bug 1292548] Re: Standalone Server: Update from Samba 2:3.6.18-1ubuntu3.1 (saucy) to 2:4.1.3+dfsg-2ubuntu3 (trusty) breaks access to the server

[Raoul Bhatia]

Dear Robie,

actually, it is quite easy to reproduce during an update from saucy to
trusty and i suspect that this bug will even strike when you do a clean
trusty install.

Nevertheless, i reproduced this issue with a fresh saucy install:

1. install saucy using http://at.mirror.archive.ubuntu.com/ubuntu/dists/saucy/main/installer-amd64/current/images/netboot/mini.iso
2. install openssh-server and samba-server during installation (via tasksel?)
3. reboot and verify samba status:
# root at ubuntu:~# smbstatus

Samba version 3.6.18
PID     Username      Group         Machine
-------------------------------------------------------------------

Service      pid     machine       Connected at
-------------------------------------------------------

No locked files

4. add a user and view list the available shares
# root at ubuntu:~# smbpasswd -a ubuntu
New SMB password:
Retype new SMB password:


# root at ubuntu:~# smbclient -L \\localhost -U ubuntu
Enter ubuntu's password:
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.6.18]

        Sharename       Type      Comment
        ---------       ----      -------
        IPC$            IPC       IPC Service (ubuntu server (Samba, Ubuntu))
        print$          Disk      Printer Drivers
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.6.18]

        Server               Comment
        ---------            -------
        UBUNTU               ubuntu server (Samba, Ubuntu)

        Workgroup            Master
        ---------            -------
        WORKGROUP            UBUNTU


5. do-release-upgrade -d (remove obsolete packages; reboot)

6. verify samba access (FAILS!)
--ubuntu at 192.168.122.233's password:
Welcome to Ubuntu Trusty Tahr (development branch) (GNU/Linux 3.13.0-18-generic x86_64)

 * Documentation:  https://help.ubuntu.com/

  System information as of Sat Mar 22 08:50:31 CET 2014


Last login: Sat Mar 22 08:41:59 2014 from rbi
ubuntu at ubuntu:~$ smbstatus

Samba version 4.1.3-Ubuntu
PID     Username      Group         Machine
-------------------------------------------------------------------
Failed to initialize session_global: NT_STATUS_ACCESS_DENIED

Service      pid     machine       Connected at
-------------------------------------------------------
Failed to initialize session_global: NT_STATUS_ACCESS_DENIED
Failed to traverse sessions: NT_STATUS_ACCESS_DENIED

No locked files

ubuntu at ubuntu:~$ smbclient -L \\localhost -U ubuntu
Enter ubuntu's password:
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 4.1.3-Ubuntu]
tree connect failed: NT_STATUS_ACCESS_DENIED



Please let me know in case you require this system as a KVM/QEMU disk image.

Cheers,
Raoul

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

Title:
  Standalone Server: Update from Samba 2:3.6.18-1ubuntu3.1 (saucy) to
  2:4.1.3+dfsg-2ubuntu3 (trusty) breaks access to the server

Status in “samba” package in Ubuntu:
  New

Bug description:
  I have been using Samba as a standalone server since many years and
  have successfully gone through multiple Samba upgrades.

  This week, I upgraded from Ubuntu 13.10 (saucy) to Ubuntu 14.04 (trusty).
  This came with an upgrade from Samba 2:3.6.18-1ubuntu3.1 (saucy) to 2:4.1.3+dfsg-2ubuntu3 (trusty).
  (NOTE: I did not use the samba4 package but was still sticking to Samba 3 in Ubuntu saucy)

  
  After the update, I wasn't able to access the shares any more.

  "smbclient -L localhost -U%" / "smbclient -L localhost -U user" resulted in various errors, including
  * tree connect failed: NT_STATUS_ACCESS_DENIED
  * (from session setup) not permitted to access this share (IPC$)
  * NT_STATUS_LOGON_FAILURE
  * string_to_sid: SID IPC_ is not in a valid format

  
  I was neither able to properly browse the server/shares via smbclient nor via Windows 7 Ultimate nor Windows 8.1.

  However, I was able to directly access a share from a Linux shell
  using "smbclient -U user //server/share-c ls".

  Not even purging samba, all related configuration, all folders,
  including /etc/samba, /var/cache/samba, /var/spool/samba,
  /var/lib/samba, and re-installing samba (Version  2:4.1.3+dfsg-
  2ubuntu3 from trusty) did the trick.

  
  Only after installing all related packages from Debian jessie (Version 2:4.1.5+dfsg-1), everything worked out of the box again.

  Thus, I think that something in the most recent Ubuntu Samba package
  might be broken and kindly ask you to investigate, as there will be
  several users who will upgrade and stick to this LTS release.

  Thanks,
  Raoul

  PS. I did not try Samba 4.0 (Package samba4*) on Ubuntu saucy and
  therefore cannot tell if these are working as expected.

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