similar to: samba 3.0, winbind is not updating userlist - only on restart

Hello List, We are having a NAS here with 4 TB (sic!) disc space and a samba server as a file server (or better: as one of the file servers). Now the vendor tells us: with samba you can't share more than 2 TB of that. This is not enough. Is that a restriction of Samba, Linux or of the vendor's system? I never encountered this restriction... Please help! -- Mit freundlichen Gr??en

Hello List, I have successfully integrated samba 3 to ADS Domain, and now i want to allow domain-users to access services on my linux box. For testing i chose /etc/pam.d/login and tried to allow ADS Users access to the console. But i always get the following errors: Mar 12 12:45:59 cuba90 pam_winbind[9011]: user 'r-ermer+mfeilner' granted acces Mar 12 12:45:59 cuba90 login[9011]: User

Hello List, has anybody got pam_winbind get to work under SuSE 9.0? I try to set up a pam.d file to enable users auth'd against winbind to access my mail server. I am testing with console login or ssd files at the moment. I found some docs at samba.org (esp the winbind section), but that didn#t work. I used to manage with older versions, but i can't figure out what went wrong ... al I

Hello List, I have successfully integrated samba to an Active Directory Domain, and it is authenticating against the ADS, but only while the Kerberos ticket is valid. After that period it seems to take only the user/group list from its (winbind) cache. By now i can get a kerberos ticket with "kinit Administrator" or any other username that has administrative rights on ADS and all is

Hello List, I am (unsuccessfully) trying to automatically get a valid kerberos ticket for my linux box. I have - in a test environment: - a windows 2000 server with Active directory and DNS properly set up. - a suse linux 9.0 router with samba3.0.2.rc.1 and heimdal 0.6.-67. - I am able to join the domain and get a valid ticket through kinit, if I enter the Administrator's password or the

Hello List, I have a strange problem: I have successfully added my debian system to the local active directory domain. Winbind works and gives me Users, Groups, and relations when I call wbinfo. However, Users cannot connect to a share I prepared. It makes no difference if there is no "valid user = " entry, or if I put an correct entry with my test user. All I get in log.winbindd is:

Hello, I have a samba share (with security=share) and I can access it from every W2K system after entering the username/password. However, when I try to access the share from Windows XP, XP always tries to connect with the guest account. Can anyone point me to the reason for this behaviour? Thank you! -- Mit freundlichen Gr??en Markus Feilner -------------------------- Feilner IT Linux &

Hi list, I am an editor at the German Linux Magazine and I am searching for an author or input on Dovecot, its advantages and especially the recent features. I had organized some authors, but unfortunately they don't have time right now. :-) Nevertheless I heard many positive comments on Dovecot. I can write or help writing the article, but I would love to have some input from an

FC4 Samba 3 joining Windows 2003 Domain. I have to manually join the Domain after rebooting. If I set samba to start when booting it doesn't join the domain. I have to smb stop, net join ..., smb start from the command line and then it will join the domain and work fine. Is there something in the smb.conf that I can set to join the domain when smb starts? Thanks, Tommy

I'm having a bizarre problem doing authentication via winbind against a Windows 2003 server. Aside from changing the hostname information, etc. as appropriate for krb5.conf and smb.conf, the configuration I'm using is one that I copied from another server that is successfully authenticating against ads. The two systems I'm having trouble with are running Suse Linux Enterprise

Hi guys; I''m sure you are all bored of hearing the same story over and over... but here it comes again. :) Yep, tomorrow I''m getting another ADSL line installed and I wanted my linux router to handle both providers (new and old). I have my linux router (fedora core 2) setup to do NAT for my current line, but I know I''ll need to change my configuration to

> -----Original Message----- > From: G?mes G?za [mailto:geza@kzsdabas.sulinet.hu] > > I've configured for testing pruposes an other PDC with tdbsam backend, > and found, that with this backend win9x clients could get > user and group > list, while with ldapsam I had no success in it. Quite strange in my > opinion:-( Same problem here too. In 9x the userlist is

There appears to be a problem with the handling of symlinks within source directories by the --relative (-R) option. I am using rsync 2.5.5 on an SGI Origin 200 running IRIX 6.5.11f. Example: copying the contents of /usr/local/etc/inhouse/db/ from wolf to fox where /usr/local is a directory on wolf, but /usr/local is a link to /usr2/local on fox. Here's the dry-run output (some

Hi, for those who are using ldap for managing Samba, here's a quick script I wrote to make it simple to list users or machines on the commandline. I use it to delete old machine entries that are not in use anymore. For usage, read the perldoc in the script. Place the script in the same directory as you have your other smbldap-tools scripts. The script is based on smbldap-usershow. Kind

Hello, I run Samba 3.0.20a with Windows XP Professional SP2 client. Sometimes, the logon is a bit slot, i.e. it takes some seconds until the "Loading profile..." dialog box comes up. The same effect happens when I start a program with the "Run as" command in the context menu. I enter my domain user and select run, and it takes about 5 seconds until the program is invoked. I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear List, Few days ago I've posted, that my Win9x boxes are unable to get the list of domain users and groups from samba-3.0.0 server (for details see bug 596). Unfortunately the same is true for samba-3.0.1pre1. Please people also having win9x boxes and Samba3 PDC confirm that it is a bug, or a configuration error. Thanks for any suggestion.

Hi all I have a samba 3.0.4 pdc compiled with acl support built in, and the following options configured at compile time: ./configure --with-acl-support --with-smbclient --with-sm bmount --with-quota --with-ads --with-tdbsam I am just trying to provide acl support to my users, and I know that acls are working properly on the linux machine (setfacl and getfacl work superbly!). Samba acl

I cannot boot domU: # xm create inhouse Using config file "inhouse". Started domain inhouse # xm list Name ID Mem(MiB) CPU VCPUs State Time(s) Domain-0 0 123 0 1 r----- 27.4 inhouse 8 2048 0 1 ------ 11.4 # xm console inhouse Linux version 2.6.12.6-xenU ( root@xen1) (gcc version 4.0.2 20050901 (prerelease)

>Thereby sorry for being impolite :-(, but at present I'm running samba >3.0.1pre1 with ldapsam in the production servers, >and Win9x clients couldn't get list of users and groups from Samba DCs (Bug596). I have 3 >choices: >- -- Switch back to 2.2.7 (not very nice:-(, I would need group support for policy) >- -- Switch to tdbsam with fam/rsync/ssh-ing password and group

When windows is set to USER mode, samba stops working, even when defined in DOMAIN SERVER mode. Anyone know why and how to fix it? If I am sharing is SHARE mode, then I can acces fine. Also, when in Share mode, I cann't get Windows to read a user list for shares from the Samba server. Anyone got any ideas? smb.conf: # This is the main Samba configuration file. You should read the #