similar to: samba-tng-alpha-2.1.tar.gz

Displaying 20 results from an estimated 500 matches similar to: "samba-tng-alpha-2.1.tar.gz"

2000 Apr 10
0
samba-tng-alpha-2.2.tar.gz
update: - fixed smbd for win95-style profile-locating (it now works, thank you to everyone who sent in log files to get this fixed) - various modes tested and confirmed as working: * ROLE_STANDALONE security = user encrypt passwords = yes domain master = no domain logons = no * ROLE_DOMAIN_PDC security = user encrypt passwords = yes domain master = yes
2000 Mar 27
2
Problem starting SMB services
This is the error I receive when attempting to start the service. This is from /var/log/messages. Mar 27 11:41:17 portero smb: smbd startup succeeded Mar 27 11:41:17 portero smb: nmbd startup failed Mar 27 11:41:18 portero srvsvcd: execvp: No such file or directory Mar 27 11:41:18 portero smb: srvsvcd startup failed Mar 27 11:41:18 portero wkssvcd: execvp: No such file or directory Mar 27
2000 Jan 26
0
coding volunteers needed for msrpc server-side API conversion
ok, people, i _really_ need help with this. i estimate that if i work on this full-time it's going to take about... two weeks. i have one volunteer for the samr functions. it's been two days, already, and i'm only half-way through samr. that means, nothing else gets done, and samba-tng current cvs is broken because the _samr_lookup_rids() function goes into an infinite loop on that
2000 Mar 31
0
TNG-1.0.5 Problems
Hi... I have exactly the same problem with lsarpcd giving the error "ERROR: setgroups call failed!". Anyone know of a fix?? MWP > Hello > > I was just installing the new TNG 1.0.5 and after i installed and cleaned the > logs i started the dameons and was unable to access the shares on win98. The > computer showed up in Network Neighborhood but i would get a \\comp03
2003 Feb 26
0
[help] Can't Join Samba 2.2.3a to TNG+LDAP
I need to join my Samba 2.2.3a to a TNG Domain (which stores users and machines account into OpenLDAP) using it as a password server. Provided that TNG is working fine in authenticating users on W2K machines, once they are logged in they should (in my intentions) see Samba 2.2.3a shares. In order to do this I provided the following configuration for Samba: workstation = <tng_domain>
2000 Mar 08
0
samba-tng-alpha-0.11.tar.gz
ftp://samba.org/pub/samba/alpha or mirror sites. this version has security = domain tested and, shock-horror, working. it is possible to do SMB connections with WORKSTATIONNAME\username (wow) and actually, this is _necessary_, because otherwise, how are you going to join it to a domain? :-) :-) as root: samedit -S . -U root% -l log [] createuser root -p rootpassword [] exit samedit -S thepdc
2000 Mar 11
0
samba-tng-alpha-0.14.tar.gz
ftp://samba.org/pub/samba/alpha and mirror sites. finally resolved some of the niggling issues that have kept tng from working: in particular, thanks to karl denninger for helping track down "invalid users = root" in the [global] section which stops root from being able to access anything, including being able to add user accounts! tng is now back where it was about 6 weeks ago: -
2000 Mar 21
0
samba-tng-alpha-1.2.tar.gz
ftp://samba.org/pub/samba/alpha and mirror sites. when using domain user map, when logging in and then accessing the samba server, i re-enabled map_nt_and_unix_username() to allow the nt username to be remapped to the unix username / share. i think i also now have the GETDC request with enough correct rules in it to allow all the various spurious combinations to be supported. NT 5 wks now can
2000 Mar 23
0
samba-tng-alpha-1.3.tar.gz
ftp://samba.org/pub/samba/alpha and mirrors. due to some confusion about how to use samedit's createuser command, i put a warning / security message in whenever createuser hostname$ is used. it basically says, now you can join the workstation to the domain because you have just set the trust account to the insecure, well-known initial value, and you had best join the workstation to the
2000 Mar 29
1
samba-tng-alpha-1.4.tar.gz
ftp://samba.org/pub/samba/alpha and mirror sites rpcclient and samedit etc. on sun ultras were failing because getopt cannot be reused. evidence of this is by doing a samedit "createuser username -p password" and the reported password on-screen is total garbage. this was fixed by using the GNU getopt and getopt_long functions (hooray!) in the same way that rsync does. i have access
2000 Mar 31
0
samba-tng-alpha-1.6.tar.gz
ftp://samba.org/pub/samba/alpha and mirror sites mainly a maintenance update: all bzeros replaced, as was done in cvs main / 2.0. readline detection added. if someone wants to add an autoconf test to detect -lcurses being needed by solaris readline, please create and send one. usrmgr user-account changing is now accepted (on systems compiled with the default, --with-sam-pwdb=passdb, this means
2000 Apr 03
0
samba-tng-alpha-1.7.tar.gz
what you've all been waiting for: a merge of smbd from cvs main to SAMBA_TNG. please help test this one lots, i may have missed something from the code i pulled over from cvs main (70,000 lines of code pretty much copy and diff style!) i spent some time last night getting the security file/dir tab working, and lo and behold, you can view and change unix file perms (i am very impressed,
2000 Apr 11
0
samba-tng-alpha-2.3.tar.bz2
yes, there's a .gz, too. there's also always patch files (diff.gz) for those people with really slow links [in russia, hi there, thanks for wanting to keep up with this stuff!] this release may be a bit dodgy, it contains three separate sets of changes: - andrew's simplified the file-opening. however, it doesn't deal with the shared NFS / SMB case, so jeremy is investigating
2000 Apr 24
0
samba-tng-alpha.2.5.tar.bz2
ftp://samba.org/pub/samba/alpha and mirrors went to minor release numbers on 2.4 because of instability. also, if you are running into problems at high debug log levels, try reducing them to more reasonable levels (between 5 and 10 or even just 1) and see if it works. i ran into timeouts because of too much debug output! andrew and i have been using insure (a proprietary, *excellent*
1999 Dec 15
0
Problems with CVS / 2.1.0 prealpha on Redhat 6.1 - still no joy with CVS
Dear All Firstly my thanks to Luke Kenneth Casson Leighton <lkcl@samba.org> for his answer - I have now 'use co -r SAMBA_TNG'ed and have a fresh CVS snapshot. The ./configure works again - yipee! But the 'make all' fails with the warnings pated below. I have tried the other CVS snapshots from http://sernet.pair.com/ and they are in a similar broken state (although broken
2000 Mar 19
2
samba-tng-alpha-1.1.tar.gz
ftp://samba.org/pub/samba/alpha and mirror sites 1) i fixed a problem with nmbd's GETDC response, it is responding better but still not perfectly (and 2.0.x and cvs main need to be fixed, as well) as there exists no explanation for the correct response to locate a Domain Controller using GETDC. the upshot of fixing this is that joining an nt workstation to a TNG domain is now _extremely_
2000 Jan 30
0
"attack" (manage) NT domain using the linux tools?
rpcclient sound cool. I am running 2.0.6 Samba. 'rpcclient' exists with it but a call to 'man rpcclient' gets no results. Could it be that the man pages are in a later release? Dan dmalcolm@hiwaay.net ----- Original Message ----- From: "Luke Kenneth Casson Leighton" <lkcl@samba.org> To: "Multiple recipients of list SAMBA-NTDOM"
2000 Feb 03
0
SYSKEY2. Request For Comments
recently, netect / bindview posted a review of the syskey system and how the RC4 cypher stream was reset each time. standard RC4 attack analysis shows that XORing two obfuscated passwords together results in the XOR cypher stream dropping out, and you have the two XORed password. further attack analysis can decrypt the passwords. i am looking to implement an equivalent mechanism to SYSKEY,
2005 Jan 07
2
Differences between Samba-related PAM modules
Several different PAM modules relating to Samba exist. The ones I could find were as follows: pam_smb http://www.csn.ul.ie/~airlied/pam_smb/ Authenticates against an NT domain controller, without joining the domain. (Doesn't work with Active Directory.) pam_ntdom http://www.cb1.com/~lkcl/pam-ntdom/ Based on the above, authenticates against an NT domain. Requires the client to be added to
2000 Feb 17
0
Using rpcclient or samedit to randomise trust account passwords
when an nt 4.0 workstation or backup domain controller is joined to a domain, the trust account password is set to a well-known initial value. if you are concerned about internal network security, this is not really an acceptable risk: any captured network traffic can be decoded simply from knowing the name of the workstation, which is contained in the network traffic itself. the initial value