LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices



Reply
 
Search this Thread
Old 02-10-2005, 04:39 AM   #1
vyom
LQ Newbie
 
Registered: Feb 2005
Location: Bangalore, India
Distribution: RedHat 9.0, Fedora Core 3
Posts: 18

Rep: Reputation: 0
Unhappy samba on fedora connects to linux machine but unseen on windows machines


hi,

i'm unable to access my FC3 machine's samba share from windows machines. first of all, i'll explain the scenario.

i have about a dozen machines in my office. two machines run linux: one RH9 and the other FC3, and rest are windows 2000 machines. i was successful in configuring the samba on the RH9 box, and all my win 2k machines are able to see the samba share files on the RH box. but, my FC3 shares are not seen by the windows machines. i can access the shares on the FC3 from the other linux box, and vice-versa. but, from windows it is not the same case. neither way i'm able to see the shares. i followed the same steps to configure samba on FC3 as i did on RH 9. no luck

any sugessions? one more thing, i'm running the samba service on both the linux boxes. i tried stopping samba on one of the boxes, but no use.

thanx for all sugessions in advance!

mahesh
 
Old 02-10-2005, 02:30 PM   #2
david_ross
Moderator
 
Registered: Mar 2003
Location: Scotland
Distribution: Slackware, RedHat, Debian
Posts: 12,047

Rep: Reputation: 65
Can you post a copy of your smb.conf file and the output from:
netstat -nlp
iptables -nL
 
Old 02-11-2005, 12:23 AM   #3
vyom
LQ Newbie
 
Registered: Feb 2005
Location: Bangalore, India
Distribution: RedHat 9.0, Fedora Core 3
Posts: 18

Original Poster
Rep: Reputation: 0
Lightbulb hmmm, it is the problem with the firewall settings!

thanx david!

some fiddling around with the system settings revealed that the problem was because of firewall settings. the firewall rules generated by the system had closed the samba access. so i ran my own firewall rules with samba port open. but the problem persists. i will give both the system-generated and my own firewall rules.

i'll be extrmly happy to hear any comments on my samba configuration and firewall settings. looking at my firewall rules, may i get some help improving them?

my firewall rules:

Chain INPUT (policy DROP)
target prot opt source destination
ACCEPT all -- 127.0.0.1 0.0.0.0/0
udpPortAllowInt udp -- 0.0.0.0/0 0.0.0.0/0
tcpPortAllowInt tcp -- 0.0.0.0/0 0.0.0.0/0
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
tcpPortAllowInt tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:901
tcpPortAllowInt tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:7
tcpPortAllowInt tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:21
tcpPortAllowInt tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:25
tcpPortAllowInt tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:53
tcpPortAllowInt tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:80
tcpPortAllowInt tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:109
tcpPortAllowInt tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:110
tcpPortAllowInt tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:174
tcpPortAllowInt tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:177
tcpPortAllowInt tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:194
tcpPortAllowInt tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:443
tcpPortAllowInt tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:2401
tcpPortAllowInt tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:8080
tcpPortAllowInt tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:8083
tcpPortAllowInt tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:3306
udpPortAllowInt udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:901
udpPortAllowInt udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:7
udpPortAllowInt udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:21
udpPortAllowInt udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:25
udpPortAllowInt udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:53
udpPortAllowInt udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:80
udpPortAllowInt udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:109
udpPortAllowInt udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:110
udpPortAllowInt udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:174
udpPortAllowInt udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:177
udpPortAllowInt udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:194
udpPortAllowInt udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:443
udpPortAllowInt udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:2401
udpPortAllowInt udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:3306
ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 icmp type 11
ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 icmp type 11
ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 icmp type 8

Chain FORWARD (policy DROP)
target prot opt source destination

Chain OUTPUT (policy DROP)
target prot opt source destination
ACCEPT all -- 127.0.0.1 0.0.0.0/0
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0

Chain tcpPortAllowInt (17 references)
target prot opt source destination
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0

Chain udpPortAllowInt (15 references)
target prot opt source destination
ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0


system generated firewall rules :

