asked on

Fedora 6 Samba Server Access Issue

Hi,

I'm having issues viewing samba shares on a linux box from an xp client. I'm running Fedora Core 6 as the samba server (version 3.x.x). I am able to view the share names in windows, however, if I try to further access the shares I get the following after attempting to log in:

"\\192.168.1.153\myshare-data is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

The network name cannot be found"

I've set up a user account in linux, and then set up the corresponding user in samba via smbpasswd. I've also changed the permissions on the directories being shared to 777 to be sure it wasn't a permissions issue. I have attached my smb.conf here for reference:

#======================= Global Settings =====================================
[global]

# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = mydomain

# server string is the equivalent of the NT Description field
server string = Samba Server

# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
security = user

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
load printers = yes
# This option tells cups that the data has already been rasterized
cups options = raw

# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m.log

# Put a capping on the size of the log files (in Kb).
max log size = 50

# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
; passdb backend = tdbsam

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
dns proxy = no

#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = yes
writable = yes

# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /usr/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
guest ok = no
writable = no
printable = yes

[www-data]
path = /var/www/webdev
browseable = yes
valid users = timmy

Thank you

Gabriel Orozco

you are trying to access
\\192.168.1.153\myshare-data

while you only have shared
[www-data]

so you need to look for
\\192.168.1.153\www-data

Also if you are having troubles with user/permissions it would be good to start with all permissions, then tight them. you can try with adding this line:
force user = timmy
and once everything works you can delete that line and test your permissions

Regards

BiTRaTE2600

ASKER

Sorry, I messed up the post a bit. The error message I typed should have mentioned www-data instead of myshare-data. So that wouldn't be a source of the problem.

No luck with force user = timmy either. I thought "force user" was to force file ownership if a file was added to that particular share? If that is the case, then this shouldn't have any effect on whether I can browse the share. I've tried leaving out the user entirely with no luck. I also tried "public=yes", which I believe makes it readable by anyone with no luck.

Any other ideas?

Thanks much for your response!

ASKER CERTIFIED SOLUTION

BiTRaTE2600

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Vee_Mod

Closed, 500 points refunded.
Vee_Mod
Community Support Moderator