similar to: 1 out of 5 wnt 4sp3 machines acts up

Can the "tar" function in SMBCLIENT be used to successfully backup and restore a remote WNT 4 sp3 system disk? I'm guessing no, because: 1. active registry files, so restored disk may not be bootable 2. loss of ACLs and other "extra" file properties in tar format Anybody tried it? This is for machines with SCSI adapters, so even if we have to replace the system disk

I tried building the 2.0.x alpha from the CVS site on our new Linux box - but no joy. It allowed WNT 4sp3 boxes to mount a share using the domain username/password, but it wouldn't let users log onto the consoles of the WNT boxes using the same domain username/password combinations. (The log file from the interaction was not very useful - it was created for each machine which tried, but had

Hi, How does one configure NT 4 workstation so that it will take the username/password pair typed in by the user on the console, and pass it to a PDC (in this case, Samba) for workstation/Domain login verification? Further details: The server (1.9.19, yes, I know that's alpha) is configured to be a PDC. We have several hundred Unix accounts, for which both the username and password are

A samba server (2.0.2 linux/intel) is the primary domain server for "SAF". 5 workstations (nt 4sp3 intel) belong to this domain. In order to trash the event viewer, do the following: As administrator: 1. select any file (on C:, this has nothing to do with samba file sharing) 2. properties 3. audit 4. add at this point it tries to look up the users in SAF, fails, and Dr. Watson

We're running an older version of Samba on an Irix machine, and just got 2.0.2 working (finally!) on our Intel/Linux box. The odd thing, is that findsmb gives different results on the two systms. On Irix it lists the NetBIOS names with OS descriptions, but on Linux it lists the IP name and no OS description. I went through it line by line and found the first difference at: ../nmblookup -r

Hi, I'm running the Alpha of 1.9.19 (we needed Samba as a domain controller) and want to know the best way to set it up so that the first login for a new user on an WNT workstation in that domain creates the profile we want for the user, rather than the one NT seems to want. 1. The profile created is about .5 Mb in size. The parts that we want in there are maybe 20% of that. How does

> Date: 30 Nov 1998 20:22:27 GMT > From: mathog@seqaxp.bio.caltech.edu > To: mlist-samba@nntp-server.caltech.edu > Subject: W95/98 connect to any SMB share as another user? > Message-ID: <73uuq3$s7j@gap.cco.caltech.edu> > > map H: as \\machine1\share1 as username=John, password=JohnsPassword map > M: as \\machine2\share2 as username=Jane, password=JanesPassword >

Setting up nut on a system where an LVM volume holds the root filesystem.. What is the appropriate device form to use with "mdadm --readonly" in halt? This is on a CentOS 5 system. So far I have found three possibilities, but I do not know which one (if any) will still be valid that late in the halt procedure: 1. /dev/md0 (from posts on the net) 2.

I recently ran into a situation where a Samba upgrade apparently broke the machine records in the smbpasswd file, with the resulting symptom that domain logons on those computers would fail about 95% of the time. (A very strange symptom, how it worked sometimes is still a mystery to me.) Similarly, this would fail: % smbclient -L saf01 -U 'saf/mathog%(password)' session setup failed:

Well this is even more interesting. Parts of the profile are not being saved back to the server, at least for existing users. For instance, 1. login 2. change the start menu to "classic view" 3. rearrange the desktop 4. logout 5. login again start menu is back as it was and it isn't classic view any more. Very strange. Wipe the test profile on the server and the copy on the

Yesterday I migrated a Samba server from one machine running Samba 3.0.13 (on Mandrake 10.0) to another running 3.0.20-3 (on Mandriva 2006). The contents of: /etc/samba/* (all the .conf files) /usr/local/samba/private/* (secrets.pdb, smbpasswd) were moved intact from one machine to the other, as was all of the user data. I even checked md5sums - no changes to any of the samba files. Then

Upgraded a Samba server from 3.0.28a-2 to 3.4.7-0.2. Initially the XP workstations could not log on (not finding machine account) then discovered a new "passdb" variable, so added to smb.conf: passdb backend = smbpasswd and also changed all browseable -> browsable. Restarted the server. Domain logins worked. Test files saved to desktop are retained between logins (are stored in

Help please, a file server was upgraded from: Mandriva 2007.1, Samba 3.0.24-2.7mdv2007.1 to Mandriva 2008.1, Samba 3.0.28a-2.1mdv2008.1 and it broke something badly. After the upgrade logins from all XP workstations broke - some of the time. For an existing account (one with a profile already in the home directory) sometimes it will login normally. Well, almost normally, it never seems

> The domain user does login eventually. Mostly. Roaming Profiles are > very broken on W7: the top level "Vista.V2" directory is created, but > nothing is stored back into it on the server, and the logged in domain > user ends up with a C:\Users\Temp profile. Thanks to Drew Vonada-Smith the roaming profiles are working again. The problem was that information stored in

After update from 3.0 to 3.4.7 roaming profiles were not being saved on XP. Disabled ipv6 on our Samba server (some update must have re-enabled it) and rebooted. Now profiles on XP seem to be working OK again. Not so for Windows 7. This is a newly set up Windows 7 machine, registry fixes were applied as indicated here: http://wiki.samba.org/index.php/Windows7 was able to join domain, and

After doing some system work, including upgrading the Samba server to 3.0.28a from 3.0.24, upgrading the kernel to 2.6.24, and changing the firewall rulesk, the XP workstations which belong to that domain, the right click "run as ..." option is slow to bring up a dialog. The phenotype is this: right click some program (for instance, a shortcut to the "command prompt")

Just in case anybody else ever needs these, here are my semi-automated powershell cloning scripts for Windows domain clients for Samba domain servers. ftp://saf.bio.caltech.edu/pub/software/windows/Cloning.zip They are not very polished, but do what I need, and could serve as a starting point for other sites. These have been tested only on XP SP3. These scripts do not use sysprep, so the

Dovecot 2.0.13 on a 64 bit linux. We have an archiver account on one machine. Most mailing lists that handles go directly to it and everything is fine. However, there is one campus list that will only send to real people. So for that one I subscribed. When one of these messages comes in, which is 1-2x per week, I copy it to an export folder and then manually run a script which does: cat

I am trying to automate W7 joining to our Samba domain. It works fine through the Windows GUI from the W7 workstations. However, for a script one would have to store password used for domain access, and since that is the server's root password, I really don't want to hard code that into a file. Is there a way to set (temporarily) a Samba server so that it will accept (admin/anything) as

I did a test shutdown on a nut controlled UPS and it all went as expected except that when it got to: /usr/local/ups/bin/upsdrvctl shutdown Nothing happened. So the halt script went on and shut down the system. I waited a while but the UPS never turned itself off. Am I doing something wrong, or does this UPS not support this function? Thank you, David Mathog mathog at caltech.edu Manager,