General
cancel
Showing results for 
Search instead for 
Did you mean: 

Problem Accessing a Samba 3.0 Share

Andrew Kaplan
Super Advisor

Problem Accessing a Samba 3.0 Share

Hi there --

We have Samba 3.0.23a running on a Fedora Core 4 system, but our remote systems are unable to access a share.

The /etc/init.d/smb script referenced the smb.conf file located in the /etc/samba directory, but the file in question was not located there. There was such a file available in the /usr/share/doc/samba-3.0.23a/LDAP/smbldap-tools-0.9.2 directory, and I copied that file to the /etc/samba directory.

The share in question has the following configuration:

[adv4dexport]
path = /export/home1/sdc_image_pool/appli/Advantage4DCT/sbreath/motion_files
comment = Respiratory Motion files directories
public = yes
writable = yes
oplocks = false
printable = no
guest ok = yes
browsable = yes
create mask = 0777
directory mask = 0777

The above configuration is based on a similar configuration that works on another system that utilizes samba 2.2.3a. After copying the smb.conf file, and editting it, the /etc/init.d/smb script was started and both smbd and nmbd started without problems.

Whenever a remote system tries to connect to the above share, the error message that is displayed on the remote system is "Network Path Cannot Be Found"

I am not familiar with Samba 3.x, although my guess is there is a problem with the smb.conf file. Has anyone seen this, and know what the solution is for me to take? Thanks.
A Journey In The Quest Of Knowledge
2 REPLIES
Ivan Ferreira
Honored Contributor

Re: Problem Accessing a Samba 3.0 Share

Is weird that smb.conf is not there, can you post the output of:

rpm -qa | grep samba

What is the output of service smb status?

Can you "attach" the whole smb.conf file?

Post the output of smbclient -L //servername
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Andrew Kaplan
Super Advisor

Re: Problem Accessing a Samba 3.0 Share

Hi there --

Thanks for your reply. The answers to your questions are shown below.

The output of the rpm -qa |grep samba command is the following:

samba-client-3.0.23a-1.fc4.1
samba-common-3.0.23a-1.fc4.1
system-config-samba-1.2.31-1
samba-3.0.23a-1.fc4.1

There was no output from the service smb status command.

Per your request, the smb.conf file is attached to this e-mail.

The output of the smbclient command is shown below:

Unknown parameter encountered: "min passwd length"
Ignoring unknown parameter "min passwd length"
WARNING: The "printer admin" option is deprecated
Error connecting to 132.183.20.114 (Connection refused)
Connection to 132.183.20.114 failed
A Journey In The Quest Of Knowledge