* samba problem.
@ Shaun Oliver
` Shaun Oliver
` (4 more replies)
0 siblings, 5 replies; 16+ messages in thread
From: Shaun Oliver @ UTC (permalink / raw)
To: speakup
[-- Attachment #1: Type: TEXT/PLAIN, Size: 516 bytes --]
Hi guys.
I've tryed to set up samba to share files between my win200 and linux
machines.
I've attached a copy of my /etc/smb.conf for you to look over. My problem
is, I can't mount the other machine even after installing the smbfs module
and I can't see this machine from the other 1.
Am I doing something wrong?
Shaun..
"Has anyone ever tasted an "END"? Are they really bitter?"
EMAIL: shauno@goanna.net.au ICQ: 76958435
YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
www.jong.com:6667
[-- Attachment #2: Type: TEXT/PLAIN, Size: 8993 bytes --]
# 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 many any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: LINUX2
workgroup = workgroup
# 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.
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
; load printers = yes
# you may wish to override the location of the printcap file
; printcap name = /etc/printcap
# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
; printcap name = lpstat
# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx
; printing = bsd
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = Sam1
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba.%m
# 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. NOTE: To get the behaviour of
# Samba-1.9.18, you'll need to use "security = share".
security = user
# Use password server option only with security = server
; password server = <Sam1>
# 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
# 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 = /usr/local/samba/lib/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
# 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
# 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
# Use only if you have an NT server on your network that has been
# configured at install time to be a primary domain controller.
; domain controller = <NT-Domain-Controller-SMBName>
# 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 = Shaun
# 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
#============================ Share Definitions ==============================
[homes]
comment = Home Directories
; browseable = no
writable = yes
# 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
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 "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 = /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/home/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 = Sam's and Shaun's stuff
path = /usr/home/shared
valid users = Sam1 shauno
public = no
writable = yes
printable = no
create mask = 0765
^ permalink raw reply [flat|nested] 16+ messages in thread* Re: samba problem.
samba problem Shaun Oliver
@ ` Shaun Oliver
` Charles Hallenbeck
` (3 subsequent siblings)
4 siblings, 0 replies; 16+ messages in thread
From: Shaun Oliver @ UTC (permalink / raw)
To: speakup
that should be win2000 sorry..
Shaun..
"Has anyone ever tasted an "END"? Are they really bitter?"
EMAIL: shauno@goanna.net.au ICQ: 76958435
YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
www.jong.com:6667
On Tue, 22 May 2001, Shaun Oliver wrote:
> Hi guys.
> I've tryed to set up samba to share files between my win200 and linux
> machines.
> I've attached a copy of my /etc/smb.conf for you to look over. My problem
> is, I can't mount the other machine even after installing the smbfs module
> and I can't see this machine from the other 1.
> Am I doing something wrong?
>
>
> Shaun..
> "Has anyone ever tasted an "END"? Are they really bitter?"
> EMAIL: shauno@goanna.net.au ICQ: 76958435
> YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
> www.jong.com:6667
>
^ permalink raw reply [flat|nested] 16+ messages in thread* Re: samba problem.
samba problem Shaun Oliver
` Shaun Oliver
@ ` Charles Hallenbeck
` sambaproblem Shaun Oliver
` samba problem Kirk Wood
` (2 subsequent siblings)
4 siblings, 1 reply; 16+ messages in thread
From: Charles Hallenbeck @ UTC (permalink / raw)
To: speakup
Hi, Shaun -
On Tue, 22 May 2001, Shaun Oliver wrote:
> Hi guys.
> I've tryed to set up samba to share files between my win200 and linux
> machines.
> I've attached a copy of my /etc/smb.conf for you to look over. My problem
> is, I can't mount the other machine even after installing the smbfs module
> and I can't see this machine from the other 1.
> Am I doing something wrong?
Yes.
Visit me at http://www.mhonline.net/~chuckh
The Moon is Waning Crescent (1% of Full)
^ permalink raw reply [flat|nested] 16+ messages in thread* Re: sambaproblem.
` Charles Hallenbeck
@ ` Shaun Oliver
0 siblings, 0 replies; 16+ messages in thread
From: Shaun Oliver @ UTC (permalink / raw)
To: speakup
ok. where did I muck it up?
Shaun..
"Has anyone ever tasted an "END"? Are they really bitter?"
EMAIL: shauno@goanna.net.au ICQ: 76958435
YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
www.jong.com:6667
On Tue, 22 May 2001, Charles Hallenbeck wrote:
> Hi, Shaun -
>
> On Tue, 22 May 2001, Shaun Oliver wrote:
>
> > Hi guys.
> > I've tryed to set up samba to share files between my win200 and linux
> > machines.
> > I've attached a copy of my /etc/smb.conf for you to look over. My problem
> > is, I can't mount the other machine even after installing the smbfs module
> > and I can't see this machine from the other 1.
> > Am I doing something wrong?
>
>
> Yes.
>
>
> Visit me at http://www.mhonline.net/~chuckh
> The Moon is Waning Crescent (1% of Full)
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: samba problem.
samba problem Shaun Oliver
` Shaun Oliver
` Charles Hallenbeck
@ ` Kirk Wood
` Shaun Oliver
` Gregory Nowak
` Geoff Shang
4 siblings, 1 reply; 16+ messages in thread
From: Kirk Wood @ UTC (permalink / raw)
To: speakup
First, I am not a samba expert. But I would start with *not* leaving one
line in a section commented. If you don't like the default of what is on
the line, change the value. Whether this has any effect or not is beyond
me. One line I noticed commented out that I never left out was the
hosts-allow line. I would uncomment it and modify it accordingly.
Second, realize that the sambe server and the sambe client are only
related in that they come from the same place and work in oposite
directions. Attempting to use the samba client to troubleshoot the sambe
server is pointless. They work independantly. (The execption is that you
can use the samba client to try connecting to the sambe server on the same
machine.
Finally, don't trust Network Neighborhood. By m$ specs, not showing up
there is not a sign of malfunction. If you can run the command \\server
and a window opens it works. (I found making linux the master browser did
work better here.)
That being said, first step is to ping each of the machines. Ping by name
and ping by number. (I would also get rid of wins. It only helps in a
segmented network. Use a hosts file instead.) If you can ping then attempt
to connect. From the w2k machine attempt to run \\ipaddress. Hopefully it
will bring up a login box. (Remember simple is better.)
Finally, if you can't seem to get past the login box revisit your decision
to use encrypted passwords. Last time I played with samba there was a
couple paragraphs about getting this to work. It just seemed much easier
to modify my registry and go on with life.
=======
Kirk Wood
Cpt.Kirk@1tree.net
Nothing is hard if you know the answer or are used to doing it.
^ permalink raw reply [flat|nested] 16+ messages in thread* Re: samba problem.
` samba problem Kirk Wood
@ ` Shaun Oliver
0 siblings, 0 replies; 16+ messages in thread
From: Shaun Oliver @ UTC (permalink / raw)
To: speakup
thanks kirk.
Shaun..
"Has anyone ever tasted an "END"? Are they really bitter?"
EMAIL: shauno@goanna.net.au ICQ: 76958435
YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
www.jong.com:6667
On Tue, 22 May 2001, Kirk Wood wrote:
> First, I am not a samba expert. But I would start with *not* leaving one
> line in a section commented. If you don't like the default of what is on
> the line, change the value. Whether this has any effect or not is beyond
> me. One line I noticed commented out that I never left out was the
> hosts-allow line. I would uncomment it and modify it accordingly.
>
> Second, realize that the sambe server and the sambe client are only
> related in that they come from the same place and work in oposite
> directions. Attempting to use the samba client to troubleshoot the sambe
> server is pointless. They work independantly. (The execption is that you
> can use the samba client to try connecting to the sambe server on the same
> machine.
>
> Finally, don't trust Network Neighborhood. By m$ specs, not showing up
> there is not a sign of malfunction. If you can run the command \\server
> and a window opens it works. (I found making linux the master browser did
> work better here.)
>
> That being said, first step is to ping each of the machines. Ping by name
> and ping by number. (I would also get rid of wins. It only helps in a
> segmented network. Use a hosts file instead.) If you can ping then attempt
> to connect. From the w2k machine attempt to run \\ipaddress. Hopefully it
> will bring up a login box. (Remember simple is better.)
>
> Finally, if you can't seem to get past the login box revisit your decision
> to use encrypted passwords. Last time I played with samba there was a
> couple paragraphs about getting this to work. It just seemed much easier
> to modify my registry and go on with life.
>
> =======
> Kirk Wood
> Cpt.Kirk@1tree.net
>
> Nothing is hard if you know the answer or are used to doing it.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: samba problem.
samba problem Shaun Oliver
` (2 preceding siblings ...)
` samba problem Kirk Wood
@ ` Gregory Nowak
` Geoff Shang
4 siblings, 0 replies; 16+ messages in thread
From: Gregory Nowak @ UTC (permalink / raw)
To: speakup
Grab that samba book that Scott referred to.
I finally found it, and am slowly but shurely starting to read it.
He's right, it's great.
If you want, right me privately, and I'll send you the zip file with the pdfs which you can run through ps2ascii.
Greg
On Tue, May 22, 2001 at 09:06:14PM +1000, Shaun Oliver wrote:
> Hi guys.
> I've tryed to set up samba to share files between my win200 and linux
> machines.
> I've attached a copy of my /etc/smb.conf for you to look over. My problem
> is, I can't mount the other machine even after installing the smbfs module
> and I can't see this machine from the other 1.
> Am I doing something wrong?
>
>
> Shaun..
> "Has anyone ever tasted an "END"? Are they really bitter?"
> EMAIL: shauno@goanna.net.au ICQ: 76958435
> YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
> www.jong.com:6667
> # 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 many any basic syntactic errors.
> #
> #======================= Global Settings =====================================
> [global]
>
> # workgroup = NT-Domain-Name or Workgroup-Name, eg: LINUX2
> workgroup = workgroup
>
> # 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.
>
> # If you want to automatically load your printer list rather
> # than setting them up individually then you'll need this
> ; load printers = yes
>
> # you may wish to override the location of the printcap file
> ; printcap name = /etc/printcap
>
> # on SystemV system setting printcap name to lpstat should allow
> # you to automatically obtain a printer list from the SystemV spool
> # system
> ; printcap name = lpstat
>
> # It should not be necessary to specify the print system type unless
> # it is non-standard. Currently supported print systems include:
> # bsd, sysv, plp, lprng, aix, hpux, qnx
> ; printing = bsd
>
> # Uncomment this if you want a guest account, you must add this to /etc/passwd
> # otherwise the user "nobody" is used
> ; guest account = Sam1
>
> # this tells Samba to use a separate log file for each machine
> # that connects
> log file = /var/log/samba.%m
>
> # 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. NOTE: To get the behaviour of
> # Samba-1.9.18, you'll need to use "security = share".
> security = user
> # Use password server option only with security = server
> ; password server = <Sam1>
>
> # 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
>
> # 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 = /usr/local/samba/lib/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
>
> # 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
>
> # 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
>
> # Use only if you have an NT server on your network that has been
> # configured at install time to be a primary domain controller.
> ; domain controller = <NT-Domain-Controller-SMBName>
>
> # 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 = Shaun
>
> # 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
>
> #============================ Share Definitions ==============================
> [homes]
> comment = Home Directories
> ; browseable = no
> writable = yes
>
> # 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
> 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 "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 = /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/home/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 = Sam's and Shaun's stuff
> path = /usr/home/shared
> valid users = Sam1 shauno
> public = no
> writable = yes
> printable = no
> create mask = 0765
>
>
^ permalink raw reply [flat|nested] 16+ messages in thread* Re: samba problem.
samba problem Shaun Oliver
` (3 preceding siblings ...)
` Gregory Nowak
@ ` Geoff Shang
4 siblings, 0 replies; 16+ messages in thread
From: Geoff Shang @ UTC (permalink / raw)
To: speakup
Hi:
I realise you're going about doing a much more complicated samba setup than
I use, but it might be worth telling what I did.
I only really want to read windows shares from linux, as I have no real
need to go the other way. I just set the shares up in windows, then used
the mount command as per normal to mount it. Mount calls smbmount in order
to achieve this. The syntax for mounting smb shares is:
mount -t smbfs //host/sharename /mountpoint
The mount procedure will prompt you for the password.
So for example, I mount my primary windows drive as follows:
mount -t smbfs //picard/c /windows/c
Where picard is the name of the windows box, c is the sharename on the
windows box, and /windows/c is the mount point (this last one could just as
easily be /mnt or whatever).
Geoff.
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: samba problem.
@ awesome-dave1
0 siblings, 0 replies; 16+ messages in thread
From: awesome-dave1 @ UTC (permalink / raw)
To: speakup
Hello,
The first thing I notice is your workgroup line. Are both machines in
the same workgroup and are there ip's both in the same subnet?
Have you created the necessary unix/samba users on the unix box? Can you
log in to the unix box using smbclient with your username? If not check
that one first.
Dave.
On Tue, 22 May 2001 21:06:14 +1000 (EST) Shaun Oliver
<shauno@goanna.net.au> writes:
> Hi guys.
> I've tryed to set up samba to share files between my win200 and
> linux
> machines.
> I've attached a copy of my /etc/smb.conf for you to look over. My
> problem
> is, I can't mount the other machine even after installing the smbfs
> module
> and I can't see this machine from the other 1.
> Am I doing something wrong?
>
>
> Shaun..
> "Has anyone ever tasted an "END"? Are they really bitter?"
> EMAIL: shauno@goanna.net.au ICQ: 76958435
> YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on
> #aussiefriends on
> www.jong.com:6667
Visit my web site at:
http://www.davemehler.com
________________________________________________________________
GET INTERNET ACCESS FROM JUNO!
Juno offers FREE or PREMIUM Internet access for less!
Join Juno today! For your FREE software, visit:
http://dl.www.juno.com/get/tagj.
^ permalink raw reply [flat|nested] 16+ messages in thread
* RE: samba problem.
@ Holmes, Steve
` Shaun Oliver
0 siblings, 1 reply; 16+ messages in thread
From: Holmes, Steve @ UTC (permalink / raw)
To: 'speakup@braille.uwo.ca'
a shorter version of this is to use the smbmount command like this:
smbmount //host/sharename /mountpoint
This only works with recent kernels with smbfs and recent version of samba.
-----Original Message-----
From: Geoff Shang [mailto:gshang@uq.net.au]
Sent: Wednesday, May 23, 2001 1:23 PM
To: speakup@braille.uwo.ca
Subject: Re: samba problem.
Hi:
I realise you're going about doing a much more complicated samba setup than
I use, but it might be worth telling what I did.
I only really want to read windows shares from linux, as I have no real
need to go the other way. I just set the shares up in windows, then used
the mount command as per normal to mount it. Mount calls smbmount in order
to achieve this. The syntax for mounting smb shares is:
mount -t smbfs //host/sharename /mountpoint
The mount procedure will prompt you for the password.
So for example, I mount my primary windows drive as follows:
mount -t smbfs //picard/c /windows/c
Where picard is the name of the windows box, c is the sharename on the
windows box, and /windows/c is the mount point (this last one could just as
easily be /mnt or whatever).
Geoff.
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
^ permalink raw reply [flat|nested] 16+ messages in thread
* RE: samba problem.
Holmes, Steve
@ ` Shaun Oliver
` Stephen Dawes
0 siblings, 1 reply; 16+ messages in thread
From: Shaun Oliver @ UTC (permalink / raw)
To: 'speakup@braille.uwo.ca'
Steve and everyone else, thanks for your help with my samba problem.
I've sorted it out to a point where I can at least brows the drives on the
other machine.
Shaun..
"Has anyone ever tasted an "END"? Are they really bitter?"
EMAIL: shauno@goanna.net.au ICQ: 76958435
YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
www.jong.com:6667
On Thu, 24 May 2001, Holmes, Steve wrote:
> a shorter version of this is to use the smbmount command like this:
> smbmount //host/sharename /mountpoint
> This only works with recent kernels with smbfs and recent version of samba.
>
> -----Original Message-----
> From: Geoff Shang [mailto:gshang@uq.net.au]
> Sent: Wednesday, May 23, 2001 1:23 PM
> To: speakup@braille.uwo.ca
> Subject: Re: samba problem.
>
>
> Hi:
>
> I realise you're going about doing a much more complicated samba setup than
> I use, but it might be worth telling what I did.
>
> I only really want to read windows shares from linux, as I have no real
> need to go the other way. I just set the shares up in windows, then used
> the mount command as per normal to mount it. Mount calls smbmount in order
> to achieve this. The syntax for mounting smb shares is:
>
> mount -t smbfs //host/sharename /mountpoint
>
> The mount procedure will prompt you for the password.
>
> So for example, I mount my primary windows drive as follows:
>
> mount -t smbfs //picard/c /windows/c
>
> Where picard is the name of the windows box, c is the sharename on the
> windows box, and /windows/c is the mount point (this last one could just as
> easily be /mnt or whatever).
>
> Geoff.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
^ permalink raw reply [flat|nested] 16+ messages in thread* RE: samba problem.
` Shaun Oliver
@ ` Stephen Dawes
` Shaun Oliver
0 siblings, 1 reply; 16+ messages in thread
From: Stephen Dawes @ UTC (permalink / raw)
To: speakup
Shaun,
I don't know if anyone has suggested this to you or not, as I haven't been
following this thread all that closely.
There is a Web interface for configuration SAMBA. I don't know if it will
be useful for you or not, not knowing what you use for a browser, and
secondly, not know how visually intensive the application is.
The SAMBA Web configuration tool is called swat.
Just thought you may want to know, and maybe it will help you solve the few
final issues that it sounds like are lingering around.
Stephen Dawes B.A. B.Sc.
Web Business Office, The City of Calgary
PHONE: (403) 268-5527. FAX: (403) 268-6423
E-MAIL ADDRESS: sdawes@gov.calgary.ab.ca
> -----Original Message-----
> From: speakup-admin@braille.uwo.ca
> [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Shaun Oliver
> Sent: Thursday, May 24, 2001 8:06 AM
> To: 'speakup@braille.uwo.ca'
> Subject: RE: samba problem.
>
>
> Steve and everyone else, thanks for your help with my samba problem.
> I've sorted it out to a point where I can at least brows the drives on the
> other machine.
>
>
> Shaun..
> "Has anyone ever tasted an "END"? Are they really bitter?"
> EMAIL: shauno@goanna.net.au ICQ: 76958435
> YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
> www.jong.com:6667
>
> On Thu, 24 May 2001, Holmes, Steve wrote:
>
> > a shorter version of this is to use the smbmount command like this:
> > smbmount //host/sharename /mountpoint
> > This only works with recent kernels with smbfs and recent
> version of samba.
> >
> > -----Original Message-----
> > From: Geoff Shang [mailto:gshang@uq.net.au]
> > Sent: Wednesday, May 23, 2001 1:23 PM
> > To: speakup@braille.uwo.ca
> > Subject: Re: samba problem.
> >
> >
> > Hi:
> >
> > I realise you're going about doing a much more complicated
> samba setup than
> > I use, but it might be worth telling what I did.
> >
> > I only really want to read windows shares from linux, as I have no real
> > need to go the other way. I just set the shares up in windows,
> then used
> > the mount command as per normal to mount it. Mount calls
> smbmount in order
> > to achieve this. The syntax for mounting smb shares is:
> >
> > mount -t smbfs //host/sharename /mountpoint
> >
> > The mount procedure will prompt you for the password.
> >
> > So for example, I mount my primary windows drive as follows:
> >
> > mount -t smbfs //picard/c /windows/c
> >
> > Where picard is the name of the windows box, c is the sharename on the
> > windows box, and /windows/c is the mount point (this last one
> could just as
> > easily be /mnt or whatever).
> >
> > Geoff.
> >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
^ permalink raw reply [flat|nested] 16+ messages in thread* RE: samba problem.
` Stephen Dawes
@ ` Shaun Oliver
0 siblings, 0 replies; 16+ messages in thread
From: Shaun Oliver @ UTC (permalink / raw)
To: speakup
I think I found the problem.
the file in /usr/lib/samba/private called smbpasswd did not exist so I
created it with the smbpasswd command. If you login as root, and do
smbpasswd -a username there username is the user account you want to add
samba access to, it will then come up prompting you for a password. if
you already have a password, just type it in and it will create the
smbpasswd file in /usr/lib/samba/private.
I hope this solution helps alot of others that need it.
I've just had my partner try to access my drive as I type this email and
it worked. so there's no need for me to edit the windows registery either.
Shaun..
"Has anyone ever tasted an "END"? Are they really bitter?"
EMAIL: shauno@goanna.net.au ICQ: 76958435
YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
www.jong.com:6667
On Thu, 24 May 2001, Stephen Dawes wrote:
> Shaun,
>
> I don't know if anyone has suggested this to you or not, as I haven't been
> following this thread all that closely.
>
> There is a Web interface for configuration SAMBA. I don't know if it will
> be useful for you or not, not knowing what you use for a browser, and
> secondly, not know how visually intensive the application is.
>
> The SAMBA Web configuration tool is called swat.
>
> Just thought you may want to know, and maybe it will help you solve the few
> final issues that it sounds like are lingering around.
>
>
>
> Stephen Dawes B.A. B.Sc.
> Web Business Office, The City of Calgary
> PHONE: (403) 268-5527. FAX: (403) 268-6423
> E-MAIL ADDRESS: sdawes@gov.calgary.ab.ca
>
>
>
>
> > -----Original Message-----
> > From: speakup-admin@braille.uwo.ca
> > [mailto:speakup-admin@braille.uwo.ca]On Behalf Of Shaun Oliver
> > Sent: Thursday, May 24, 2001 8:06 AM
> > To: 'speakup@braille.uwo.ca'
> > Subject: RE: samba problem.
> >
> >
> > Steve and everyone else, thanks for your help with my samba problem.
> > I've sorted it out to a point where I can at least brows the drives on the
> > other machine.
> >
> >
> > Shaun..
> > "Has anyone ever tasted an "END"? Are they really bitter?"
> > EMAIL: shauno@goanna.net.au ICQ: 76958435
> > YAHOO ID: blindman01_2000 IRC NICK/SERVER: |3|1ndm4n on #aussiefriends on
> > www.jong.com:6667
> >
> > On Thu, 24 May 2001, Holmes, Steve wrote:
> >
> > > a shorter version of this is to use the smbmount command like this:
> > > smbmount //host/sharename /mountpoint
> > > This only works with recent kernels with smbfs and recent
> > version of samba.
> > >
> > > -----Original Message-----
> > > From: Geoff Shang [mailto:gshang@uq.net.au]
> > > Sent: Wednesday, May 23, 2001 1:23 PM
> > > To: speakup@braille.uwo.ca
> > > Subject: Re: samba problem.
> > >
> > >
> > > Hi:
> > >
> > > I realise you're going about doing a much more complicated
> > samba setup than
> > > I use, but it might be worth telling what I did.
> > >
> > > I only really want to read windows shares from linux, as I have no real
> > > need to go the other way. I just set the shares up in windows,
> > then used
> > > the mount command as per normal to mount it. Mount calls
> > smbmount in order
> > > to achieve this. The syntax for mounting smb shares is:
> > >
> > > mount -t smbfs //host/sharename /mountpoint
> > >
> > > The mount procedure will prompt you for the password.
> > >
> > > So for example, I mount my primary windows drive as follows:
> > >
> > > mount -t smbfs //picard/c /windows/c
> > >
> > > Where picard is the name of the windows box, c is the sharename on the
> > > windows box, and /windows/c is the mount point (this last one
> > could just as
> > > easily be /mnt or whatever).
> > >
> > > Geoff.
> > >
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
^ permalink raw reply [flat|nested] 16+ messages in thread
* Samba Problem
@ Luke Davis
` Keith Watson
0 siblings, 1 reply; 16+ messages in thread
From: Luke Davis @ UTC (permalink / raw)
To: Speakup
Getting an error when an smbmount is attempted. Has anyone seen this, and
what should one do about it?
smbfs: failed to load NLS 'n'
Therefore, smbmount does not work. How does one get around this problem?
Using kernel 2.4.22.
Thanks
Luke
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Samba Problem
Samba Problem Luke Davis
@ ` Keith Watson
` Luke Davis
0 siblings, 1 reply; 16+ messages in thread
From: Keith Watson @ UTC (permalink / raw)
To: speakup
Luke,
Did it work before you went to 2.4.22?
I have never seen that error and I use smbmount like everyday. I
will have to check on monday about what kernel version the beta
of fadora is using, but I do know that it is using samba 3.0 and
smbmount works fine.
Send your smbmount line so's I can take a look see.
Keith
On 09:42 PM, Luke Davis wrote:
> Getting an error when an smbmount is attempted. Has anyone seen this, and
> what should one do about it?
>
> smbfs: failed to load NLS 'n'
>
> Therefore, smbmount does not work. How does one get around this problem?
>
> Using kernel 2.4.22.
>
> Thanks
>
> Luke
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
--
Keith Watson
kwatson@smed.yi.org
Among the major impediments to discovery are not the ignorant
but those with illusions of knowledge. - B. Alan Wallace
^ permalink raw reply [flat|nested] 16+ messages in thread* Re: Samba Problem
` Keith Watson
@ ` Luke Davis
0 siblings, 0 replies; 16+ messages in thread
From: Luke Davis @ UTC (permalink / raw)
To: speakup
This was a new install, on a new system--never used it on anything below
2.4.22 on this configuration.
Of course, I have used it on other systems, on 2.4.20, with no problem.
I believe the smbmount command line was something like this:
smbmount '//system/share' ./test -o username=a_user
Also tried adding:
,charset=iso8859-1
and:
,codepage=cp850
(I could be wrong about that number--it is what ever the man page
suggests).
Luke
On Sat, 4 Oct 2003, Keith Watson wrote:
> Luke,
>
> Did it work before you went to 2.4.22?
>
> I have never seen that error and I use smbmount like everyday. I
> will have to check on monday about what kernel version the beta
> of fadora is using, but I do know that it is using samba 3.0 and
> smbmount works fine.
>
> Send your smbmount line so's I can take a look see.
>
> Keith
>
> On 09:42 PM, Luke Davis wrote:
> > Getting an error when an smbmount is attempted. Has anyone seen this, and
> > what should one do about it?
> >
> > smbfs: failed to load NLS 'n'
> >
> > Therefore, smbmount does not work. How does one get around this problem?
> >
> > Using kernel 2.4.22.
> >
> > Thanks
> >
> > Luke
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
--
Want a free month of internet access on a great ISP? Go here:
http://www.tacticus.com/net/
^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
samba problem Shaun Oliver
` Shaun Oliver
` Charles Hallenbeck
` sambaproblem Shaun Oliver
` samba problem Kirk Wood
` Shaun Oliver
` Gregory Nowak
` Geoff Shang
awesome-dave1
Holmes, Steve
` Shaun Oliver
` Stephen Dawes
` Shaun Oliver
Samba Problem Luke Davis
` Keith Watson
` Luke Davis
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).