LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices

Reply
 
Search this Thread
Old 05-06-2004, 10:03 AM   #1
cvc505
LQ Newbie
 
Registered: May 2004
Distribution: Red Hat 9.0
Posts: 23

Rep: Reputation: 15
unable to connect to smb shares on linux RH9.0


Greetings all:

I am a fairly new user to linux and am trying to comnfigure a test system as a file server ( possible Novell/windows 2000 replacement) using Red Hat 9.0. My problem comes from the smb setup. After modifing the smb.conf file ( see listing below) I am able to run the local check and the system seems to be working. However, I am not able to see the server when I try to access it from my windows XP machine nor am I able to connect from my linux work station.

From the XP machine:

I am able to Ping the smb server.
Cannot browse the network neighborhood and find the smb server
Cannot search for a computer and find the smb server.

From the Linux workstation:

I can ping the smb server
running "smbclient -L192.168.0.5'' yeilds:
added interface 192.168.0.155 ....... (.... other data as usual, 192.168.0.155 is ip address of workstation)
Error connecting to 192.168.0.5:139 (connection refused) (Does this mean my port 139 is closed?)
error connecting to 192.168.0.5 ( connection refused)
connection to 192.168.0.5 failed

WINS services are provided my a networked win2k server at IP 192.168.0.26

Workgroup name is : "workgroup"
smb.log and nmb.log don't seem to show anything of value. My logging setting may be wrong in the smb.conf file

Any help or suggestions you can make would be helpful.
Rick




SMB.CONFIG is:

# 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
netbios name = linuxsrv1
netbios aliases = bigsamba

# server string is the equivalent of the NT Description field
server string = linux1 smb server

# 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.168.0. 192.168.1. 127.
hosts allow = 192.168.0. 192.168.1. 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, cups
; printing = cups

# 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/
debug level = 3
# Put a capping on the size of the log files (in Kb).
max log size = 1001

# Security mode. Most people will want user level security. See
# security_level.txt for details.
security = USER

# Use password server option only with security = serverHard Disc
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password 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 is needed to keep smbclient from spouting spurious errors
# when Samba is built with support for SSL.
; ssl CA certFile = /usr/share/ssl/certs/ca-bundle.crt

# 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*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*

# You can use PAM's password change control flag for Samba. If
# enabled, then PAM will be used for password changes when requested
# by an SMB client instead of the program listed in passwd program.
# It should be possible to enable this without changing your passwd
# chat parameter for most setups.

pam password change = yes

# Unix users can map to different SMB User names
; username map = /etc/samba/smbusersHard Disc

# 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

# This parameter will control whether or not Samba should obey PAM'sHarHard Discd Disc
# account and session management directives. The default behavior is
# to use PAM for clear text authentication only and to ignore any
# account or session management. Note that Samba always ignores PAM
# for authentication in the case of encrypt passwords = yes

; obey pam restrictions = yes Hard Disc

# 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
interfaces = 192.168.0.6/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

# 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 = 192.168.0.26

# 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.
guest ok = yes
guest account = rjh
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 ==============================
[homes]
comment = Home Directories
browseable = no
writeable = yes
valid users = %S
create mode = 0664
directory mode = 0775
# If you want users samba doesn't recognize to be mapped to a guest user
; map to guest = bad user


# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/local/samba/lib/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 = /usr/local/samba/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
; writable = yes
; printable = no
; 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 = /home/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/local/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

[vol1]
comment = 4Gig volume
path = /mnt/vol1
writeable = yes
guest ok = yes

[vol2]
comment = 9 Gig Volume
path = /mnt/vol2
writeable = yes
guest ok = yes
 
Old 05-06-2004, 12:06 PM   #2
sandiegocal
LQ Newbie
 
Registered: Mar 2004
Location: san diego
Posts: 16

Rep: Reputation: 0
i use debian, so this might be slightly different, but it should be close enough.

rename your current smb.conf file and create a brand new one with these lines.

[global]
netbios name = linuxsrv1
workgroup = WORKGROUP
security = SHARE

[projects]
path = /projects
comment = /projects
public = yes
guest ok = yes
writeable = yes

then open a root shell, cd to /, and then mkdir projects
chmod 777 projects

after you restart your smbd, you should be able to get to the share in Windows Network Neighborhood, or just Start>run>\\linuxsrv1\projects

start simple and then add functionality as you learn more.

go to samba.org and download the Samba HOWTO pdf:
http://us1.samba.org/samba/docs/Samb...Collection.pdf