Chain INPUT (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- 0.0.0.0/0 0.0.0.0/0

Chain FORWARD (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- 0.0.0.0/0 0.0.0.0/0

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Chain RH-Firewall-1-INPUT (2 references)
target prot opt source destination
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 icmp type 255
ACCEPT esp -- 0.0.0.0/0 0.0.0.0/0
ACCEPT ah -- 0.0.0.0/0 0.0.0.0/0
ACCEPT udp -- 0.0.0.0/0 224.0.0.251 udp dpt:5353
ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:631
ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:80
ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:21
REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited


thanx,
mahesh
 
Old 02-11-2005, 01:36 PM   #4
david_ross
Moderator
 
Registered: Mar 2003
Location: Scotland
Distribution: Slackware, RedHat, Debian
Posts: 12,047

Rep: Reputation: 65
Regardless of whether you use your own rules or the lokkit tool, you need to allow the following ports:
137/udp
138/udp
139/tcp
 
Old 02-16-2005, 04:21 AM   #5
vyom
LQ Newbie
 
Registered: Feb 2005
Location: Bangalore, India
Distribution: RedHat 9.0, Fedora Core 3
Posts: 18

Original Poster
Rep: Reputation: 0
hi,

well, now, the windows machines can access the shares on fc3, but, not vice-versa. even before i am asked for the password, the samba client says "error displaying folder.......... u do not have the permissions necessary to view the contents of ......". i'm able to access the shares on the other linux machines frm the fc3 box. the firewall has ports 137, 138, 139 open. any sugessions? here is my smb.conf:....


# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]

# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = workgroup

# server string is the equivalent of the NT Description field
server string = Fedora Core 3

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
hosts allow = 192.80.9. 127.

# 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

# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx
; printing = cups

# This option tells cups that the data has already been rasterized
cups options = raw

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest

# 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/smbd.log

# 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.
# Use password server option only with security = server
; password server = <NT-Server-Name>

# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
; password level = 8
; username level = 8

# 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*successfully*

# 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

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes

# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes

# 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
username map = /etc/samba/smbusers
password server = None
guest ok = yes
guest account = mahesh
winbind use default domain = no
[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
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


[mahesh]
path = /home/mahesh
writeable = yes

Last edited by vyom; 02-16-2005 at 04:39 AM.
 
Old 07-04-2006, 03:25 AM   #6
jacx
LQ Newbie
 
Registered: Jul 2006
Posts: 1

Rep: Reputation: 0
Hello Everybody!! please help to resolve the below problem

I have issue regarding samba connectivity. I already make amendments in /etc/samba/smb.conf according to my network profile. Now my printer and file sharing is o.k. The only issue regarding sharing of windows machine via linux os. Whenever I clicked on network icon in linux it shows me every machine that exist in my LAN but as soon as I clicked upon any machine it not showing me any files under that machine name though there are already files are shares in windows. I want to access the shared files from windows in linux. For further ref. the view of my smb.conf as below :


[global]

guest account =linux_mac
workgroup = alliance
encrypt password = yes
password level = 20

restrict anonymous = no
domain master = no
preferred master = no
max protocol = NT
ldap ssl = No
server signing = Auto

[printer@linux]
printable = yes
printer name = printer-m125


[homes]
comment = Home Dir of linux user
browseable = no
read only = no
create mode = 0750




[Common_ Dir]

# comment=common
# path=/home/common
# read only=no
# public=yes



comment= Software
path=/sda6/software
read only=no
public=yes

[LINUX_WIN]

comment=linux_share
path=/sda6/linux_docs
read only=no
public=yes
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Windows Can't See Linux Machine After Configuring Samba! movanns Linux - Networking 6 02-13-2014 02:52 AM
Joining Samba 3.0 Linux machine to a Windows AD Domain markham82 Linux - Networking 1 10-08-2004 04:21 AM
Trying to run samba from linux to windows xp machine... jmax24 Linux - Networking 2 04-20-2004 04:43 AM
when fedora machine is connected to the internet via network windiws machines cannot purbeck Linux - Networking 1 01-24-2004 08:50 AM
browsing windows machines in linux machine SSENT12 Linux - Networking 8 07-21-2003 10:04 PM


All times are GMT -5. The time now is 10:07 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration