similar to: Samba 3.0.8 - Unable to login/logon from Windows 2003 or CIFS

I'm running 3.4.6 (was running 3.0.28a but upgraded in hopes to fix this issue). Clients running Windows 7 that are NOT joined to the AD domain (samba authenticates against it via "security = server") cannot authenticate to access the server. Clients running Windows 7 that are on the domain as well as Windows XP, Windows 2003 on and off the domain work as expected. Any help would

Folks: I've got several systems attached to a 2003 domain where we use kerberos to authenticate. When I upgraded a system to the latest greatest samba things stopped working. Just to find where it happened in the different versions of samba I downloaded, built, & ran 3.0.23d to 3.0.25c using the same smb.conf file. Turns out the 2.0.23d and 3.0.24 works but from 3.0.25 on it fails.

Installed Samba 3.0.10 via 'pkgadd' on Solaris 2.6 - previously running Samba 2.2.8. It starts up and SWAT confirms that it is running and I am using the same smb.conf but I am unable to connect to a share via PC. Message "\\s080 is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access

Hi all, I had linux samba 3.0.10 running as PDC of my domain which does only authentication for other linux samba boxes which are providing access to shares. After upgrade of PDC to Debian Lenny + samba 3.2.5 I've lost guess access to the shares which are run by samba 3.0.x boxes, while it works on samba 3.2.5 samba box. the scheme is like following :

Hi, I am new to samba. I have configured password server to authenticate centos users. But i got the following errors and not authenticating. [2007/10/29 02:48:24, 1] auth/auth_server.c:check_smbserver_security(363) password server WINDOWS rejected the password following is my smb.conf [global] workgroup = WINDOWSAD server string = Samba Server security = SERVER password

We run Samba, but wish to authenticate against Windows DC. We do this using the "security = server" mode. We don't have the option of being part of the Windows setup directly. Although authentication is done against Windows DC (so users are not prompted for passwords) users do need a Unix account to use the service. We have users in multiple Windows domains, and the DCs we

Installed Samba 3.0.10 via 'pkgadd' on Solaris 2.6 workstation s080 (137.223.31.80) - previously running Samba 2.2.8 which has worked for a long time. Samba 3.0.10 smb.conf file - changed to security =DOMAIN from SERVER at 2.2.8 version password server = 137.223.33.45, 137.223.33.72 - these are DCs # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date:

================== platform ===================== Linux version: RHEL-3 resp. Scientific Linux 305 Samba vesrion: 3.0.9-1.3E.3 Samba operating mode: security = SERVER ================== problem ===================== 'net use n: \\smbs1\public' on Windows XP, always asks for a password. 'smbmount //smbs1/public /mnt/public -o password=' does not. This all used to work fine

I've been running Samba 2.2.2 for a while as a domain controller on my mostly Windows network. It's been working great up to this point. Anyway, I just put together a new Linux server and installed 2.2.2 on it as well. I copied the conf file and pretty much mirrored everything on the existing server, changed the paths and the "workgroup" field in the conf file to match the new

I have a Samba server set up to share files within a small network (with 2 clients) and I use OpenLDAP to store user accounts. I have pretty much got everything working (smbclient prints the correct information and I can browse and log into Samba via Nautilus) except I can't get the Vista client to connect to Samba, as it won't even prompt for a username and password it simply pops up

System Summary: centos 6.2 samba 3.5 smbldap-tools 0.9.6 openldap 2.4.23 Hello, I am installing smb 3.5 on a CentOS 6.2 host using smbldap-tools. I've previously installed a similar configuration on RHEL4 using smb 3.0 but CentOS now uses nss-pam-ldapd and nslcd instead of nss_ldap, so the configurations cannot be moved straight across. Currently, when I attempt to connect to an smb share

Hello, I have recently installed Samba 3.0.2 on Solaris 8. All is OK except for Windows NT. I can't open the user's shares on the Samba box. I get : D:\ n'est pas accessible Erreur reseau inattendue (Unexpected network error) I have already set encrypt passwords = No unicode = No in smb.conf and the corresponding register key on NT I have a level 3

Hi All, I installed samba 3.0.22 and join it to Win2003 AD domain. Users from my domain can access the samba shares successfully. My problem is that users from trusted domains can not access to my samba shares Wbinfo -m - show all the trusted domains Wbinfo -u - show all the users include the trusted domains users. Any Idea? My smb.conf global parameters: # Global parameters

Specifics samba-3.0.0beta1-1.i386.rpm on RedHat 9 and smbpasswd authentication, the machine is the PDC and security is set for user. The machine account was setup on the fly and it appears in passwd, shadow, and smbpasswd files as it should. However it seemed to take a very long time to join the domain, about 1-1/2 minutes. I can browse the Samba PDC machine and access the shares, etc. After

Hi, I am running Samba 3.6.19 and making my way through all the Active Directory documentation. I have joined various Linux boxes to a Windows Server 2008 R2 Active Directory domain. Windows 7 users who log on with their domain accounts can mount the correct shares exported by the Linux boxes without having to supply any additional credentials. All working perfectly! However, I have a

hi all i am new to samba and struggling with trusted domains authentication from many days .i have a win2k3 domain(corp.raju.ad )and win2k8 domain ( testraju.ad) . i have joined samba server as a member to win2k8 domain (testraju.ad) using net ads join commands / i m able to access samba shares using testraju.ad user ID's successfully , while authenticating with corp.raju.ad users i m

Hi, I'm using 3.0.21b and I cannot get the guest account to work. some of smb.conf: ------------------------------ security = user hosts allow = 192.168.2. 127. guest account = visiteur log level = 2 log file = /var/log/samba/samba.%m max log size = 1024 socket options = TCP_NODELAY [publique] path = /vol2/samba/publique browseable = yes guest ok = yes

Hi all, We're having some issues getting Samba to work in the way we'd like it to in our domain infrastructure. We have a real Windows domain WIN (WIN.DOC.IC.AC.UK) which is run on Windows 2003 domain controllers. We also have an MIT Kerberos realm DOC.IC.AC.UK. A realm trust exists such that WIN.DOC.IC.AC.UK trusts DOC.IC.AC.UK for authentication, and users have appropriate Kerberos

I have a problem with Samba: I want to make trust between two Samba domains. I have setup the trust on the DOMAINB server then on the Samba DOMAINA server "net rpc trustdom establish DOMAINB" I then get the following: Password: [entered password] Could not connect to server SERVERB [this is the PDC for the DOMAINB domain] Trust to domain DOMAINB established When I then try

Hi! I'm experiencing problems with access to one of shares on server with Samba working as PDC for windows clients, after I upgraded Samba from 3.0.22 to 3.0.23 (this problem also present in 3.0.23a). There are config section for this share: ---------------------------------------------------------------- [domain] comment = Domain users exchange share path =