and consider Terpstra's new book "Samba 3 - By Example" at amazon for $30 or wait for it to be a free download .pdf in a few months.

please write back to let me (and others reading this thread) know if this works, or how you solved it otherwise.

Last edited by sandiegocal; 05-06-2004 at 01:00 PM.
 
Old 05-06-2004, 03:07 PM   #3
cvc505
LQ Newbie
 
Registered: May 2004
Distribution: Red Hat 9.0
Posts: 23

Original Poster
Rep: Reputation: 15
Unhappy

sandiegocal

As I have been working with this today I realized that I was able to see the server linuxsrv1 in my network neighborhood, but was not able to connect to it. However, after I made the changes you suggested, I am no longer able to see the server from my windows XP machine. I have rebooted both the XP and the linux boxes just to make sure. As I said in my earlier message, the wins server is running on a separate windows 2000 server so that may have something to do with it just not sure what.

I am able to run the smbclient -L localhost -U% command and get what looks like a valid response so I am guessing that the samba server is working correctly. Any other suggestions? Would samba 3 be any better?
Rick
 
Old 05-06-2004, 04:08 PM   #4
sandiegocal
LQ Newbie
 
Registered: Mar 2004
Location: san diego
Posts: 16

Rep: Reputation: 0
sorry, i missed that bit of information about wins.
i also made the assumption that you were running samba 3.

what i wrote is only good if you are just trying to connect a workgroup together using linux (samba 3) and windows (any flavor).

if you want to switch to samba 3, i can probably help you. i am fairly new at linux myself, but have experience in windows 2000 domains primarily (mcsa). i have set up several linux fileservers in domains and workgroups to replace or add to windows servers. have not worked with wins much, but it should not be a problem.

i will have to write back tomorrow when i have more time.
you will probably need a wins statement in your smb.conf

in the meantime, you may want to fill in more information about your network for me or others. do you have a domain set up? are the xp and linux box on the same network segment?
 
Old 05-06-2004, 04:18 PM   #5
cvc505
LQ Newbie
 
Registered: May 2004
Distribution: Red Hat 9.0
Posts: 23

Original Poster
Rep: Reputation: 15
Currently I do not use a domain as my main network here is a novell system. I am working with the samba server and RH9.0 in an attempt to prevent a major meltdown. My Novell server is 5 years old and is getting a little long in tooth. all of my computers are on the same segment so routers are not the issue. At one point this morning I was able to see my linux server but now I am not seeing it.

At some point I will probably have to establish a domain controller but I was hoping I could avoid that for now. According to the various documents I have seen the basic smb.conf you suggested should work for a wins based system but then I am so new at this, what would I know? I am trying to get ethereal up and running on my linux workstation, so I can see what might be going on with the packets, I hope that will help shed some light.

It looks like my RH9.0 install installed the ethereal but I have not been able to find it or make it run. Any other suggestions?
 
Old 05-06-2004, 07:46 PM   #6
sandiegocal
LQ Newbie
 
Registered: Mar 2004
Location: san diego
Posts: 16

Rep: Reputation: 0
i got to thinking about this on the way home. i believe your problem is related to novell, but only because i can't think of anything else.

samba is IP based, and perhaps your novell (since it is older) is ipx/spx based. perhaps they cannot talk to each other without some modifications.

i don't think the problem is wins related, since everything is on one segment (in fact, not sure why you are using wins at all, but i am sure you have your reasons). my limited knowledge of wins is that it provides name resolution across multiple segments, and should not be necessary on a single segment.

anyway, my two suggestions would be this:
1. if there is any way possible to connect JUST the xp and linux using a hub, and test my smb.conf file. then add the wins server, and test again. if that all works then you can be sure it is a novell related problem.

2. repost your question in the networking forum. be sure to include the very pertinent info about novell and win2k/wins. skip posting your smb.conf and just ask the how to question.

wish i could have been more help, but this was more complex than i first realized.

ps - if you would like to enlighten me further about wins, please do so. always interested, although it is used less and less.
 
  


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
Unable to unmount SMB shares reyemarr Linux - General 5 03-29-2004 02:25 AM
cant connect to smb shares murray_linux Slackware 3 02-02-2004 11:35 AM
Samba:Unable to connect shares from win2k client vikram_cvk Linux - Software 0 01-13-2004 06:03 AM
RH9 and smb shares Thaidog Linux - Newbie 1 05-07-2003 11:17 AM
Linux unable to connect to another Linux machine via Samba (SMB) Please help shassouneh Linux - Networking 4 03-11-2002 02:26 AM


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

Main Menu
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