similar to: Reality Check -> Roaming Profiles

Recent list messages got me thinking... Is there a way to support both local and roaming profile with one server / domain? As I understand it, the "magic" line that tells Samba not to do roaming profiles is the smb.conf line: logon path = Which the line must exist, and must be set to null. But that is in the global section. So is there a way to support both local and roaming...

I have a network comprised of a linux server (mandrake) running samba 3.0.4 as a PDC and clients all being windows xp. I am in the process of doing a practice run of roaming profiles and am currently stuck. What is the most common way to prevent two of the workstations from logging into the pdc and thus corrupting the roaming profile? Ive googled this till im blue in the face and am getting

Hey all, Relatively new to Samba configuration here - I've set up a system where XP clients can login and get their roaming profiles and all is well with that, but I see the synchronization which takes place on logout to be a big problem. So, I'm looking to turn off roaming profiles and instead go with remapping the documents, desktop and pictures folders to their server

I'm trying to locate the list of registry values to adjust how Win2K clients handle the user profile with the Win2K boxes joined to a Samba PDC and logging in with domain accounts. Specifically I would like to DISABLE roaming profiles!!! Many moons ago, the WarpServer Win2K client from IBM came with very good documentation on how to adjust that client to not create roaming profiles, etc...

Hi list, a strange problem occurs in samba 3.0.8 (Debian 3.0.8-2 package): When a Domain-User tries to log off (WinXP SP2), the workstation fails to store the profile in the PROFILE-Path. The message "cannot store \\SERVER\Profiles\Administrator\Recent" pops up. But this is only the half truth. The directory for the user (f.e. Administrator) is been created. A few files are copied

I have Samba 3 running on gentoo as a pdc. I read in someone's forum posting to try enabling acls and that didn't seem to do much good. I can get the computers to be added to the domain using their smb username/passwords and when they login, the correct shares corresponding to their users map perfectly; however, my biggest problem is when they do login it says the following: Windows

hi all... i have a little problem with an include statement in my smb.conf. what i want to achieve is to allow the "administrator" user access to "read/write/browse" to all the users home drives under "/array2/samba/homes" can anyone see why even after the include file was added, the administrator user is not able to browse /array2/samba/homes/* ? [homes]

Greetings- I am wondering if anyone from the Samba team would happen to have interest in creating official builds for Ubuntu? To add a twist, unfortunately I would not be fishing for 7.10 packages, but rather 7.04 as we ran into too many issues with 7.10 whereas 7.04 seems rock solid stable. Or, are there packages built of Samba releases for Ubuntu external to samba.org? Thanks, -- Michael

Greetings- I am working through coming up with a Linux client integration to Samba PDC's. I mount several shares with this sort of syntax: /bin/mount -t cifs -o credentials=/home/userid/.smbcredentials,uid=userid,gid=userid,dmask=0777,fmask=0666 //ldslnx01/data /mnt/ldslnx01/data/ However when I create new files/dirs on the Samba share from the Linux workstation, the perms are not 0666/0777

One of the servers we admin has countless such errors in log.smbd: [2007/05/07 14:17:08, 0] tdb/tdbutil.c:tdb_log(783) tdb(/var/cache/samba/printing/HPLJ3600.tdb): rec_read bad magic 0x443810ec at offset=28412 The only thread I saw regarding "rec_read" stated: <><><><><> If this really happens often to you, then you have some basic problems with your

man smb.conf does not specifically say admin users supports @groupname syntax. Google turns up lots of examples of it being used, but everyone hanging their smb.conf's up to air does not mean they are 100% accurate either. Here, Samba 3.0.4 in PDC mode, I can not get it to accept the name of a group in /etc/group, user ID's only. -- Michael Lueck Lueck Data Systems Remove the upper

Hi everyone, I'm about to install a Samba PDC in a network that previously was working as a workgroup. All the users have been logging into their local machines as "administrator" and all with the same password. What I would really like to do is to move their profiles with them, but as they are all using the same username and the like I can see this is going to cause problems. So

I am testing out Debian Etch, and ran into an issue granting SeMachineAccountPrivilege to an account... which granting that permission had been troublesome in the past. The command I am issuing is: net rpc rights grant LDS-DEMO\\ldsinst SeMachineAccountPrivilege And I try running the command with an account that is a member of the "Domain Admins" group. The command returns: Failed to

Is there a trick to append an additional directory level onto the defauly behavior of a [homes] share looking in /etc/passwd to find the users Linux home dir? It would offer a bit of protection if Windows clients ended up in say the WinHome directory within their Linux home directory when logging in from Windows so they are not tempted to tamper with their desktop settings files for Linux from

I am logged into a new test Linux server with my personal admin account. It is a member of a Linux group which has been mapped to Domain Admins. When I issue 'net rpc rights grant auserid SeMachineAccountPrivilege' and enter the password for my personal admin account, I am returned that it failed with NT_STATUS_NO_SUCH_PRIVILEGE. 'auserid' is both a Linux account and has been

I have a share which a group write list. That group is mapped to a Linux group in /etc/group. That group in Linux has two users. The first user listed is suddenly unable to write, but the second one is. With the affected user logged in to Win2K, ifmember /list shows they are a member of the group, as does the working account. I am guessing one of those .tdb files or something got scrambled on the

We have bumped into a most odd problem. Server: Debian Etch and their Samba 3.0.24-2 Client: WinXP SP2, MSI v3, all hot fixes The following settings are in place on the server: #!/bin/bash # # initGrps.sh # Map Windows Domain Groups to UNIX groups net groupmap add ntgroup="Domain Admins" unixgroup=domadmin rid=512 type=d net groupmap add ntgroup="Domain Users"

<rant>Every time I set up a new test Samba server, the step to "net rpc rights grant..." ALWAYS fights me tooth and nail... ALWAYS with a different error message. I've even created little scripts to run so I am not typing commands incorrectly... but NNNOOOOOO, the script to grand rights to one stink'n account always has to complain!</rant> OK, this time it is...

Greetings- I have not found discussed / documented what to do with machine accounts when moving a Samba PDC to new hardware. I have seen that uid/gid numbers must match between the old/new system. I am thinking to use adduser to accomplish that, then make the numbers on the new server match, using a text editor. After that, can I simply enter the machine account entries by hand with a text

I see that the w32time service as it is configured when a Win2K Pro client joins a Samba PDC Domain is not configured in such a way that the service is able to successfully sync time with Samba. I:\>w32tm -source -v W32Time: BEGIN:InitAdjIncr W32Time: Adj 100144 , Incr 100144 fAdjust 0 W32Time: END:Line 2503 W32Time: BEGIN:TsUpTheThread W32Time: END Line 1407 W32Time: TimeMMInit()