Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 107830 - nmb doesn't work
Summary: nmb doesn't work
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: samba
Version: rawhide
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jay Fenlason
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks: CambridgeBlocker
TreeView+ depends on / blocked
 
Reported: 2003-10-23 14:51 UTC by Roman Krylov
Modified: 2014-08-31 23:25 UTC (History)
2 users (show)

Fixed In Version: 3.0.14a
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-08-20 07:58:06 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Roman Krylov 2003-10-23 14:51:59 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031016

Description of problem:
[*** /]# /etc/rc.d/init.d/smb status
smbd (pid 2784) is running...
nmbd dead but pid file exists


Version-Release number of selected component (if applicable):
3.0.0-5rc1

How reproducible:
Always

Steps to Reproduce:
1.switch on system
2.-
3.-
    

Actual Results:  cannot connect from other computers

Additional info:

-
Comment 1 Jay Fenlason 2004-11-30 16:17:47 UTC 
Can you try the recently released 3.0.9 rpms?  On both my fc2 and rawhide 
boxes, the 
/etc/rc.d/init.d/smb status 
command works as expected, saying that both smbd and nmbd are running.
Comment 2 Marius Andreiana 2005-08-20 07:58:06 UTC 
Works for me in FC4.
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present.  Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.

Setting status to "CURRENTRELEASE", however if you still
experience this problem after updating to our latest Fedora
Core release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.

Thanks in advance.
Note You need to log in before you can comment on or make changes to this bug.