similar to: need some assistance - Samba 3.09 on FreeBSD 4.5

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

Help, wbinfo -t fails with the error in subject, and getting sids of groups that aren't BUILTIN fail. Everything else seems to work. Note: I am not converting my kerberos tickets to krb4, is this necessary? (It used to work without it..but now it seems not to work.) I get no errors from kinit. all other wbinfo requests succeed with the exception of looking up the SIDS of groups that

Problem: wbinfo -t fails. As long as it fails, I am unable to map sids to Group Names. I need this functionality for my application. I can use just about everyother function of wbinfo at least partially... Distro: Debian woody. Packages: ii samba 3.0.11-0woody1 a LanManager-like file and printer server fo ii samba-common 3.0.11-0woody1 Samba common files used by both the server a

Hi I cannot make winbind work correctly. My problem is that my AD users & groupes are not authenticated on my samba box. I made it work correctly on my samba 2.2x, an dfrom my understanding, each time a AD user is connected, a Unix account is created, nad winbind synhronize both accounts. It looks like the user script "/usr/sbin/useradd -s /bin/false %u" doesn't work, and my

I recently upgraded my PDC's and BDC's to 3.0.14a but my member servers are still running 3.0.10. Today users complained that the couldn't logon to the member server. When I try to run a wbinfo -u I get: Error looking up domain users Here's the log.windbindd: 2005/05/31 11:06:26, 4] param/loadparm.c:lp_load(3933) pm_process() returned Yes [2005/05/31 11:06:26, 3]

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

I'm using Samba 3.0.21b on SuSE 9.3 Pro (x86) with the binary RPMs from samba.org/suse.com (3.0.21b-1.1.2-SUSE-SL9.3) on a Domain Member Server in ADS mode with winbind against W2K3 SP1 AD servers and idmap uids/gids stored in a central OpenLDAP directory. Unfortunately, winbind gives me a hard time and reproducibly dies with a PANIC on a "wbinfo -g", although I think I've

If you require and more information let me know and thanks in advance .. I'm working with dansguardian and squid with ntlm_auth. I join squid to the domain and it works for 7 days. After 7 days to the minute from the time I joined the server to the domain winbind decides it has lost its trust. And then squid cant utilize ntlm_auth as it requires winbind to function properly. I'm using

Hi list, I've just upgrade my current samba config to 3.0.23c on Suse 9.1. x86 I join my active directory 2003 domain and 'getent passwd' works fine but each time I run 'getent group' winbind crash I deleted the winbindd_cache.tdb but nothing better wbinfo -u / wbinfo -g works wbinfo -t tells "checking the trust secret via RPC calls succeeded" Can someone help me I

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

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

CentOS 3.5 samba3-3.0.20a-24 Security ADS I can't get windows group permissions on shares to work except for 'domain users'. The windows group I am trying to use is Unix.Samba. This group does not exist on the linux box. It resolves correctly using getent group and when I chgrp files to unix.samba, ls shows the group ownership as Unix.Samba. getent group shows this group with the

Hi I have a problem with an interdomain trust where on the PDC for DomainA, everything works perfectly. getent returns local and DomainB usernames. On the PDC for DomainB, it's DomainB works fine, but getent only returns local usernames and groups, it doesn't return the usernames or groups for DomainA. wbinfo -u and wbinfo -g work fine and return all DomainA's usernames and groups.

I've been checking the authentication with "wbinfo -a <username>%<password>", which is failing with the following error: plaintext password authentication failed error code was NT_STATUS_NO_SUCH_USER (0xc0000064) error messsage was: No such user Could not authenticate user <username>%<password> with plaintext password challenge/response password

I'm trying to setup Samba in ADS security mode so I can run winbind for NSS and Kerberos for user authentication, chiefly for shell accounts for developers. These hosts will not provide any file or printer services, at least in the near-term. My hosts are CentOS 3 (a free RHEL3 clone) and my ADS servers are Windows 2000 (not 2003), in hybid mode. I am using stock RPMs for both Kerberos and

Hello, I have a very strange trouble with samba 3.0.33 when I integrate a Linux server in my Windows 2003 AD. I do : - kinit administartor, it's work. - klist, it's work too. - net join ads -U administrator, it's work. I hev the message that my computer has join the domain and I see the Linux in my Domain. - wbinfo -t give me "checking the trust secret via RPC calls

Was: RE: [Samba] samba 3.0 and freebsd 5.1 Hi Aaron, I deinstalled the 3.0.1 port and got the source tarball for 3.0.2a and installed from there. I also swapped out 3.0.1 for 3.0.2 on the domain controller when I discovered the second problem. I can now use smbclient to log into a file share on the member server, giving an " smb: \> " prompt but doing ls gives an error of:

I have read through previous posts but still cant connect to samba shares - any help much appreciated. Running Samba 3.0.10-1 on fedora Core 2. Dont know anything about AD as it's looked after by the big boys and they wont share their secrets with the linux team. I do know the server I need to authenticate with is acting as some sort of time server so I assume that is not an issue.

I'm trying to learn about the interactions between SAMBA and win2k DCs. The eventual goal is to have a Win2k server with ADS working with a freeBSD SAMBA server. I've used the setup from http://oslabs.mikro-net.com/fbsd_samba.html as the basis for what I've done so far. Winbind seems to work and I can show users and groups using wbinfo although I see some things in the logs that I

I posted my original post to FreeBSD-questions@freebsd.org and since then have had a running dialog with another poster. It now seems I am having trouble with the NSSWITCH function. I am now reporting back to the Samba list in hopes someone can help me out at this point. Can anyone help me out here? ~Doug -----Original Message----- Sent: Friday, September 16, 2005 12:48 PM To: 'Dan