search for: evilgenius

Given that rsync, smbclient and smbmount are all kissin' cousins, this seems like a good place to post this question. I'm building a linux backup server which will be archiving other linux and some NT servers. The Linux boxes are being rsynced over ssh, so everything is happy there. The NT servers were initially going to be smbmounted and rsynced, but this ended up hanging about 30%

...bind nss info = rfc2307 winbind trusted domains only = no winbind enum users = yes winbind enum groups = yes winbind nested groups = Yes winbind offline logon = Yes #======================= Share Definitions ======================= [netlogon] path = /usr/local/samba/var/locks/sysvol/dc1.evilgenius.net/scripts read only = No [sysvol] path = /usr/local/samba/var/locks/sysvol read only = No ;[homes] ; comment = Home Directories ; browseable = no

...gt; winbind enum groups = yes >> winbind nested groups = Yes >> winbind offline logon = Yes >> >> >> >> #======================= Share Definitions ======================= >> [netlogon] >> path >> = /usr/local/samba/var/locks/sysvol/dc1.evilgenius.net/scripts read >> only = No >> >> [sysvol] >> path = /usr/local/samba/var/locks/sysvol >> read only = No >> >> ;[homes] >> ; comment = Home Directories >> ; browseable = no >> >> > Can I also suggest repl...

Today we had a problem with our Win NT4 PDC and discovered numerous failover issues with our Samba file server. For starters, this is a Debian Etch machine running Samba-3.0.24-2. At this point, this is a critical production machine. Upgrading is on our to-do path, but is not an option for an immediate fix to this problem. With the exception of this problem, this Samba installation has been

...Rights (0x 400): Oct 4 13:56:15 harleyquinn smbd[17703]: Right[ 0]: SeRemoteInteractiveLogonRight These are repeated for various SIDs. Also, the samba-tool dbcheck is unable to fix the following: ERROR: incorrect GUID component for member in object CN=Domain Admins,CN=Users,DC=dc1,DC=evilgenius,DC=net - <GUID=7ae0e1a8b8ca2242a02497d59084268b>;<RMD_ADDTIME=130335192420000000>;<RMD_CHANGETIME=130335196040000000>;<RMD_FLAGS=1>;<RMD_INVOCID=c60633bfc7bbc740b63f9b2c6f6ffe2a>;<RMD_LOCAL_USN=6216>;<RMD_ORIGINATING_USN=6216>;<RMD_VERSION=1>;<SID...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 First, the more I read about olocks the more inclined I am to disable them globally. Here's the issue though, after experiencing data corruption in Act files at the hands of oplocks, we checked the Act support database and they recommended disabling oplocks not only on the server, but on the client machine as well. Is there any reason why

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We've recently moved from 2.2.2a on Suse using PDC authentication with local accounts created, to 2.2.8a on Debian with Winbind authentication. We are mapping shares on user's machines via a login script. So here's the problem several users are losing access to their home directory mappings. In other words, we are mapping their home

I read a few posts in the archives about this problem and that it was to be fixed in 3.0.23c. Currently I'm running 3.0.23d-2+b1 on a debian system and am getting the following: $ ssh -l testuser fileserver Password: Your password has expired Here's what auth.log shows: Jan 4 11:46:26 tmcsamba1 pam_winbind[14309]: user 'DOMAIN1+testuser' OK Jan 4 11:46:26 tmcsamba1

Sorry for the repost, but I've not gotten any response and the problem persists. Does anyone have any idea how to fix? =================================== I read a few posts in the archives about this problem and that it was to be fixed in 3.0.23c. Currently I'm running 3.0.23d-2+b1 on a debian system and am getting the following: $ ssh -l testuser fileserver Password: Your password

I have been having a problem with my Samba server for about a month now and need help. I am having users mysteriously losing access to drives during the day. The drive will un-map itself and any further attempt to access it through wither Windows Explorer or just typing the UNC in the "Run" window will result in a "Drive or path not accessible" error. On the samba side,

I'm having an issue with CIFS ACLs, and I'm not sure if this is the right place to post, but it's a good place to start. Until now, we've been all Samba-based for our file services. I developed a backup system that uses rsync to back the data up to hard drives on a remotew system. Thanks to the ACL patch in rsync, everything was preserved and all was good. Now, we're rolling

I have backups of user home directories that I've shared out via samba so that my non-linux level 1 guy can restore files using the drag-n-drop. Problem is, all directories are owned by their respective user and are set 700. In order for the admin users to access these directories, I've set admin user=@SuperAdmins for the share in smb.conf. The problem is, al the admin users have

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm having a problem getting a browse list from my Samba box. I'm running debian testing with the 3.0beta2-1 package. Winbind appears to be installed properly and functioning properly: root@dbs1:~# wbinfo -t checking the trust secret via RPC calls succeeded root@dbs1:~# wbinfo -a Administrator%xxxxx plaintext password authentication

Seriously, I realize the below post doesn't have all the necessary info to diagnose the problem, but I'm not even sure where to look for more info. Any help would be greatly appreciated. ===================================== I have been having a problem with my Samba server for about a month now and need help. I am having users mysteriously losing access to drives during the day.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 First the setup: Samba 2.2.3a on Debian testing, built with ACL support on XFS filesystem. NT4 PDC (Eventually we plan to implement Samba PDC, but that's a ways off.) Secondary offsite Samba server, same config as above, rsyncing data directories every 5-minutes over T1. Offsite Backup server grabbing data off the live Samba server nightly

I upgrade my Debian Samba packages from 3.0.14a-1 to 3.0.23c-1. I experienced 2 problems, one was that certain shares were locking users out who were listed in the "Valid users" parameter, but not all shares were doing this. I ran across a post that advised changing the parameter to "users" alone, omitting "valid" This fixed it, but I'm not sure why. WHen did

I posted this plea for help last week, but received no responses, so I figured I'd re-send. Since posting this message I upgraded to 3.0 stable using the package posted on the samba.org site, and the behavior remains the same. I should also mention, if I try smbclient -U guest and enter an empty password, I can successfully get a browse list fromt the server. Is there an increased