Greetings,
Disclaimer: I am using my own build of SAMBA 2.0.7 which I built from
source. I effectivelly have everything that might be found in a SAMBA
distribution. I am not sure what the package on QNX start has.
If you would like to ‘fix’ your windows clients there are files in the /docs
directory named NT4_PlainPasswords.reg, Win2000_PlainPasswords.reg,
Win98_PlainPasswords.reg, and Win95_PlainPasswords.reg.
If you do not have these files you can download the SAMBA archive from
samba.org and untar it. There will be a /docs directory there (you do not
need to build anything).
The other option is that you enable encrypted passwords in SAMBA. Change
your smb.conf file to include …
[global]
security = user
encryp passwords = yes
smb passwd file = /somewhere/there/is/a/passwdfile
You have to init the password file. That is, you have to add the users which
will be connecting through SAMBA …
smbpasswd -a username
… and then type in the same password as on your Windows machine.
You can synchronise your password with your RTP password automatically. Just
at “unix password sync = yes” to your “[global]” section.
]{ristoph
“Jose Luis” <> joseluis1569@my-deja.com> > wrote in message
news:> 3a9ec1aa.8536386@inn.qnx.com> …
It is a password encrytion problem, Samba wants passwords in clear text,
but Windows
sends them encryted. The distribution includes a file that must be
imported into the
registry (NT_PlainText.reg, or something like that).
This trick fixes the problem on NT machines, but not under Win95/98. Does
anyone
have the solution for these two OSes?
On Wed, 28 Feb 2001 10:45:38 -0500, “John Bowen” <> John.Bowen@grc.nasa.gov
wrote:
That fixed the problem with nmbd dying. Now I’m getting errors when
trying
to map to a share from Win2k that says “The account is not authorized to
log
in from this station”. The “hosts allow” and “hosts deny” sections of
smb.conf are empty. According to the docs, this allows all machines
access.
john
“Sean Boudreau” <> seanb@qnx.com> > wrote in message
news:97j3ba$ogi$> 1@nntp.qnx.com> …
The tiny stack doesn’t support SO_REUSEADDR on udp sockets
(mentioned in docs) which seems to be the major problem here.
It probably shouldn’t core dump though.
You might try the full stack. See:
http://qdn.qnx.com/support/bok/solution.qnx?10080
-seanb
John Bowen <> John.Bowen@grc.nasa.gov> > wrote:
: I’ve been trying to get Samba to work, like FibreBoy has been, and
I’m
: having some other trouble. The nmbd daemon keeps dying and
restarting.
: Below is a dump of the /usr/local/samba/var/log.nmb file. Any ideas?
I
: have the /etc/services ports defined as follows:
: netbios-ns 137/udp # NETBIOS Name Server
: netbios-dgm 138/udp # NETBIOS Datagram
Service
: netbios-ssn 139/udp # NETBIOS Session
Service
: netbios-ssn 139/tcp
: and /etc/inetd.conf set to the following:
: netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd
: netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd
: swat stream tcp nowait.400 root /usr/local/samba/bin/swat swat
: john
: *** snip ***
: [2001/02/28 07:08:01, 1] nmbd/nmbd.c:main(757)
: Netbios nameserver version 2.0.7 started.
: Copyright Andrew Tridgell 1994-1998
: [2001/02/28 07:08:01, 0] lib/util_sock.c:open_socket_in(849)
: setsockopt: SO_REUSEADDR=1 on port 137 failed with error =
Operation
not
: supported
: [2001/02/28 07:08:01, 0] lib/util_sock.c:open_socket_in(853)
: setsockopt: SO_REUSEPORT=1 on port 137 failed with error =
Operation
not
: supported
: [2001/02/28 07:08:01, 0] lib/util_sock.c:open_socket_in(863)
: bind failed on port 137 socket_addr=139.88.52.227 (Address already
in
use)
: [2001/02/28 07:08:01, 0] nmbd/nmbd_subnetdb.c:make_subnet(142)
: nmbd_subnetdb:make_subnet()
: Failed to open nmb socket on interface 139.88.52.227 for port 137.
Error
: was Address already in use
: [2001/02/28 07:08:01, 0] nmbd/nmbd.c:main(817)
: ERROR: Failed when creating subnet lists. Exiting.
: [2001/02/28 07:08:02, 1] nmbd/nmbd.c:main(757)
: Netbios nameserver version 2.0.7 started.
: Copyright Andrew Tridgell 1994-1998
: [2001/02/28 07:08:02, 0] lib/util_sock.c:open_socket_in(849)
: setsockopt: SO_REUSEADDR=1 on port 137 failed with error =
Operation
not
: supported
: [2001/02/28 07:08:02, 0] lib/util_sock.c:open_socket_in(853)
\
Alain.