similar to: samba error message - "broken (and insecure) behavior"

I am not a member of the samba listserv, but I wanted to contribute the following code to the samba effort. The following is clipped from some experimental changes I have made to my own copy of the samba source. I have not included all of the changes because I don't have the time to. But someone should be able to properly do the integration without too much effort. Summary, these

We are seeing erratic behaviour from Samba for connecting Unix drives to an NT terminal Server. Samba version 2.0.6 Solaris 2.6 NT Server 4.0 Terminal Server Edition with service pack 4 running WinCenter NIS Logon Utility. The NT server is not part of a domain and uses the WinCenter Logon Utility to authenticate username and passwords from my Unix NIS server. Samba is set up for server level

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 :

I''ve been going through Pat''s example story and noticed that there was no checking for a bad login. I assume this is because that would have made the article bigger and more complicated than it needed to be. So the question that comes of of this is: How do folks normally handle the negative case? My plan was to just use another scenario, but as a new person to BDD/TDD,

Hi all, sorry if this has been asked before, but as far as I could see there's no similar entry in the archive. I'm using version 2.2.7a on a HP machine running HP-UX 11.11. The binaries have been created for PA-RISC 2.0 supporting 64Bit mode. The SAMBA has been configured to use securty = server. Password servers has been 'defined'. For a certain user (Service account used to

Hi y'all, I have a little problem with Samba which I hope you can help me with. We are running Samba 2.0.4 on a Sun Enterprise 4500 with Solaris 7. Clients are mostly Win 9x and a few NT workstations (and one NT Terminal Server). I have security = server (password server is the NT Terminal Server). What happens is occasionally Samba will not let a certain user connect, saying the password

Built from tar. Same result from git pull as of 01NOV install sudo samba-tool domain provision --realm=hen.us.mentats.us --domain=NEWDOM --dns-backend=BIND9_DLZ --adminpass=badpass --server-role='domain controller' "libkdc-policy.so: cannot open shared object file: No such file or directory" How do I find/build this module?

I would like it to provision a domain or have had no response on irc or the samba maing list as to why it fails. Having the wiki howto up to date would not be a bad idea either. <br> The wiki and most other online resources indicate the one should use the "provision" command. This command is no longer available in the S4RC you must use samba-tool to accomplish the task. sudo

================================================================ "You can''t have everything. Where would you put it? Steven Wright ================================================================ Release Announcements ===================== This is a maintenance release of the Samba 3.2 series. Major enhancements in 3.2.11 include: o Fix domain logins for WinXP

================================================================ "You can''t have everything. Where would you put it? Steven Wright ================================================================ Release Announcements ===================== This is a maintenance release of the Samba 3.2 series. Major enhancements in 3.2.11 include: o Fix domain logins for WinXP

I'm attempting to get a Linux box to authenticate users from NT. I think it's possible by writing a PAM module (not hard) and using part of Samba's source to verify the password on the NT server. I'm getting pretty bogged down trying to work out how to do this - it seems like it should be simple - just take the password and username and ask the NT server if it's correct. If

================================================================= "A banker is a fellow who lends you his umbrella when the sun is shining and wants it back the minute it begins to rain." Mark Twain ================================================================= Release Announcements ===================== This is the latest bugfix release of the Samba 3.3 series.

================================================================= "A banker is a fellow who lends you his umbrella when the sun is shining and wants it back the minute it begins to rain." Mark Twain ================================================================= Release Announcements ===================== This is the latest bugfix release of the Samba 3.3 series.

I have a Windows 2K SP2 terminal server and a Samba 2.2.7a server. The Samba server uses security=server with the 2K terminal server as the password server. Users log in to the terminal server and attempt to access (always the same) share on the Samba box. When there are no sessions open to the Samba server the connection from the terminal server always works; subsequent connections (with

Hi Toni, This error is the result of a test that samba does in the module "server_validate", (in password.c) to check the password server for a bug where NT 4 (some versions) would not correctly set the guest bit. There is currently no smb.conf parameter to allow you to control this behavior, so to change it , you would need to actually hack the password.c module to disable it. Not

Hi all, using samba 2.2.5; security=server connecting as user1 (user logged in on PC) works (12:28:55), disconnecting and connecting as another user2 (not the user logged in on PC) works too (12:30:22), but disconnecting and connecting again as user1 (user logged in on PC) fails (12:34:29) as well as user2 (12:38:19). It seems it works only once and never again after one time logged in as user2 ?

We need to give a user in another domain access to our printer: our domain: OURDOM (samba) other domain: OTHERDOM (AD?) user's workstation: \\OTHERDOM\WKSTN, in other domain printer: in our domain user: JOEBLOW - an account in each domain with the same login/password We're getting this error in wkstn.log: [2003/05/28 20:44:20, 1] smbd/password.c:server_validate(1101) password

https://bugzilla.samba.org/show_bug.cgi?id=10551 Summary: Daemon infinite loop when no matched user in secrets Product: rsync Version: 3.1.1 Platform: x64 OS/Version: Linux Status: NEW Severity: major Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: ryan at

I'm preparing to roll out a bunch of win XP clients and and am running down all the quirks that come up in the application log on my test box. 1) AutoEnrollement fails - samba is not an active directory so this makes sense it must be disabled by editing the group policy with gpedit.msc computer configuration->windows settings -> security settings -> public key policies ->

Here is my setup. samba+winbind on OpenSuse 11.3 (samba 3.5.4). Using winbind to auth to another samba+ldap server. Authentication works until first failed login: host:~ # wbinfo -a prod\\user%goodpass plaintext password authentication succeeded challenge/response password authentication succeeded host:~ # wbinfo -a prod\\user%badpass plaintext password authentication failed Could not