[Bug 521085] Re: Samba 3.4.0 denies access to Roaming Profiles for XP Clients

[Rolf Leggewie]

Karmic has long since stopped to receive any updates. Marking the Karmic
task for this ticket as "Won't Fix".

** Changed in: samba (Ubuntu Karmic)
       Status: New => Won't Fix

-- 
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/521085

Title:
  Samba 3.4.0 denies access to Roaming Profiles for XP Clients

Status in “samba” package in Ubuntu:
  Fix Released
Status in “samba” source package in Karmic:
  Won't Fix

Bug description:
  Binary package hint: samba

  Source Package: samba_2:3.4.0-3ubuntu5.4
  Ubuntu Release: 9.10 (Karmic 64-bit AMD Server)

  This is basically the same problem as reported in Bug #397699; however
  the problem persists in Karmic (9.10) and has not been fixed, as far
  as I can tell.  Using an smb.conf file which worked perfectly for
  (Debian) samba_3.0.2-2, one gets something similar to the following
  error message when trying to login using a roaming profile on a
  Windows XP machine:

  "Windows did not load your roaming profile and is attempting to log
  you on with your local profile. Changes to the profile will not be
  copied to the server when you logoff. Windows did not load your
  profile because a server copy of the profile folder already exists
  that does not have the correct security. Either the current user or
  the Administrator's group must be the owner of the folder. Contact
  your network administrator."

  Deleting the profile and starting with a clean slate allows the user
  to login and logout again, however the message above is repeated upon
  a subsequent attempt to login.

  I tried every suggestion I could find to fix this, including such ill-
  advised steps as chmod'ing the permissions on the profile to 1777.

  My original profile share configuration in smb.conf looked like this:
  [profile]
     create mode = 0600
     directory mode = 0700
     path = /home/%U/profile
     read only = no
     profile acls = yes
     browseable = yes

  One suggestion involved changing the create and directory mode masks
  as follows:

  [profile]
     force create mode = 0777
     force directory mode = 0777
     path = /home/%U/profile
     read only = no
     profile acls = yes
     browseable = yes

  This did not solve the problem.  As far as I can tell, the bug
  reported for Jaunty samba 3.3.2 has not been fixed for Karmic samba
  3.4.0.

  Given the importance of Samba in many linux server environments, the
  fact that this was not tested more thoroughly before  Karmic was
  released is frankly shocking and disappointing.

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