similar to: Samba-3.0.0beta2 - cannot connect to share

Hi All, I'm having issues getting Samba/Winbind to work with a domain that is lowercase. I have read on some sites that it won't work, is this the case? system is Debian lenny, samba 3.2.5-4. Windows server is 2003 running AD in 2000 native mode. I've done everything I would normally do that my running samba/ad authing servers do, and wbinfo -u + wbinfo -g work fine, as do the

I can get authentication to work on linux 7.1 with samba 3.0alpha15 if I make valid users = @"INS+Domain Users", but if I try to set valid users to just a single user: valid users = INS+DavidSha, it fails to give me access. I see the following in log.winbindd. It looks like it is looking for a domain called DavidSha?!? My winbindd separator is +. Can somebody please respond to this.

I want to limit access to shares via windows groups but when I set a share to anything other than 'valid users = %S' or 'valid users =', I cannot access the share. The error message indicates that the share is not accessible and I may not have sufficient permissions. If I change just the valid users in smb.conf and restart smb, I get right in without prompting. I also found that I

Hi All, I am running Samba3.0 beta 3 installed from RPM's provided on the Samba.org FTP server. My platform is Red Hat 9. I am seeing a lot of errors such as: Aug 6 17:50:18 server3 winbindd[31138]: [2003/08/06 17:50:18, 0] nsswitch/winbindd_sid.c:winbindd_lookupname(103) Aug 6 17:50:18 server3 winbindd[31138]: could not find domain entry for domain AND smbd[27004]: [2003/08/06

The following configuration has been working OK with Samba 3.0.1 Mandrake 9.0 PDC. Redhat 7.3 BDC. (both with ldapsam passdb backend). Solaris 8 Memberserver. After upgrade to 3.0.3pre2, exactly the same configuration - with exactly the same smb.conf - produces an error, when you try to add a user or group in the security settings of a file or directory through MS Explorer. The message text is

Hello Samba folks, I have recently begun seeing some disturbing behavior from winbind. Winbind will fail to look up users and groups. Examples: The machine is configured to use winbind as a nss module. "getent passwd <username>" will yield no results. "wbinfo -n <username>" will yield "Could not lookup name <username>" "wbinfo -g"

Hi! I have the following problem: winbindd getgrnam/getpwnam/lookupname calls do not return for a long time (> 30 seconds) which is obviously quite annoying to the users. This usually happens at the "first" login, i.e. subsequent connections are not delayed until a (probably cache) timeout. I've failed to determine who is responsible for the caching yet. I'll provide

Hello, I've configured a small Linux box just for sharing some disks and route the traffic across two networks. This works fine, since Samba can join the domain of my NT4 PDC by Winbind. But I get those strange error messages on my logs, even if all seems to work correctly. This seems regarding to winbindd: Jan 27 11:03:25 wanda winbindd[1015]: [2003/01/27 11:03:25, 0]

Greetings all, I've been a long term user of the samba, ntlm, winbind, and active directory as the backend authentication mechanism for a squid proxy server. Recently, a challenge has presented itself and I am still seeking an answer. Currently, my users login to the PCs, VPN connection, etc with just a username. Ie: jgauthier I would like to have them login to these services using any

I'm stumped! From within CUPS, I'm able to successfully print test pages. From the Windows machine, I'm able to: * Browse the Samba server's printers via SMB * Add the Samba server's printers * Write to the Samba server's print$ share If I pause the printers via CUPS's interface, then Samba successfully relays this information when I try printing a test page from the

In my never-ending quest of removing clutter from the log files, I notice that we in /var/log/messages get a lot of: > Jul 25 13:08:30 filur00 winbindd[88603]: [2023/07/25 13:08:30.756462, 1] ../../source3/winbindd/winbindd_lookupname.c:122(winbindd_lookupname_recv) > Jul 25 13:08:30 filur00 winbindd[88603]: Could not convert SID S-0-0, error is NT_STATUS_NONE_MAPPED Seems to happen

Hello, recently I migrated 3 Netware 4.11 server to one Linux/Samba-box running on Suse Enterprise Server 7. Everything seemed fine, until performance problems were detected, especially when starting programs located on shares. Samba is a domain member using an NT4 PDC for authentication. The current samba version is 2.2.6 and the kernel is 2.4.19, but with 2.2.4 and 2.4.18 there was no

Hello to all. I?m using squid + samba to authenticate my users with active directory. The error occour only in the first time i authenticate an user. All works fine, but i have this is my logs: ==> /var/log/samba/log.winbindd <== [2008/05/21 00:32:36, 2] nsswitch/winbindd_util.c:add_trusted_domain(171) Added domain BUILTIN S-1-5-32 [2008/05/21 00:32:37, 2]

Hello, I have been using samba to authenticate my squid users to Active Directory. Because of the amount of users, I would like to set up my ACL's based on groups, rather than individual user accounts. I have successfully joined my samba box to our windows domain (2k). For some reason I had to enter the domain controller name instead of the domain name when doing so. I am now having issues

Hello, I've been able to get Samba up and running, it joins the ADS domain fine. It appears in the network browser on our Windows machines but when anyone attempts to access a restricted share it fails to authenticate them. I say restricted because if anyone accesses an open to everyone share it works. I'm trying to get the entire thing setup so that the Samba server is just a

I have two boxes on which I am trying to get idmap_ad (from xad_oss_plugins) to provide uid/gid mapping, and am getting the error: "Could not convert sid <sid of some_user> to uid" The story so far goes like this: Without the line "idmap backend = ad:ldap://<PDC's FQDN>/" in smb.conf, I can successfully do all of: #> wbinfo -S $(wbinfo -n some_user | awk

hi im using precompiled samba v. 3.0.4 packages from SuSE 9.1 DVDs all services (ldapsam, winbind, ... ) are compiled in user mapping on the PDC "SERVER" (SID-RID to UID) work fine the domain member server "FILESERV" gets the local accounts via nsswitch from the ldap backend of "SERVER" (tested with getent passwd) he also gets and checks the samba users and

Hello experts, I?ll try and keep this brief but detailed (if that?s possible.). I?m sure I don?t understand the technologies sufficiently but I believe I?m seeing counter-intuitive behavior with my Samba 3 setup. What I want is nice, tight Win 2K3 security. What I?ve got is ADS integration, including domain user authentication using winbind, but I can?t get the security level right. Problem

OS: Mandrake 10.0 Official PowerPack Samba version: 3.0.2a OpenLDAP: 2.1.25 smb.conf: # Global parameters [global] workgroup = WSLYHBB netbios aliases = wslyhbb server string = Wes' Computer map to guest = Bad User smb passwd file = passdb backend = ldapsam:ldap://wslyhbb.personal-pc.com passwd program = /etc/passwd unix password sync = Yes client plaintext auth = No log file =

Hi there, I have another problem on WinXP SP2 with samba.3.0.20a. Somehow, in a random situation, once user logged onto the workstations, they were prompted with the winlogon.exe Fatal error + blue screen to death then self-reboot. When I checked out the log from windows, it said there's problem on msgina.dll from WinXP SP2. However, another user can successfully logon to the same workstation