similar to: Vista SP1-rc1 appears to break against Samba-3.0.27a

Hello, Is the Vista compatibilty issue resolved? Is there any change in PAC structure sent by Vista? Would appreciate any information on this. Thanks Kris Hi Jeremy, > > I started having similar problems after installing Vista SP1 RTM. I > patched samba to dump that *auth_data blob, here it is: > > [2008/03/03 17:20:33, 10] libsmb/clikrb5.c:unwrap_pac(292) >

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 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

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

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 there I was using "username map" under 3.0.24 so that when I connected from DOM\jhaar under (ADS Win2K3) Windows, it was mapped to my local "jhaar" Unix account - with homedir "/home/jhaar", etc. However, when I upgraded to 3.0.25, I started getting NT_STATUS_LOGON_FAILURE errors - even when just trying to list the shares. This occurred using smbclient as well as

Hi, after upgrading samba from 4.1.17 to 4.1.19 on OpenSuSE 13.2, any shares offered by this machine can nolonger be accessed, when these shares contain an entry "force group" which specifies a local unix group and when there exists a unix user with the same name. Here's an excerpt from smb.conf: [FactWork] comment = FactWork-Downloadportal path =

Hi, I have two samba domains. On one member of DOMAIN1 I set up a share "intranet" with valid users = +"DOMAIN1+webmaster" +"DOMAIN2+TestGroup" Winbindd is running. When I try to access the share from a DOMAIN2 workstation permission is denied. When I look at the logfile, I see that the server tries to find the group of DOMAIN2 (TestGroup) in ldap of the local

Hi all, I seem to be having a problem identical to this bug: https://bugzilla.samba.org/show_bug.cgi?id=3940 in Samba 3.0.28, however the bug is supposed to be fixed by now. I have a Fedora 7 box joined as a member to Windows 2003 domain. All my Windows users have accounts on the Samba machine, with the same user name in Windows and in Unix. I have a share with valid users = +group, where

I am attempting to get a Debian box running Samba 3.0.23d (latest from debian testing) to work with our shiny new Windows 2003 server PDC. I can join the domain. windbinds various wbinfo commands return all the groups and users, as does getent. I can access everything from the PDC. Effectively, everything works _except_ specifying a group to 'valid users'. My smb.conf[0] is run of the

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.

We had to power down all servers today for electrical maintenance in the building and for some reason I began having access problems related to the valid users lists when power was restored. The dialog from the 'Samba-3.0.23 broke my network' thread seemed as if it might be related even though I had not performed any software upgrade so I tried adding the group mappings as discussed in

No one care then i closed it. Thanks. On Fri, Jun 5, 2020 at 5:18 PM Jeremy <jeremy55662004 at gmail.com> wrote: > Hi all, > > I am using samba 4.10.7 and it seems to have bug for using @group in valid > or invalid conf (?). And i can't find fixed patch in later release. I > describe this issue detail below: > > 1. Firstly, there is my samba conf below (Add

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 all, I am using samba 4.10.7 and it seems to have bug for using @group in valid or invalid conf (?). And i can't find fixed patch in later release. I describe this issue detail below: 1. Firstly, there is my samba conf below (Add @d_group in "invalid users"): (smb_share.conf) [f1] path = /home/f1 write list = "admin" "@Administrator_Group"

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

I've gone further down the food chain in diagnosing the problem: A net rpc join command works but wbinfo -u or wbinfo -g fails: [root@hcnas samba]# net rpc join -U Administrator Password: Joined domain MERCURY. [root@hcnas samba]# net rpc info -U Administrator Password: Domain Name: MERCURY Domain SID: S-1-5-21-356471451-824197641-1237804090 Sequence number: 20543 Num users: 625 Num domain

Hi: I have been using Dovecot for well over a year now and it has always worked with few problems. The mail setup is not simple... Postfix+MailScanner+ClamAV+Docvecot+MySql+postfix.admin... just to mention the major things. The system is CentOS 5.3 on VMware. The maildir is on an NFS share, index and control is local. About a month ago I thought I upgraded from 1.1.x to 1.2.x. by doing an

Gerry, all: HELP! On mandriva, I compiled samba from source and got it running, but I cannot connect from windows. (see my post from earlier "[Samba] Compiling and Configuring Samba for Mandrival") I think this relates to the group/SID changes discussed in the release notes. However, I'm not smart enough to figure it out. The tarball compiled and installed fine. It