Bug 650 - Issue with Samba Client share
Summary: Issue with Samba Client share
Alias: None
Product: Samba 2.2
Classification: Unclassified
Component: smbclient (show other bugs)
Version: 2.2.8a
Hardware: Other Windows 98
: P1 critical
Target Milestone: ---
Assignee: Gerald (Jerry) Carter (dead mail address)
QA Contact:
Depends on:
Reported: 2003-10-19 04:35 UTC by Nav
Modified: 2004-02-17 08:56 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Nav 2003-10-19 04:35:29 UTC
We are using samba services for establishing connection btw Unix server & 
Windows 95 PC. Samba services are running at Sun Server. The issue is that all 
of sudden for unknown reasons samba client share  goes down. Root processes 
nmbd & smbd (with PID = 1) keeps on running. Here is one sample:
Following is the samba status, when there is a samba connection with 
PC "client123"
Samba version 2.2.8a
Service      uid      gid      pid     machine
queue01      aradmin  remedy   11583   client123  ( Sun Oct 19 
15:43:20 2003

& here are the samba processes :
root  1151     1  0   Oct 05 ?  0:00 /usr/local/samba/bin/smbd -D -s/u
root  1156     1  0   Oct 05 ?  0:09 /usr/local/samba/bin/nmbd -D -s/u
root  1162  1156  0   Oct 05 ?  0:00 /usr/local/samba/bin/nmbd -D -s/u
root 11583  1151  0 15:43:18 ?  0:05 /usr/local/samba/bin/smbd -D -s/u

When the samba share for client "client123" goes down then we don't have 
anything beneath samba status & the following process (last one)  processes 
heading get killed. samba processes still shows remaining 3 processes.

root 11583  1151  0 15:43:18 ?  0:05 /usr/local/samba/bin/smbd -D -s/u
Now-a-days samba is dropping share very frequently. Samba plays a critical role 
in our application. Any help in this regard will be greatly appreciated.

Comment 1 Gerald (Jerry) Carter (dead mail address) 2004-02-17 08:56:06 UTC
Sorry, but the 2.2 is not under development any longer.
If you can reproduce this bug against the latest 3.0 release, 
please reopen this bug and change the version in the report.