similar to: Problems with migrating from local to roaming profiles

Hi, I have recently upgaded from samba 2.2 to samba 3.0. I used to have "domain admin group = @winadmin" in my smb.conf, but I understand from the documentation that it is deprecated in favour of "net groupmap set "Domain Admin" winadmin". I would expect unix users who are members of the unix group winadmin to become Domain Admins, then, but they don't ?. Do I

Hai Marco, Ok thats strange, this works fine since Jessie and up. I did some extra checks and i'll show my outputs so you can compaire them. My "domain" admin shows : id winadmin uid=10000(winadmin) gid=10000(domain users) groups=10000(domain users),116(lpadmin),10001(domain admins),2001(BUILTIN\users),2000(BUILTIN\administrators) My group output: getent group lpadmin

Created an "add machine" script that basically looks for an unused uid/rid, and then creates a stub LDAP entry for the machine; the first time I issue "net join", the script is invoked and creates the LDAP entry correctly, but the join operation fails nevertheless: f1sa:~# net -U winadmin join winadmin's password: [2006/09/08 10:19:40, 0] utils/net_ads.c:ads_startup(191)

On Wed, 13 Jun 2018 17:07:39 +0200 Marco Gaiarin via samba <samba at lists.samba.org> wrote: > Mandi! L.P.H. van Belle via samba > In chel di` si favelave... > > > Ok thats strange, this works fine since Jessie and up. > > Ahe,, probably i'm not explaining me well. I've not 'windows' > troubles, i've troubles accessing CUPS web interface,

Hi, i have a Ubuntu x64 10.04 Server. Samba configured as PDC. Since today i experience that roaming prfiles can't copy one file to the server and shout an error message. It's no specific file, mostly its one in my Thunderbird Profile. Does anybody know what could this cause to happen? My smb.conf: [global] printing = bsd netbios name = PDC server string = PDC (%h)

Hi. I've just installed Samba 2.2.8 (SuSE Linux 8.0). My clients are running Win2000 Pro. I'm struggeling with the printer setup. Could anybody route me to an detailed step-by-step guide on how to do this right OR maybe explain it to me? What I have is this: ------------------- [print$] comment = Printers ... path = /home/ANDROMEDA/printers write list =

Hi, i've finally have my LDAP backend working for authentication for my DC. Logon scripts are executed, user is authenticated, but my roaming profiles are not found. here is what i have in my config files: smb.conf [global] printing = bsd netbios name = PDC server string = PDC (%h) workgroup = workgroup interfaces = eth0,lo security = user encrypt passwords =

I'm having a problem wtih 2.2.6pre2 that I seem unable to resolve. When logging out of my Win2K SP3 machine, I receive the error "Windows cannot update the roaming profile. The system cannot find the file specified." Checking the archives and google brings up several references to errors around the copying of ntuser.dat from the local machine, to a temporary file on the

How to set up roaming profiles that samba doesn't download whole profiles, only necessary files ntuser.ini ntuser.dat eg. end rest of registry settings? I would like to setup profiles running (downloading) fast from server when clients login. Clients XP PRO SP3. Samba ver. 3.0.33-3.29.el5_5 Which file form samba registry should I use to force using roaming profiles :

Hi After changing from samba 2.2.7 to 3.0.rc2 I can't get roaming profiles work. Clients Are W2K and XP. I've also switched from smbpasswd backend to ldap. Logon path is only set in smb.conf, not in ldap. Storing of profiles is working but it takes very long. I've tried logon path = \\wilma2\profile\Win2K and \\wilma2\profile. But the clients are always storing profile in

HEllo, i am running samba 3.0.14a with this smb.conf file: [global] netbios name = redhat workgroup = net2day server string = PDC [on Redhat :: Samba server %v] security = user encrypt passwords = yes socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 hosts allow = 192.168.0.0/24 127.0.0.1 interfaces = lo eth0 bind interfaces only = yes local master = yes os level = 65 domain master = yes

Hello everyone! I'm facing a big problem with the samba server I just set up: System: FreeBSD 5.4 Samba ver: 3.0.20 (previuosly 3.0.12) Client(s): Windows XP Professional I configured the server to make use of roaming profiles. I was able to copy local profiles to the server, to login and voila - got my desktop. Also after creating a new user, the new profile gets copied to the server,

I had the same problem. We used samba 3.0.14 and upgraded to 3.0.20 After that profile were not loaded anymore. Th problen you are discribing looks like Windows is loading the local copy of your profile and after you deleted it it tries to load the profile from samba and fails. I found out that we had problems with "profile acls = Yes" wich was needed by the earlier samba releases.

Hi list, I am faced by a strange problem w/ one of our 10 win2k/sp3 clients in a samba2.2.8a pdc-network. If I want to logon I get a message like this(translated from german): "Your profile has not been loaded, but you will be logged in to a local Profile. Your serverside profile has not been loaded because its security-properties are not properly." and that's it. Even if I blast my

[samba v3.0.24, gentoo w/ kernel 2.6.15] I'm hoping someone has some insight into the following problem that I've recently encountered: Basically, winxp seems to be creating roaming profiles that are incompatible with another winxp client. I've got two sets of winxp clients, which I'll call 'new' and 'old'. Profiles created (and perfectly usable) by the old

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm about to migrate a load of profiles from an old Windows DC to our new Samba4 DC (well, the file server is Samba 3.6.6). Could anyone advise me on how to go about migrating these across. As I've noticed that just shifting the profile data from the old domain to the new one doesn't appear to work for non-Xp profiles (and for all I

Hi, Yesterday I found big problems concerning my roaming profiles. They seem to work on some computers where they are always used, on some other the did not load properly (i.e. a default profile was loaded instead). After some debugging with userenv.log I found the very strange problem: case sensitivity for ntuser.dat!: [...] IsCentralProfileReachable: Testing <F:\testuser\ntuser.dat>

I am seeing these in smb.log and each time I do it appears that the user in question is unable to retrieve their roaming profile. Does anyone know what is going on and more importantly, how to cure it? . . . [2017/03/28 16:24:37.426162, 0] ../source3/smbd/oplock.c:713(oplock_timeout_handler) Oplock break failed for file Administrator/AppData/Roaming/Microsoft/Internet Explorer/Quick

I need a little advice on finishing off a Samba PDC. I have Samba 3.0.0RC1 installed and working as a PDC on a Redhat AS 3.0 machine. It authenticates users nicely but the "roaming" profiles don't work. Tailing the samba log, I see the an attempt to access the users ntuser.dat file, which doesn't exist before the first logon, when logging in. The profile directory

Through much help from a guy in my local LUG I found the solution to making roaming profiles work on Win2000 (SP4). 1) You should have SP4 installed. 2) Two registry changes are needed: Use regedit and change the following two dword attributes to 0 "requiresignorseal" "signsecurechannel" 3) Run the group policy editor "gpedit.msc" and enable the