I have tried several times to get ‘smbd’ working on my Nto system. I
have read every piece of documentation I could find and still it
eludes me.
What is the magic?
I am aware that smbd and nmbd can be started either from inetd or a
start-up shell script. I have tried both methods. My preference is is
to start them myself in a shell script because I understand that they
will make initial connections slightly faster.
Let’s assume that all I want is for users to get access to their own
home directories (read/write) and read only access to some other
directory (/other_dir). I don’t need printer support at all.
I have added these lines to these files:
/etc/services:
swat 901/tcp
/etc/inetd.conf
#netbios-ssn stream tcp nowait root /usr/sbin/smbd smbd
#netbios-ns dgrap udp wait root /usr/sbin/nmbd nmbd
swat stream tcp nowait.400 root /opt/sbin/swat swat -a
I’m still trying to start smbd & nmbd from my own startup file:
/usr/sbin/smbd -D
/usr/sbin/nmbd -D
I have had many different /etc/samba/smb.conf files ranging from very
complex (with the help of swat) to very simple (my own hand creations).
Here is my current /etc/samba.cmb.conf file:
Global parameters
[global]
workgroup = TRACKSTAR
server string = QNX 6.2.1 Server
log file = /usr/local/samba/log.%m
load printers = No
preferred master = No
local master = No
domain master = No
guest account = pcguest
printing = bsd
[tmp]
comment = Temporary file space
path = /tmp
guest ok = Yes
When I try to test this with:
smbclient -L TRACKSTAR
I got:
added interface ip=192.168.1.223 bcast=192.168.1.255 nmask=255.255.255.0
Connection to TRACKSTAR failed
When I tried:
smbclient -L dell.ts (the host name of this system)
I got:
added interface ip=192.168.1.223 bcast=192.168.1.255 nmask=255.255.255.0
Password:
session setup failed: NT_STATUS_LOGON_FAILURE
BTW: It never paused for me to enter a password.
Dave Latter <DLatter@hollandco.com> wrote:
I have tried several times to get ‘smbd’ working on my Nto system. I
have read every piece of documentation I could find and still it
eludes me.
What is the magic?
You should run nmbd first, and let it detach instead of using &.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Chris McKillop <cdm@qnx.com> wrote:
CM > Dave Latter <DLatter@hollandco.com> wrote:
I have tried several times to get ‘smbd’ working on my Nto system. I
have read every piece of documentation I could find and still it
eludes me.
What is the magic?
CM > You should run nmbd first, and let it detach instead of using &.
CM > chris
I just tried running nmbd first. There was no difference.
I never did have a '&" on the command line.
Is there another guess?
Doesn’t anyone have smbd working under QNX?
Dave Latter <DLatter@hollandco.com> wrote:
DL > Chris McKillop <cdm@qnx.com> wrote:
DL > CM > Dave Latter <DLatter@hollandco.com> wrote:
I have tried several times to get ‘smbd’ working on my Nto system. I
have read every piece of documentation I could find and still it
eludes me.
What is the magic?
DL > CM > You should run nmbd first, and let it detach instead of using &.
DL > CM > chris
DL > I just tried running nmbd first. There was no difference.
DL > I never did have a '&" on the command line.
DL > Is there another guess?
I surely do.
Guessing is not going to get you far. Look into smbd/nmbd log files for
error messages. Most of the time it is something silly, like being unable to
resolve your hostname, et cetera.
– igor
“Dave Latter” <DLatter@hollandco.com> wrote in message
news:bqqvfa$blq$1@inn.qnx.com…
Doesn’t anyone have smbd working under QNX?
Dave Latter <> DLatter@hollandco.com> > wrote:
DL > Chris McKillop <> cdm@qnx.com> > wrote:
DL > CM > Dave Latter <> DLatter@hollandco.com> > wrote:
I have tried several times to get ‘smbd’ working on my Nto system. I
have read every piece of documentation I could find and still it
eludes me.
What is the magic?
DL > CM > You should run nmbd first, and let it detach instead of using &.
DL > CM > chris
DL > I just tried running nmbd first. There was no difference.
DL > I never did have a '&" on the command line.
DL > Is there another guess?
Igor Kovalenko wrote:
I surely do.
Guessing is not going to get you far. Look into smbd/nmbd log files for
error messages. Most of the time it is something silly, like being unable to
resolve your hostname, et cetera.
Actually, I have encountered several situations where someone trying to set up
Samba powered off their machine during the process, and the lock files (under
var) didn’t get deleted, and then were baffled by the fact that samba wouldn’t
start. Deleting the lock files will fix the problem if this is the case.
Rennie Allen <rallen@csical.com> wrote:
RA > Igor Kovalenko wrote:
I surely do.
Guessing is not going to get you far. Look into smbd/nmbd log files for
error messages. Most of the time it is something silly, like being unable to
resolve your hostname, et cetera.
RA > Actually, I have encountered several situations where someone trying to set up
RA > Samba powered off their machine during the process, and the lock files (under
RA > var) didn’t get deleted, and then were baffled by the fact that samba wouldn’t
RA > start. Deleting the lock files will fix the problem if this is the case.
Yes. There were lock files and *.tdb files that had to be deleted.
Now it works as expected.
Very User Friendly - NOT !
SMBD is now essentially working. I do still have one problem.
When I edit a file from another host (a QNX4 host in this case) the
date/time stamp on the file appears to almost be a random number.
Sometimes it is many years in the future, sometimes it is many years
in the past.
Is there something else that I have to tweek?
Dave Latter wrote:
Yes. There were lock files and *.tdb files that had to be deleted.
Now it works as expected.
Very User Friendly - NOT !
Yeah. This has stung several people that I know of 
You can add a script to your /etc/rc.d/rc.local to delete all of these
files on startup (if Samba was properly shut down they shouldn’t be
there anyway).