The work Olaf did would probably be of interest to anyone
trying to port
Samba code to non-Posix platforms, particularly small
platforms such as
appliance systems.
VMS must have as mentioned before addresses the same issues.
I.e fork() etc..
The linked libsmb with way smaler exe files
Hi,
I'm using samba-2.2.7-2 in RH 8.0. I'm receiving, lot off
e-mails(Logwatch), with the error message:
[2003/01/28 08:23:15, 0]
nmbd/nmbd_browsesync.c:get_domain_master_name_node_status_fail(509)
: 1 Time(s)
I configured smb.conf to Wins Server, with global options:
security = share
os
... The only thing that doesn't work is
passwd itself:
venezuela:/home/tdm # passwd guest
Changing password for guest.
Enter login(LDAP) password:
New password:
Bad password: a palindrome
Re-enter new password:
LDAP password information update failed: Unknown
error
Password changed
line #29:
} else (m/-r/) {
should be
} elsif (m/-r/) {
Cheers,
Waider.
--
[EMAIL PROTECTED] / Yes, it /is/ very personal of me.
kate says, no, there's a lot of red in heliotrope.
kate says, we're talking like #993366 or so
Samba-folk:
The libsmbclient.so in SAMBA_3_0 looks good. The OS-specific checks
don't have NetBSD, though.
The settings are the same as FreeBSD, so the simplest change is in
configure.in, line 894, change from:
*freebsd*) BLDSHARED=true
to
*netbsd* | *freebsd*) BLDSHARED=true
'it seemed like a good idea at the time...'
I've come to the conclusion that 'unixsam' has reached the end of it's
useful life. And a short life it has been to.
Originally added as a way of moving the last of the 'fixed' uid-rid
translations into the passdb backends, and as a way of doing some
I've just come across a problem listing shares on both samba and Win*
boxes using the samba suite.
Initially I tried using 'smbclient -L' and parsing the output using a
perl script, which works to a degree.
The problem is that the V2.x.x smbclient uses the old-style RAP calls
to talk to the
Danny Smith wrote:
I've just come across a problem listing shares on both samba and Win*
boxes using the samba suite.
Initially I tried using 'smbclient -L' and parsing the output using a
perl script, which works to a degree.
The problem is that the V2.x.x smbclient uses the old-style RAP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 21 Jan 2003, Ronan Waide wrote:
Continuing the saga:
Groups are not migrated by the ldap_nua backend, even if I create a
posixGroup entry. After a bit of prodding, I found the latter was
because Samba had set up group mappings in
Hi,
Before writing this mail, I queried google (there's so
many Samba installation hoping I could find an answer!).
I did find an old message posted on samba-technical back in
2001 but my query did not lead me to *the* answer.
Reference:
I forgot to mention this is under LANMAN . I attached
a debug 9 output.
If the supplied password is not good, we shouldn't get
that far... I guess? Unless there's something I don't
get...
I tried to change in lanman.c api_SamOEMChangePassword to
anon not Ok by adding True for fun, didn't work
Hello all(I'm a new face here),
Currently netbios aliases are bcast registered on every subnet on a
multihomed box if samba is operating as a B-node. If it's operating as a
P-node, then I assume samba will just use the interface where a WINS
server is reachable(I haven't examined the code on
[EMAIL PROTECTED] wrote:
Danny Smith [EMAIL PROTECTED] writes:
I've just come across a problem listing shares on both samba and Win* boxes
using the samba suite. Initially I tried using 'smbclient -L' and parsing
the output using a perl script, which works to a degree. The problem is
that
Good evening folks,
I have a WIN2K system and I am failing to authenticate to a Samba 2.2
installation, which I suspect is due to the weird length of Unicode
password length in the SessionSetupAndX message. Here is my
circumstance.
On my W2K machine:
-Run the secpol.msc management plug-in
Check out Chris' book - http://www.ubiqx.org/cifs/SMB.html#SMB.8.5
He's got a great explanation of what we observed while looking at a few
captures.
Also, if you would have a capture of it of the response, I'd love to
take a look at it - there's a few bytes that are still unknown.
Vance
On Tue, Jan 28, 2003 at 08:11:54PM -0700, Vance Lankhaar wrote:
Check out Chris' book - http://www.ubiqx.org/cifs/SMB.html#SMB.8.5
He's got a great explanation of what we observed while looking at a few
captures.
Also, if you would have a capture of it of the response, I'd love to
take a
The SNIA doc provides information on Message Authentication Codes (MACs).
These are signatures contained in the SMB header.
Are these the same as Sign and Seal or are we talking about two
different basilisks altogether?
Chris -)-
--
Samba Team -- http://www.samba.org/ -)-
On Thu, 30 Jan 2003, Christopher R. Hertel wrote:
The SNIA doc provides information on Message Authentication Codes (MACs).
These are signatures contained in the SMB header.
Are these the same as Sign and Seal or are we talking about two
different basilisks altogether?
TDB.
Sign and
On Wed, Jan 29, 2003 at 11:26:16PM -0800, Richard Sharpe wrote:
On Thu, 30 Jan 2003, Christopher R. Hertel wrote:
The SNIA doc provides information on Message Authentication Codes (MACs).
These are signatures contained in the SMB header.
Are these the same as Sign and Seal or are we
19 matches
Mail list logo
