similar to: Roaming profiles is not working

I've searched the archives for an answer to this problem, and yet nothing that works seems to have been posted. I've seen it posted many times In my particular case, I'm running Samba 2.0.6 on Solaris 2.5.1, configured with the --with-smbwrapper, --with-automount, and --with-syslog options. I also have samba set up as a PDC, and that seems to be working fine. A stripped down

Hi, since we did an upgrade from samba 3.0.28 to samba 3.4.x we have trouble with roaming profiles. Currently we are running samba 3.4.3. When logging on, the profile folder on fileserver is created, but the user gets an error message: ---- 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

Okay, I don't have much hair left and I am ready to pull it out. I am running samba 2.2.7a as a PDC for Windows XP clients. Everything works fine for DOMAIN users who are in the administrators group on the XP workstation. My problem is if users are in the Power Users or Users group on the XP client, then when the log out changes to their profiles are not saved back to the server. I know

Hello samba dancers, I'm Friedrich Strohmaier and new to this mailing list. More important: I'm (very) new to PDCing Computers in a network, and I ran in big troubles doing so. Try to tell a long story in short: I'm a fairly experienced administrator for linux systems, and was orderd to move a serverinstallation (SuSE7.0, Samba2.2.x) to a new machine. The old machine did stop

Hi Rene, I have found this in the "whats new" for Samba 2.2.3 Added/changed parameters. ------------------------- ... nt acl support This parameter has been changed to a per-share option, and is very useful in enabling Windows 2000 SP2 to load/save profiles from a Samba share. ... Maybe it helps! Regards, Thomas Bitte antworten an <rene.lenga@atacama.de> Gesendet von:

Hello samba-insiders, we have a WinNT 4.0 SP5 PDC and our samba 2.2.3a is member of the domain. The roaming profiles of our clients stored on the samba 2.2.3a server. All seams to be perfect but only clients with W2K SP2 cannot use there roaming profiles. ---> "Access Denyed" is the W2K errro message. But if the same user loggs on on a client machine with W2K SP1 all things are ok.

Hello samba-insiders, we have a WinNT 4.0 SP5 PDC and our samba 2.2.3a is member of the domain. The roaming profiles of our clients stored on the samba 2.2.3a server. All seams to be perfect but clients with W2K SP2 cannot use there roaming profiles. ---> "Access Denyed" is the W2K error message. But if the same user loggs on on a client machine with W2K SP1 all things are ok. In

Hi, since rolling out roaming profiles, some user profiles are growing very fast. I like to keep the profiles small and think about changing ExcludeProfileDirs default settings in Software\Microsoft\Windows NT \CurrentVersion\Winlogon by System Policies to remove caches, cookies, recent and other "useless" stuff. Which paths could be excluded without "killing" the benefits

Hi to all, nt acl support = no for the profile share solved the problem. But why? > -----Urspr?ngliche Nachricht----- > Von: samba-admin@lists.samba.org > [mailto:samba-admin@lists.samba.org]Im > Auftrag von Sylvestre Taburet > Gesendet: Donnerstag, 7. M?rz 2002 13:27 > An: thomas_tiedtke@de.schindler.com; rene.lenga@atacama.de > Cc: samba@lists.samba.org >

We recently upgraded our samba 3.6 network to samba 4.2.3. It is still a NT-style domain. The underlying OS was upgraded from CentOS 5 to CentOS 7. The profiles share is set up like this: [profiles] comment = Roaming Profiles path = /mnt/share2/ntprofiles browseable = no writable = yes csc policy = disable create mask = 0600 directory mask

Hi. I have a xen virtualized samba server. Today i was experiment a very strange situation. Practically all the stations are windows XP. Some station are vista or 7, but they are not connected to the domain yet. I have just 1 win7 logged on the domain, and today, after restart the samba server, the station cant load the apps correctly. We use roaming users and use a centraliced access

We have been directed to move off a SAMBA domain to a server 2003R2 domain. We run roaming profiles with samba and would like to continue this on 2003R2. After bringing all the XPSP3 desktops into the 2003R2 domain, roaming profiles wont work. I'm not even trying to use the SAMBA generated profiles. The error I get when logging on is: *Windows cannot locate the server copy of your

Hi everyone , Recently upgraded to 2.2.5 on RH73 and suddenly my Roaming profiles did stop working and on top of this my NMBD is giving me constant errors!!!! when i try nmblookup -U 127.0.0.1 _SAMBA_ name_query fail to find name _Samba_ then i have tried : nmblookup -B 192.168.123.1 MYSERVER and then : nmblookup -U 127.0.0.1 MYSERVER 192.168.123.1 MYSERVER<00> looks fine after this i

I've been browsing the archive and googling for something like 3 days now and still haven't found where the problem is. Here the situation: Samba 2.2.8a acting as a PDC Some Win2kSP3 clients The problem: When a user logon for the first time, a cache profile is created locally, when he logoff, that profile is saved on the PDC. It's working as expected. The problem arise when the

Hi all, I've got a Samba PDC working on Slackware 9.0 with clients running Win2k SP3 French. Everything runs fine, except one thing. I suppose you guessed what... (eh... no? erm...) the roaming profile. I've been googling / reading howtos / searching the archive for some time now, still can't find what is the problem. Here's the behaviour i get: Everything is ok, the profile get

Ever since I upgraded Samba from 3.0.x to 3.4.x, and reconfigured it to support Windows 7 clients, I am having issues with roaming profiles on my Windows XP clients. All the machines have been rejoined to the domain, domain authentication appears to be working fine, the home drive is mounted ok, and the profile information is even read, but never updated upon logout. A user with no profile will

Due to hardware failure we had a rushed migration from a Samba v3.0.9 on FreeBSD 4, to v3.0.10 on Mandrake Linux 10.1. Since then I have had problems getting roaming profiles to work for new users. Things works fine for existing users, but things are broken for new ones. The setup is a fairly standard Samba PDC with Windows XP clients. When users added since the upgrade log in, they then do

Hello. I've configured roaming profiles on my server. But they are working very strange. When I log in from a Windows XP machine with the user 'test' I get an error message saying that the machine can't find a server copy of my roaming profile and is logging on using the default local profile. In details it says that the network name cannot be found. But after logging in and after

I'm finding our employees' roaming profiles are not being updated. They were initially created correctly, they copy down onto a new machine, but updates are not put back onto the server. I've also noticed that smbstatus does not show any open dat files, such as ntuser.dat. I would have assumed that these files would have been held open while the client was connected. Employees can

hi ! thanks now I have my samba up and running fine. I have it configured as a PDC, and all the roaming profiles work, the management, etc. it's all fine. now, the client that I'm working for, told me ( after some days of making it all work ) that he sees that the use of roaming profiles in his network is useless. ok now, he says no roaming profiles ! I have searched around the network