FedoraForum.org - Fedora Support Forums and Community
Results 1 to 15 of 15
  1. #1
    Join Date
    Dec 2004
    Location
    Cambridge, MA
    Posts
    89
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    fedora 11 - xp roaming profiles with samba pdc no longer works after upgrade

    i was successfully using samba + fedora directory server in fedora 10 as a primary domain controller for my home network (achieved mostly by following barry905's instructions here: http://forums.fedoraforum.org/showthread.php?t=183837).

    after upgrading to fedora 11, some of the pdc functionality no longer worked.

    for example, when i ran 'pdbedit -Lv', i got:

    Code:
    # pdbedit -Lv htpc
    Failed to issue the StartTLS instruction: Protocol error
    Connection to LDAP server failed for the 1 try!
    Failed to issue the StartTLS instruction: Protocol error
    Connection to LDAP server failed for the 1 try!
    Failed to issue the StartTLS instruction: Protocol error
    Connection to LDAP server failed for the 1 try!
    Unix username:        htpc
    NT username:          htpc
    Account Flags:        [U          ]
    User SID:             S-1-5-21-662797068-642394324-2295719409-3006
    Failed to issue the StartTLS instruction: Protocol error
    Connection to LDAP server failed for the 1 try!
    Failed to issue the StartTLS instruction: Protocol error
    Connection to LDAP server failed for the 1 try!
    Failed to issue the StartTLS instruction: Protocol error
    Connection to LDAP server failed for the 1 try!
    Primary Group SID:    S-1-5-21-662797068-642394324-2295719409-513
    Full Name:            HTPC
    Home Directory:       \\MYHOST\htpc
    HomeDir Drive:        P:
    Logon Script:
    Profile Path:         \\MYHOST\profiles\htpc
    Domain:               MYDOMAIN
    Account desc:
    Workstations:
    Munged dial:
    Logon time:           0
    Logoff time:          Mon, 18 Jan 2038 22:14:07 EST
    Kickoff time:         Mon, 18 Jan 2038 22:14:07 EST
    Password last set:    Wed, 18 Feb 2009 23:09:57 EST
    Failed to issue the StartTLS instruction: Protocol error
    Connection to LDAP server failed for the 1 try!
    Password can change:  Wed, 18 Feb 2009 23:09:57 EST
    Failed to issue the StartTLS instruction: Protocol error
    Connection to LDAP server failed for the 1 try!
    Password must change: never
    Last bad password   : 0
    Bad password count  : 0
    Logon hours         : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
    i was able to fix this by adding to the [global] section in /etc/samba/smb.conf:

    Code:
            ldap ssl = off
    i also found that i could no longer join an xp computer to the domain. i discovered that for some reason, the samba administrator password had been cleared. after running:

    Code:
    # smbpasswd -w myadminpassword
    that was fixed.

    the last problem, which i have still not fixed, is that roaming profiles no longer work. when i try to do a domain login as user 'htpc' from an xp machine, i get the following message in xp:

    Code:
    Your roaming profile is not available. You
    are logged on with the locally stored
    profile. Changes to the profile will not be
    copied to the server. Possible causes of
    this error include network problems or
    insufficient security rights. If this problem
    persists, contact your network
    administrator.
    
    DETAIL - Access is denied.
    however, once logged in i can directly browse to the profiles directory \\MYHOST\profiles\htpc in windows explorer. i can also access all of my samba shares normally.

    anyone have an idea why xp can no longer access the roaming profile? this is happening from multiple xp clients. and remember, this all worked fine in fedora 10.

    here's an excerpt of my /etc/samba/smb.conf:

    Code:
    # Samba config file created using SWAT
    # from UNKNOWN ()
    # Date: 2009/02/19 00:55:51
    
    [global]
            workgroup = MYDOMAIN
            server string = Samba Server Version %v
            interfaces = vnet0, lo
            bind interfaces only = Yes
            smb ports = 139
            security = USER
            passdb backend = ldapsam:ldap://localhost
            log file = /var/log/samba/log.%m
            max log size = 50
            load printers = No
            add user script = /usr/sbin/smbldap-useradd -m "%u"
            rename user script = /usr/sbin/smbldap-usermod -r "%u"
            delete user script = /usr/sbin/smbldap-userdel "%u"
            add group script = /usr/sbin/smbldap-groupadd -p "%g"
            delete group script = /usr/sbin/smbldap-groupdel "%g"
            add user to group script = /usr/sbin/smbldap-groupmod -m "%u" "%g"
            delete user from group script = /usr/sbin/smbldap-groupmod -x "%u" "%g"
            set primary group script = /usr/sbin/smbldap-usermod -g "%g" "%u"
            add machine script = /usr/sbin/smbldap-useradd -w "%u"
            logon drive = P:
            logon home = \\%N\%U
            domain logons = Yes
            preferred master = Yes
            domain master = Yes
            wins support = Yes
            ldap admin dn = cn=Directory Manager
            ldap group suffix = ou=Groups
            ldap idmap suffix = ou=Idmap
            ldap machine suffix = ou=Computers
            ldap suffix = dc=mynetwork,dc=net
            ldap user suffix = ou=People
            ldap ssl = off
            idmap uid = 10000-20000
            idmap gid = 10000-20000
            create mask = 0664
            directory mask = 0775
            map acl inherit = Yes
            cups options = raw
    
    [profiles]
            comment = Windows User Profiles
            path = /home/samba/profiles
            read only = No
            create mask = 0600
            directory mask = 0700
            profile acls = Yes
    #       browseable = No
    
    [homes]
            comment = Home Directories
            path = /home/%S/share
            valid users = %S
            read only = No
            browseable = No

  2. #2
    Join Date
    Dec 2004
    Location
    Cambridge, MA
    Posts
    89
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    still searching for clues. here's what i've tried. as in above, the user is called 'htpc'.

    i copied the current profile /home/samba/profiles/htpc to a backup file /home/samba/profiles/htpc.backup and then tried to login from the xp machine, hoping a new profile would be created. i get the same error "Your roaming profile is not available." however, a new profile directory is created:

    Code:
    [root@myhost profiles]# ls -al
    drwx------+  2 htpc Domain Users 4096 2009-06-18 17:22 htpc
    drwx------. 15 htpc Domain Users 4096 2009-05-17 21:46 htpc.backup
    the new directory 'htpc' is empty, however. hmm, it has a '+' at the end of directory permissions. is this a clue? i check the acls for the directories:

    Code:
    [root@myhost profiles]# getfacl htpc.backup
    # file: htpc.backup
    # owner: htpc
    # group: Domain\040Users
    user::rwx
    group::---
    other::---
    
    [root@myhost profiles]# getfacl htpc
    # file: htpc
    # owner: htpc
    # group: Domain\040Users
    user::rwx
    group::---
    other::---
    default:user::rwx
    default:group::---
    default:other::---
    i don't really know what it means, if anything. but maybe there is a problem in the permissions. so i delete the 'htpc' directory and change the file creation and directory masks to 777 in smb.conf:

    Code:
    [profiles]
            comment = Windows User Profiles
            path = /home/samba/profiles
            read only = No
    #       create mask = 0600
            create mask = 0777
    #       directory mask = 0700
            directory mask = 0777
            profile acls = Yes
            csc policy = disable
    #       browseable = No
    and restart samba. try to login from the xp machine again. still get "Your roaming profile is not available." then, from windows explorer, i browse to \\myhost\profiles and manually create a folder 'htpc.test' and do `ls -al` at the samba host again:

    Code:
    [root@myhost profiles]# ls -al
    drwx------+  2 htpc Domain Users 4096 2009-06-18 17:34 htpc
    drwx------. 15 htpc Domain Users 4096 2009-05-17 21:46 htpc.backup
    drwxrwxrwx+  2 htpc Domain Users 4096 2009-06-18 17:35 htpc.test
    this is strange. the directory 'htpc' created by the windows login process still has permissions 700. however, the directory 'htpc.test' created by me manually in windows explorer has permissions 777 which is what i expect since that's the directory mask i specified in smb.conf. is there some permissions problem, or is this a red herring?

  3. #3
    Join Date
    Dec 2004
    Location
    Cambridge, MA
    Posts
    89
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    more clues. it does seem to be a permissions problem. continuing where i left off in my last post, i decide to set the permissions for the 'htpc' directory to 777. remember, at this point, 'htpc' is an empty directory:

    Code:
    [root@myhost profiles]# chmod 777 htpc
    [root@myhost profiles]# ls -al
    drwxrwxrwx+  2 htpc Domain Users 4096 2009-06-19 13:40 htpc
    drwx------. 15 htpc Domain Users 4096 2009-05-17 21:46 htpc.backup
    [
    now try logging in as user 'htpc' from the xp machine--success! no message saying that the roaming profile can't be found, and it logs right in. then i log out to see if the new profile is written into the 'htpc' directory. now i get this error:

    Code:
    Windows cannot copy file C:\Documents
    and Settings\htpc\Templates to location
    \\MYHOST\profiles\htpc\Templates.
    Possible causes of this error include
    network problems or insufficient security
    rights. If this problem persists, contact
    your network administrator.
    
    DETAIL - Access is denied.
    and then another message saying that my roaming profile can't be updated. if i look into the 'htpc' directory, i see:

    Code:
    [root@myhost htpc]# ls -al
    -rwx-w--w-  1 htpc Domain Users 262144 2009-06-19 13:46 NTUSER.DAT
    -rwx-w--w-  1 htpc Domain Users   1024 2009-06-19 13:46 ntuser.dat.LOG
    -rwx-w--w-  1 htpc Domain Users     20 2009-06-18 17:51 ntuser.ini
    so part of the profile did get written, it just can't seem to create new directories.

    starting over, i restore my original profile folder and recursively set 777 permissions for it:

    Code:
    [root@myhost profiles]# cp -a htpc.backup/ htpc
    [root@myhost profiles]# chmod -R 777 htpc
    [root@myhost profiles]# ls -al htpc
    drwxrwxrwx. 12 htpc Domain Users    4096 2009-01-22 13:31 Application Data
    drwxrwxrwx.  2 htpc Domain Users    4096 2009-03-14 12:31 Cookies
    drwxrwxrwx.  2 htpc Domain Users    4096 2008-02-15 23:39 Desktop
    drwxrwxrwx.  3 htpc Domain Users    4096 2008-12-20 14:18 Favorites
    drwxrwxrwx.  2 htpc Domain Users    4096 2007-11-30 23:32 .GalleryRemote
    drwxrwxrwx.  5 htpc Domain Users    4096 2008-12-20 14:18 My Documents
    drwxrwxrwx.  8 htpc Domain Users    4096 2008-02-03 17:50 NetHood
    -rwxrwxrwx   1 htpc Domain Users 2097152 2009-05-17 21:49 NTUSER.DAT
    -rwxrwxrwx   1 htpc Domain Users    1024 2009-05-17 21:49 ntuser.dat.LOG
    -rwxrwxrwx   1 htpc Domain Users     178 2009-05-17 21:46 ntuser.ini
    drwxrwxrwx.  2 htpc Domain Users    4096 2006-05-18 17:13 PrintHood
    drwxrwxrwx.  2 htpc Domain Users    4096 2009-05-16 22:51 Recent
    drwxrwxrwx.  2 htpc Domain Users    4096 2006-05-18 21:31 SendTo
    drwxrwxrwx.  3 htpc Domain Users    4096 2006-05-18 17:13 Start Menu
    drwxrwxrwx.  2 htpc Domain Users    4096 2006-05-18 21:22 Templates
    drwxrwxrwx.  6 htpc Domain Users    4096 2007-07-04 17:00 UserData
    log in from the xp machine--success. log out from the xp machine--success. and the profile does get updated (note the updated file time for ntuser.dat):

    Code:
    [root@myhost profiles]# ls -al htpc
    drwxrwxrwx. 12 htpc Domain Users   4096 2009-01-22 13:31 Application Data
    drwxrwxrwx.  2 htpc Domain Users   4096 2009-03-14 12:31 Cookies
    drwxrwxrwx.  2 htpc Domain Users   4096 2008-02-15 23:39 Desktop
    drwxrwxrwx.  3 htpc Domain Users   4096 2008-12-20 14:18 Favorites
    drwxrwxrwx.  2 htpc Domain Users   4096 2007-11-30 23:32 .GalleryRemote
    drwxrwxrwx.  5 htpc Domain Users   4096 2008-12-20 14:18 My Documents
    drwxrwxrwx.  8 htpc Domain Users   4096 2008-02-03 17:50 NetHood
    -rwxrw-rw-   1 htpc Domain Users 524288 2009-06-19 13:57 NTUSER.DAT
    -rwxrw-rw-   1 htpc Domain Users   1024 2009-06-19 13:57 ntuser.dat.LOG
    -rw-rw-rw-   1 htpc Domain Users    178 2009-06-19 13:57 ntuser.ini
    drwxrwxrwx.  2 htpc Domain Users   4096 2006-05-18 17:13 PrintHood
    drwxrwxrwx.  2 htpc Domain Users   4096 2009-05-16 22:51 Recent
    drwxrwxrwx.  2 htpc Domain Users   4096 2006-05-18 21:31 SendTo
    drwxrwxrwx.  3 htpc Domain Users   4096 2006-05-18 17:13 Start Menu
    drwxrwxrwx.  2 htpc Domain Users   4096 2006-05-18 21:22 Templates
    drwxrwxrwx.  6 htpc Domain Users   4096 2007-07-04 17:00 UserData
    so this is definitely a permissions problem. as long as the permissions are set so that everyone has rwx access, the windows xp login process has no problems accessing the roaming profile. why would this have changed from f10 to f11? i still don't see why the file and directory masks in smb.conf aren't being obeyed by the xp login process.

  4. #4
    Join Date
    Nov 2004
    Location
    Ontario, Canada
    Age
    51
    Posts
    160
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Hi bbobbo; I'm also running into this exact same issue after upgrading to F11. I've tried erasing the profile from a workstation, running "sudo chmod u+rwx -R" on my user directory in the profiles share, but the issue still persists.

    I haven't had time to do much else yet as I've got another, more serious problem on the same server I'm trying to fix, but I'm following your posts with interest!

  5. #5
    Join Date
    Jan 2005
    Posts
    5,057
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    The xp clients need to be updated to post sp3 until the fix in 3.3.4
    F11 is using 3.3.2
    There has been 3.3.3, 3.3.4, and 3.3.5

    smaba is moving very fast due to the new info from M$ and the samba4 code coming together.
    I think 3.4.0+ will end most of the crud.

    SJ
    Do the Math

  6. #6
    Join Date
    Dec 2004
    Location
    Cambridge, MA
    Posts
    89
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    mlavalle: glad to see i'm not the only one experiencing this problem. i thought i was talking to myself for a while.

    slowjet: my xp client machines all have sp3 installed. thanks for the tip about samba 3.3.4, though. this item in the changelog seems particularly encouraging:

    o Simo Sorce
    * Fix writing of roaming profiles with "profile acls" set to "yes".
    (from http://samba.org/samba/history/samba-3.3.4.html)

    i think the latest version of samba i was using in f10 was 3.2.11. maybe when i get some time i can peruse the changelogs of the intervening releases and see if anything jumps out.

    in the meantime, i guess the fix is to 'chmod -R 777' the 'profiles' directory and to change the file and directory masks to 777 in smb.conf.

  7. #7
    Join Date
    Jun 2009
    Posts
    3
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I have the same problem in Windows XP SP3 with all updates.
    With fedora 10 all are ok, after upgrade to fedora 11 this problem appeared:

    Your roaming profile is not available. You
    are logged on with the locally stored
    profile. Changes to the profile will not be
    copied to the server. Possible causes of
    this error include network problems or
    insufficient security rights. If this problem
    persists, contact your network
    administrator.

    DETAIL - Access is denied.

    Somebody has a solution for this?

  8. #8
    Join Date
    Dec 2004
    Location
    Cambridge, MA
    Posts
    89
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by thieme.reis
    I have the same problem in Windows XP SP3 with all updates.
    With fedora 10 all are ok, after upgrade to fedora 11 this problem appeared:

    Your roaming profile is not available. You
    are logged on with the locally stored
    profile. Changes to the profile will not be
    copied to the server. Possible causes of
    this error include network problems or
    insufficient security rights. If this problem
    persists, contact your network
    administrator.

    DETAIL - Access is denied.

    Somebody has a solution for this?
    i mentioned a temporary fix in the post right above yours:

    in the meantime, i guess the fix is to 'chmod -R 777' the 'profiles' directory and to change the file and directory masks to 777 in smb.conf.
    otherwise, i think we just have to wait until the fedora samba packages gets updated.

  9. #9
    Join Date
    Jul 2009
    Posts
    4
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Having similar issue, though it was not an upgrade, I moved from a test install of f9 samba and FDS (ldap) to f11 samba and FDS because someone mentioned that the issues I was having with adding Win7 to the domain worked in f11. I haven't gotten to the WIn7 testing yet because I have spent about a day fixing everything that didn't work when I used the same samba config.

    Anyway I have gotten to the point where the profiles are being dynamically created when a user logs in for the first time, however I am still getting the error and nothing is being written to the users profile directory.

    I used 1777 -R on the profile directory.

    Any suggestions?

  10. #10
    Join Date
    Dec 2004
    Location
    Cambridge, MA
    Posts
    89
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    did you try the file and directory mask settings in the [profiles] section in smb.conf?

    Code:
    [profiles]
            comment = Windows User Profiles
            path = /home/samba/profiles
            read only = No
            create mask = 0777
            directory mask = 0777
            profile acls = Yes
            csc policy = disable

  11. #11
    Join Date
    Jul 2009
    Posts
    4
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I actually found the solution after talking with someone on irc. It turns out that these smb.conf options:

    Code:
    create mask = 0777 
    directory mask = 0777
    perform an AND function on the directory permissions and actually do the opposite of what the intent is. By adding the following I was able to get samba to create the profile directories as new users login, no more error messages and their profiles are saved as they log out:

    Code:
    force create mode = 0777
    force directory mode = 0777
    What I am starting to piece together is that some of the smb.conf functionality was "broken" in previous 3.2.X versions and was corrected in the f11 version 3.3.2-0.33.fc11. This would explain why some of these new parameters are needed though I used the same options from the config file from my f9 install.

    I also had a StartTLS issue using ldapsam where I had to use ldap ssl = off to turn off StartTLS even though I did not have to do the same thing in f9.

    It looks like you were able to fix existing users, did you have the same luck with new users as they logged in?

  12. #12
    Join Date
    Dec 2004
    Location
    Cambridge, MA
    Posts
    89
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by ciphyre
    I actually found the solution after talking with someone on irc. It turns out that these smb.conf options:

    Code:
    create mask = 0777 
    directory mask = 0777
    perform an AND function on the directory permissions and actually do the opposite of what the intent is. By adding the following I was able to get samba to create the profile directories as new users login, no more error messages and their profiles are saved as they log out:

    Code:
    force create mode = 0777
    force directory mode = 0777
    the AND function on the directory permissions doesn't do the opposite of what the intent is. rather, it specifies the maximum set of permissions allowable for the file/directory.

    for instance, if the file mask is 0777, and some program tries to write a file with permissions 0644, the file will get permissions 0644. but if the file mask is 0444 and the program tries to write a file with permissions 0666, the file will get written with permissions 0444.

    Quote Originally Posted by ciphyre
    What I am starting to piece together is that some of the smb.conf functionality was "broken" in previous 3.2.X versions and was corrected in the f11 version 3.3.2-0.33.fc11. This would explain why some of these new parameters are needed though I used the same options from the config file from my f9 install.

    I also had a StartTLS issue using ldapsam where I had to use ldap ssl = off to turn off StartTLS even though I did not have to do the same thing in f9.

    It looks like you were able to fix existing users, did you have the same luck with new users as they logged in?
    i haven't tried with any new users (this is just my home network), but i suspect that it will work.

  13. #13
    Join Date
    Jun 2009
    Posts
    3
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Samba update profile

    This solve the problem:

    Update samba from:
    http://admin.fedoraproject.org/updat....4.0-0.39.fc11
    and update libtalloc to version 1.3.1 from fedora update testing repository (else samba do not
    start)
    http://download.fedora.redhat.com/pu....fc11.i586.rpm

    See: https://bugzilla.redhat.com/show_bug.cgi?id=508760

  14. #14
    Join Date
    Dec 2004
    Location
    Cambridge, MA
    Posts
    89
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by thieme.reis
    This solve the problem:

    Update samba from:
    http://admin.fedoraproject.org/updat....4.0-0.39.fc11
    and update libtalloc to version 1.3.1 from fedora update testing repository (else samba do not
    start)
    http://download.fedora.redhat.com/pu....fc11.i586.rpm

    See: https://bugzilla.redhat.com/show_bug.cgi?id=508760
    great news. i'll wait for the fix to be released to the updates repository, which should be soon enough.

  15. #15
    Join Date
    Jun 2009
    Posts
    3
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Samba: Update profile

    I update and now all work fine!

Similar Threads

  1. Sound no longer works after Fedora 10 upgrade
    By jspot in forum Installation, Upgrades and Live Media
    Replies: 0
    Last Post: 24th January 2009, 05:02 PM
  2. Samba, Vista RC1, and Roaming Profiles
    By merton in forum Servers & Networking
    Replies: 3
    Last Post: 26th November 2006, 12:29 AM
  3. Samba Server... ?Roaming Profiles ?Something else
    By polc1410 in forum Servers & Networking
    Replies: 0
    Last Post: 28th May 2006, 12:24 PM
  4. Roaming Profiles (SAMBA 3)
    By masterlodi in forum Servers & Networking
    Replies: 1
    Last Post: 22nd March 2005, 02:28 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •