Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Samba on Red Hat 7.3 question

Status
Not open for further replies.

ServingSize1can

Technical User
May 21, 2002
15
0
0
US
I installed the samaba package during the install of rh7.3. I want to be able to have windows clients access my rh7.3 machine. My rh7.3 machine can be seen in network neighborhood as part of the 98 workgroup but when I doubleclick on it is says "the network path was not found". I can ping the rh7.3 machine ok and I can browse other windows machines on the same network from a windows machine. I am not running iptables or ipchains on the rh7.3 box. Here is what my smb.conf file looks like:

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

# server string is the equivalent of the NT Description field
server string = Samba 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.1. 192.168.2. 127. 169.254.

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

# 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

# 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
# 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 sytsem 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/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

# This parameter will control whether or not Samba should obey PAM's
# 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

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

# 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 = 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 ==============================
[homes]
comment = Home Directories
browseable = yes
writable = 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 = /home/agw
; browseable = yes
; 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
writable = 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 &quot;staff&quot; group
[public]
comment = Public Stuff
path = /home/agw
public = yes
writable = yes
printable = no
write list = @agw

# 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
 
What exactly did you change (if you did at all) in the conf file?

Do you belong to the same workgroup as the others?

This is the only way I know how to do it but I'm sure there are other ways:

-Open a shell prompt
-(you may have to navigate to /etc/bin or do a &quot;locate smbpasswd&quot;)
-type &quot;smbpasswd -a &quot;theSameName as the person logs into their computer with (minus the quotes)&quot;
-When prompted for a password use the same password that the user uses to log into their Windoze computer.

Do this for each user and I think you'll be all set.
 
I'm thinking you should try &quot;remote announce = x.x.x.x&quot;. Also, check out the files in /path/to/samba-version/docs/textdocs, particularly diagnosis.txt. If you don't have the docs, I believe they are available on samba's website.
 
I went ahead and created my own smb.conf file. When I run testparm it checks out ok and when I run /etc/rc.d/init.d/smb start and stop it works fine. I checked the processes and smbd and nbmd are there running. I also checked the /etc/services file and it looked ok. When I doubleclick my samba share in network neighborhood I still get &quot;the network path was not found&quot;. I checked event viewer on my Windows 2000 machine and found:

The master browser has received a server announcement from the computer ROCKETQUEEN that believes that it is the master browser for the domain on transport NetBT_Tcpip_{2FE37087-A06C-43. The master browser is stopping or an election is being forced.


rocketqueen is my redhat 7.3 machine


my smb.conf:


[global]
workgroup = 98
server string = Samba Server
os level = 65


[agw]
path = /home/agw
read only = no
guest ok = yes
comment = blah
browseable = yes


 
is rocketqueen supposed to be the master browser? if not, drop your os level down. Win98 has an OS level of 1, WinNT has 33, and W2k i dunno, but samba is probably set higher. drop samba down to 0 and retest.
 
I dropped the os level to 0 and still no success but I noticed that the windows 2k professional box was the master browser. I also added my rh7.3 linux box in the lmhosts (193.168.0.6 ROCKETQUEEN) on the windows 2k machine. On the linux box I specified the netbios name in the smb.conf file. I also ran &quot;smbclient //rocketqueen/public&quot; and was able to get to my shares. I made sure that netbios over tcpip was enabled on the windows 2000 machine. I also tried the remote announce and still no success.

After that did not work I tried to make my linux box a netbios server. I had WIN enabled int he smb.conf file and localmaster, domain master, and preferred master set to yes. I pointed the windows 2k box to use my linux box to resolve netbios names and still no success. I added a windows me machine to the workgroup 98 and was able to access the windows 2k shares and not the shares on the linux box running samba. I ran &quot;nbtstat -r&quot; on the w2k machine found that one netbios name was resolved by broadcast. I think it was because I was able to browse the windows 2k machine from the windows me machine.

3 days straight and I still cannot get it work.
 
I forgot to add that I can see the windows 2000 shares when I run &quot;smbclient 193.168.0.5&quot; from my redhat7.3 machine.
 
I ran smbmount and was able to browse the windows 2000 computer shares. But I still cannot browse the Linux machine from the Windows 2000 machine. I have the user agw with the same passwords on both windows and linux computers. I get the error message &quot;the network path was not found&quot;. I tried the net view and net use commands from the windows 2000 machine and still I can't access the linux box.

Anyhelp would be greatly appreciated

Thanks
Adam
 
Yes I did add user agw to the encrypted password file. When I ran smbclient //rocketqueen/public to myself I was able to login with agw's password so that's all setup. I cannot access the linux box (hostname = rocketqueen) from my windows 2000 client. When I click on rocketqueen in network neighborhood I get &quot;the network path was not found&quot;

Adam
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top