View Full Version : Conecting to Linux Share From XP
lfirth
2006-06-07, 10:07 PM CDT
Hi,
This is my situation. I have a Windows XP box connected to a Fedora Core 4 Linux box via a wireless card. The problem I am having is not with network connectivity because I can ping the linux box and even connect via remote desktop (VNC). I have followed the instructions at www.reallylinux.com/docs/sambaserver.html and when I go to "My Network Places/View Workgroup Computers" I can see the linux box "Samba Server (localhost)". As soon as I try to connect to it though I get the following message:
"\\Localhost\Lee is not accessable. 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."
It's not a firewall problem because I have disabled the firewall on the linux box. Below are gif images of my samba setup:
http://www.firthcomputerservices.com.au/EditSambaShare_Access.gif
http://www.firthcomputerservices.com.au/EditSambaShare_Basic.gif
http://www.firthcomputerservices.com.au/ServerSettings_Basic.gif
http://www.firthcomputerservices.com.au/ServerSettings_Security.gif
Thanks.
byroniac
2006-06-07, 11:29 PM CDT
I tried several times before getting this same thing to work, and I forgot exactly what I did. Some things to try:
1. Are the passwords the same on the XP and Linux boxes for that account?
2. Try using Share security instead of User (last image)? Or not encrypting passwords?
3. Have you set up a Samba user under Preferences -> Samba Users? *EDIT* I set up my own Linux account as a Samba user on my machine (I think this actually specifies what privileges the Samba connectivity has when it is active).
Sorry, I'm grasping for straws here due to memory failure.
jhetrick62
2006-06-07, 11:45 PM CDT
Post your smb.conf file. That is more helpful that the screenshots.
Jeff
lfirth
2006-06-08, 12:05 AM CDT
Post your smb.conf file. That is more helpful that the screenshots.
Jeff
Hi Jeff,
I'm pretty much a newbe to linux and so try not to go editing config files if I can help it. I usualy use the GUI if I can, bet here it is:
#======================= Global Settings ====================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = mshome
# server string is the equivalent of the NT Description field
server string = Samba Server
# if you want to automatically load your printer list rather # than setting them up individually then you'll need this
printcap name = /etc/printcap
load printers = yes
# this tells Samba to use a separate log file for each machine # that connects
log file = /var/log/samba/%m.log
# all log information in one file
# log file = /var/log/samba/log.smbd
# Put a capping on the size of the log files (in Kb).
max log size = 50
# Security mode. Most people will want user level security. See # security_level.txt for details.
; security = user
# Use password server option only with security = server
; password server = <NT-Server-Name>
# You may wish to use password encryption. Please read # ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents ; encrypt passwords = yes ; smb passwd file = /etc/samba/smbpasswd
# The following are needed to allow password changing from Windows to # update the Linux system password also.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
# the encrypted SMB passwords. They allow the Unix password
# to be kept in sync with the SMB password.
; unix password sync = Yes
; passwd program = /usr/bin/passwd %u
; passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n \n *passwd:*all*authentication*tokens*updated*success fully*
# Unix users can map to different SMB User names ; username map = /etc/samba/smbusers
# Using the following line enables you to customise your configuration # on a per machine basis. The %m gets replaced with the netbios name # of the machine that is connecting
; include = /etc/samba/smb.conf.%m
# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
# Configure Samba to use multiple interfaces # If you have multiple network interfaces then you must list them # here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24
# Configure remote browse list synchronisation here # request announcement to, or browse list sync from:
# a specific host or from / to a whole subnet (see below)
; remote browse sync = 192.168.3.25 192.168.5.255
# Cause this host to announce itself to local subnets here
; remote announce = 192.168.1.255 192.168.2.44
# Browser Control Options:
# set local master to no if you don't want Samba to become a master # browser on your network. Otherwise the normal election rules apply
; local master = no
# OS Level determines the precedence of this server in master browser # elections. The default value should be reasonable
; os level = 33
# if you enable domain logons then you may want a per-machine or # per user logon script # run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U
# All NetBIOS names must be resolved to IP Addresses # 'Name Resolve Order' allows the named resolution mechanism to be specified # the default order is "host lmhosts wins bcast". "host" means use the unix # system gethostbyname() function call that will use either /etc/hosts OR # DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch.conf # and the /etc/resolv.conf file. "host" therefore is system configuration # dependant. This parameter is most often of use to prevent DNS lookups # in order to resolve NetBIOS names to IP Addresses. Use with care!
# The example below excludes use of name resolution for machines that are NOT # on the local network segment # - OR - are not deliberately to be known via lmhosts or via WINS.
; name resolve order = wins lmhosts bcast
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT
both
; wins server = w.x.y.z
# WINS Proxy - Tells Samba to answer name resolution queries on # behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names # via DNS nslookups. The built-in default for versions 1.9.17 is yes, # this has been changed in version 1.9.18 to no.
dns proxy = no
# Case Preservation can be handy - system default is _no_ # NOTE: These can be set on a per share basis ; preserve case = no ; short preserve case = no # Default case is normally upper case for all DOS files ; default case = lower # Be very careful with case sensitivity - it can break things!
; case sensitive = no
#============================ Share Definitions ==============================
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
template shell = /bin/false
winbind use default domain = no
username map = /etc/samba/smbusers
; security = user
; encrypt passwords = yes
; guest ok = no
; guest account = nobody
; security = user
; encrypt passwords = yes
; guest ok = no
; guest account = nobody
; encrypt passwords = yes
; guest ok = no
; guest account = nobody
[homes]
comment = Home Directories
browseable = no
writeable = yes
# Un-comment the following and create the netlogon directory for Domain Logons ; [netlogon]
; comment = Network Logon Service
; path = /home/netlogon
; guest ok = yes
; writable = no
; share modes = no
# Un-comment the following to provide a specific roving profile share # the default is to use the user's home directory ;[Profiles]
; path = /home/profiles
; browseable = no
; guest ok = 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 = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
; guest ok = no
; writeable = no
printable = yes
# This one is useful for people to share files ;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes
# A publicly accessible directory, but read only, except for people in # the "staff" group ;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; read only = yes
; write list = @staff
# Other examples.
#
# A private printer, usable only by fred. Spool data will be placed in fred's # home directory. Note that fred must have write access to the spool directory, # wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
# A private directory, usable only by fred. Note that fred requires write # access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
# a service which has a different directory for each machine that connects # this allows you to tailor configurations to incoming machines. You could # also use the %u option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes
# A publicly accessible directory, read/write to all users. Note that all files # created in the directory by users will be owned by the default user, so # any user with access can delete any other user's files. Obviously this # directory must be writable by the default user. Another user could of course # be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no
# The following two entries demonstrate how to share a directory so that two # users can place files there that will be owned by the specific users.
In this
# setup, the directory should be writable by both users and should have the # sticky bit set on it to prevent abuse. Obviously this could be extended to # as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
[Lee]
comment = Lee's home drive on Linux
path = /home/Lee
writeable = yes
browseable = yes
valid users = Lee
icydog
2006-06-08, 12:48 AM CDT
What about the ports? Are the samba ports (I don't know which ones those are) open in iptables?
lfirth
2006-06-08, 05:51 AM CDT
What about the ports? Are the samba ports (I don't know which ones those are) open in iptables?
I don't know how would I check that?
byroniac
2006-06-08, 11:39 AM CDT
According to this, the ports are 137, 138, 139, and 445.
http://www.samba.org/samba/docs/server_security.html
I missed the fact that you are using FC4 not FC5. FC5 is the first Fedora I've ever used. I think though (in FC5 at least) the two main things to check are these:
1. Preferences -> Samba Users (make sure you set up one)
2. SELinux (automatically blocks access to user home directories... on FC5 you have to modify the policy or set it to permissive).
sankarsrini
2006-06-09, 05:48 AM CDT
hi,
Good day for all
I face the same problem in my network. I change the ownership and readwrite permission on the shared folder and files. then the problem is solved.
I need one clarification is it possible to configure samba and squid in a single linux box. when I installed squid in the machine both are correpted.
jhetrick62
2006-06-11, 08:05 PM CDT
lfirth, Did you get this corrected? I've been out of town for several days with no access and I just got back.
Jeff
sankarsrini
2006-06-12, 10:28 AM CDT
I cont understand what u come to say
vBulletin® v3.7.3, Copyright ©2000-2008, Jelsoft Enterprises Ltd.