similar to: samba breaks during user authentication after it was updated

Hi, I've just updated (using yum under fedora 5) to the latest version of samba and am now encountering a major problem with samba. Whenever I attempt to access shares (don't have printers or other such non disk shares) the access fails (after prompting for password, and performing some level of authentication, it notes if no password is entered that Anonymous login successful).

Hi there, I use FC5. I discovered, for an exemple, if you have a user group with 3 members (Alan, Baker, Clive), before 3.0.23c this line at smb.conf worked fine: valid users = @user But with 3.0.23c update it doesn't work anymore. You have to replace the line like this: valid users = Alan, Baker, Clive I mean, replace the "@groupname" with the complete userlist of the

Hi there, I?m using FC5 and since I updated to Samba 3.0.23c-1.fc5 I?m not able to access some shares from the workstations. Lookin at the log, i found this error: [2006/09/29 19:34:27, 0] lib/fault.c:fault_report(41) =============================================================== [2006/09/29 19:34:27, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 3646

I've recently rebuilt a samba server and noticed this problem keeps coming up with groups. If I use a user in smb.conf valid users = me It works and I'm able to access the shared drive. There are no messages in the log file. However if I use group valid users = @admin I can't access the drive and I get a lot of errors in my messages file. Here is some of the errors.

Hello list ! Today i ran yum update on my corporate server thta runs fedoara core 5. All went well but i stumbled on the samba update... My network setup is as follows.. I have a small office network, no domain controller and such. The setup uses user authentication, and all shares are devided into departments, each defined group is a department, the groups cannot access/browse eachothers

Hi, I can't answer in a way it appears in the thread, sorry ... Examining the backtrace and these innermost frames: #0 smbd(log_stack_trace+0x1c) [0x5555557586cc] #1 smbd(smb_panic+0x43) [0x5555557587b3] #2 smbd [0x555555746b82] #3 /lib64/libpthread.so.0 [0x2aaaac259de0] #4 /lib64/libc.so.6(strlen+0x30) [0x2aaaad3c9510] #5 /lib64/libc.so.6(__strdup+0x16) [0x2aaaad3c9246]

Hey list, Having a strange issue on a new File server. This system is running the 64-bit version of Fedora 5 running kernel 2.6.20-1.2300.fc5 and version 3.0.24-1.fc5 of Samba. This system is functioning as a backup to a primary system that is configured the same way. Same OS, hardware, etc. After moving data over and setting up the users and groups, I moved over the smb.conf file as well. In

Hi All I have done as much as I can to try and figure out what is going wrong with my samba migration by googleing and reading mailing list archives and reading documentation etc. I have an existing SAMBA 3.0.5 domain running on suse linux 9.3. I am trying to migrate this setup to a new server which is running Fedora Core 6 smbd 3.0.24-7.fc6 I have migrated the data across to the new system

Hello everyone, I have the following data frame: > df V1 V2 V3 1 bench1_10 16675 16678 2 bench1_10 16585 16672 3 bench1_100 183924 185563 4 bench1_100 169310 184806 5 bench1_300 514430 516834 6 bench1_300 510743 514062 7 bench1_500 880146 877882 8 bench1_500 880146 857359 9 bench1_1k 880146 1589600 10 bench1_1k 880146 1709990 > I'd like to

Hi, I've got a big problem since my new samba servers are in 3.0.23c version, no problems before. The server is only a file server and domain member in a Win2K Active Directory domain (4 replicated DC, 1 domain, no forest). My problem: Anytime I try to connect a share through any kind of client (MacOS cifs client, smbclient, windows win2K pro, ...) the client can't mount the

Hi, I've got a big problem since my new samba servers are in 3.0.23c version, no problems before. The server is only a file server and domain member in a Win2K Active Directory domain (4 replicated DC, 1 domain, no forest). My problem: Anytime I try to connect a share through any kind of client (MacOS cifs client, smbclient, windows win2K pro, ...) the client can't mount the

http://bugs.freedesktop.org/show_bug.cgi?id=16675 Summary: Request for working fan speed adjustment on NV40 Product: xorg Version: git Platform: Other OS/Version: All Status: NEW Severity: enhancement Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

I would like t compile NIS+ support into SAMBA, but I am getthing an error. I am doing this: ./configure --with-nisplus and when I run make, I get these errors: Linking bin/smbd passdb/nispass.o: In function `make_sam_from_nisresult': passdb/nispass.o(.text+0x84f): undefined reference to `nis_sperrno' passdb/nispass.o: In function `nisp_get_nis_list':

I have a file server with two shares accessible to 2 different groups. After the last update ( from debian 2:3.2.5-4 to 2:3.3.2-1 ) i cannot any more access ONLY ONE of the two shares and I can't understand the reason! Can anyone hel me? I'm getting mad! Thanks Giorgio from smb.conf: [documenti_movi] path = /home/documenti_movi valid users = @staffmovi read

Hi, When I use "valid users" in smb.conf to limit access on my share, I have this message with smbclient : [global] workgroup = MYDOM domain master = no local master = no security = user passdb backend = ldapsam:ldap://x.x.x.x:389 ldap admin dn = cn=admin,dc=company,dc=com ldap suffix = dc=company,dc=com ldap user

Hi I'm using Samba 3.6.3 on ubuntu 12.04 as a domain member with AD on Win Server 2012. My hare is configured like this: valid users = @"EVSOFFICE.LOCAL+dangroup" When I try to connect to a share via IP from Win7 (part of the domain) it succeeds but when use host name \\node15 I can see shares but double-click on share shows AccessDenied. I'm trying to connect as

Hi, We have been running samba file server about 2 years without this problem. The problem appeared at the same time on our debian and centos servers. Not sure if it's related to any updates on our windows AD servers. Debian Squeeze sernet-samba-3.5.8-27 Centos 5.5 samba3-3.5.5-43.el5 Use Active Directory for user login authentication Use uid/gid from ldap The reason we still want winbind

For the last 3 weeks I've been working on getting RHEL4 (and 5, but that's a different story) to play well with Active Directory, OpenLDAP, Kerberos, PAM and NSS. It's been a long struggle but I now have a process to authenticate and authorize a RHEL4 client to a windows Active Directory server to that my AD Users can log into my Linux boxes (assuming their group permissions are set

Hi I have been working all week with samba 3.4.7 in Centos 5.5 PDC(3.4.7) with LDAP backend+Centos 5.5(3.4.7) BDC with LDAP slave. I already have 5 clients join. 1 Windows XP 1 Windows 7 UE 1 Centos 5.5 Desktop 1 Ubuntu 9.x 1 Centos 5.5 I can browse inside windows and see my clients, access some shares. I want to create private shares inside my PDC, I use: force group valid users write list

We've got nicely ADS integrated Samba-3.0.27a servers that are working fine with Win2000 through to standard Vista. However, we are starting to test RC1 of Vista SP1 and discovered that once applied, that workstation cannot connect to Samba server shares - unless the share is open - i.e. no "valid user" style settings. The moment one is defined, Vista fails to connect and pops up an