Go Job Hunting at the LQ Job Marketplace
Go Back > Forums > Linux Forums > Linux - Software
User Name
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.


Search this Thread
Old 01-23-2005, 11:52 AM   #1
Registered: Jul 2004
Location: The Netherlands
Distribution: Mandrake, Knoppix, Coyote Linux, RedHat
Posts: 354
Blog Entries: 3

Rep: Reputation: 31
Samba does not allow writing to public shares / browsing home directories disallowed


I'm sure this topic has been chewed on before but after some trawling through all the relevant hits from searching LQ I couldn't find anything that made sense for my situation..

I need some help getting Samba to behave according to my wishes..
My problem is that although I have Samba running, and I can actually access (some) of the shares, further access is denied (no login dialog is ever presented), and the machine is not detected in a Windows XP network neighborhood browse. I have to type out \\ to get the machine to show up in Windows XP, and then I can see the public shares.

The machine that runs Samba, is installed with Mandrake 10.0 Official Powerpack, the box is registered and has (as far as I could tell) received any remaining updates for this particular version of MDK.
It was installed with the 'Paranoid' security option selected, with Root as the security administrator. I have since today, lowered the security levels to 'Higher', and through the KDE Samba admin disabled 'Paranoid server security' on the Samba service.
Reason for the paranoid level was so I would get the secure kernel, because this box is going to be opened up to the Internet on a 24/7 basis, with as little worry for security maintenance as possible.

The shared objects have been left on their defaults for the most part, and I added two more shares to Samba. namely:

#1. /var/ftp as ftp_root
#2. /var/www as apache_root

Both respectively reside on their very own hdd, which are completely empty as of yet (since I can't write to them yet)

What I need to solve is:
#1. Get write access permission to ftp_root and apache_root. I can see how this relates to the machine's security levels, and the permissions set on their respective directories, but the point I ask is if anyone has any tips on a decent set of permissions, i'll gladly hear them
#2. Login-free access to the Samba shares, including some select home directories. Perhaps I could accomplish this through username mapping, but I have already created all the required accounts for both the windows clients and the server, and changing them would be much hassle, which i'd rather avoid...
#3. Get the machine to appear properly in the Windows workgroup. I believe I have set all relevant options to add the machine to the workgroup, but if anyone could list -all- of the things I should have set, perhaps I can see what I missed?

I will dig out the smb.conf file and post it here shortly.

Thank you for your time.
Old 01-24-2005, 06:43 PM   #2
Senior Member
Registered: Oct 2003
Location: Bonaire
Distribution: Debian Lenny/Squeeze/Wheezy/Sid
Posts: 4,067

Rep: Reputation: 491Reputation: 491Reputation: 491Reputation: 491Reputation: 491

What does your /etc/samba/smb.conf look like?

You need to add a samba user for anyone who has to access a samba share. That is, if your name on the XP box is xp_user, then the samba box should *know* xp_user. In other words, xp_user should exist on your Linux box. (I guess you did not aim for more complicated things like having the Linux box acting as a Windows PDC.)

If you have done so, in smb.conf you have to define each share (that is, which directory you want to have visible and mappable to Win clients) and for each share you have to provide a list with users which are allowed to brows/read/write the directories.

Take a look at this exellent document:

Old 01-25-2005, 07:07 AM   #3
Registered: Jul 2004
Location: The Netherlands
Distribution: Mandrake, Knoppix, Coyote Linux, RedHat
Posts: 354
Blog Entries: 3

Original Poster
Rep: Reputation: 31
I'll post my smb.conf file as soon as I get home from work.
On the server I created different users for different purposes (all of which I also added as Samba users), but disregarding any usernames that exist on the Windows machines. it is only a small network, therefore I saw no benefit of going through the trouble of creating a Samba PDC, I merely want a secure machine that drives a handful of public services and acts as a file repository. but what I don't want is, what it is doing now. nothing. I expected a login prompt on the folders belonging to the users I created on the server, but instead I am denied access without a chance to fill in any credentials. it'll be clearer talking when I get the smb.conf file up here, so i'll leave it at that.
Funny thing is, if I fire up Knoppix and start Samba, I have no problems. I can access the Knoppix Samba server without having to dive into smb.conf with vi to tweak around and map any usernames to the Windows usernames or do anything about permissions. it is kind of unnerving. I know it has to be simpler than that and actually, the smb.conf file in Knoppix has far less options in it than my smb.conf from my server... which puzzles me as to why there are so many options, and which are actually relevant to the goals I am trying to reach.

Thank you for the link, that is some good literature. I will keep it in print and read it through, it may give me some insight as to the many options available in Samba.
Old 01-25-2005, 08:58 AM   #4
LQ Newbie
Registered: Jan 2005
Distribution: fedora core 2
Posts: 2

Rep: Reputation: 0
Make sure shared samba drive is not root owned

I had a similiar problem when I first brought samba up. I had to do a chgrp & chown on the shared samba drive to be nobody, this all depends upon who you are allowing to access the samba share though. I let all users on my network to access the drive so this is working for me. When I get a braver I will try to limit certain directories to certain users.
Old 01-25-2005, 10:24 AM   #5
Registered: May 2002
Location: Argentina
Distribution: Mandrake 9.2
Posts: 177

Rep: Reputation: 30
security = share

and add at the directories you wish write

writable = yes

If you want to write from windoze add the following lines to the same directories

guest only = yes
browseable - yes
guest ok = yes

let me know if its works
Old 02-14-2005, 04:17 PM   #6
Registered: Jul 2004
Location: The Netherlands
Distribution: Mandrake, Knoppix, Coyote Linux, RedHat
Posts: 354
Blog Entries: 3

Original Poster
Rep: Reputation: 31
Right.. i'm finally back, I had to deal with some delicate personal business which kept me from getting back to you guys.
Here is the smb.conf file I promised to post:

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

# 1. Server Naming Options:
# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = XARANE

# netbios name is the name you will see in "Network Neighbourhood",
# but defaults to your hostname
#  netbios name = <name_of_this_server>

# server string is the equivalent of the NT Description field
server string = Xolo's Peak - Samba v%v

# Message command is run by samba when a "popup" message is sent to it.
# The example below is for use with LinPopUp:
; message command = /usr/bin/linpopup "%f" "%m" %s; rm %s

# 2. Printing Options:
# (as cups is now used in linux-mandrake 7.2 by default)
# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
printcap name = cups

# 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

# Samba 2.2 supports the Windows NT-style point-and-print feature. To
# use this, you need to be able to upload print drivers to the samba
# server. The printer admins (or root) may install drivers onto samba.
# Note that this feature uses the print$ share, so you will need to
# enable it below.
# printer admin = @<group> <user>
printer admin = @adm
# This should work well for winbind:
#   printer admin = @"Domain Admins"

# 3. Logging Options:
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m

# Put a capping on the size of the log files (in Kb).
max log size = 50

# Set the log (verbosity) level (0 <= log level <= 10)
# log level = 3

# 4. Security and Domain Membership Options:
# 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. Do not enable this if (tcp/ip) name resolution does
# not work for all the hosts in your network.
#   hosts allow = 192.168.1. 192.168.2. 127.

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
#  guest account = pcguest
# Allow users to map to guest:
map to guest = Bad User

# Security mode. Most people will want user level security. See
# security_level.txt for details.
security = share
# Use password server option only with security = server or security = domain
# When using security = domain, you should use password server = *
#   password server = <NT-Server-Name>
#   password server = *

# 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
# Encrypted passwords are required for any use of samba in a Windows NT domain
# The smbpasswd file is only required by a server doing authentication, thus
# members of a domain do not need one.
encrypt passwords = yes

# The following are needed to allow password changing from Windows to
# also update the Linux system password.
# 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
# You either need to setup a passwd program and passwd chat, or
# enable pam password change
;  pam password change = yes
#  passwd program = /usr/bin/passwd '%u'
;  passwd chat = *New*UNIX*password* %n\n *Re*ype*new*UNIX*password* %n\n \

# 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

# Options for using winbind. Winbind allows you to do all account and
# authentication from a Windows or samba domain controller, creating
# accounts on the fly, and maintaining a mapping of Windows RIDs to unix uid's
# and gid's. winbind uid and winbind gid are the only required parameters.
# winbind uid is the range of uid's winbind can use when mapping RIDs to uid's
#  idmap uid = 10000-20000
# winbind gid is the range of uid's winbind can use when mapping RIDs to gid's
#  idmap gid = 10000-20000
# winbind separator is the character a user must use between their domain
# name and username, defaults to "\"
#  winbind separator = +
# winbind use default domain allows you to have winbind return usernames
# in the form user instead of DOMAIN+user for the domain listed in the
# workgroup parameter.
#  winbind use default domain = yes
# template homedir determines the home directory for winbind users, with
# %D expanding to their domain name and %U expanding to their username:
#  template homedir = /home/%D/%U

# When using winbind, you may want to have samba create home directories
# on the fly for authenticated users. Ensure that /etc/pam.d/samba is
# using 'service=system-auth-winbind' in pam_stack modules, and then
# enable obedience of pam restrictions below:
#  obey pam restrictions = yes

# template shell determines the shell users authenticated by winbind get
#  template shell = /bin/bash

# 5. Browser Control and Networking Options:
# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=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 =

# 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 =
# Cause this host to announce itself to local subnets here
#   remote announce =

# 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

# 6. Domain Control Options:
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations or Primary Domain Controller for WinNT and Win2k
#   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 roaming profiles for WinNT and Win2k
#        %L substitutes for this servers netbios name, %u is username
#        You must uncomment the [Profiles] share below
#   logon path = \\%L\Profiles\%u

# Where to store roaming profiles for Win9x. Be careful with this as it also
# impacts where Win2k finds it's /HOME share
# logon home = \\%L\%u\.profile

# The add user script is used by a domain member to add local user accounts
# that have been authenticated by the domain controller, or when adding
# users via the Windows NT Tools (ie User Manager for Domains).

# Scripts for file (passwd, smbpasswd) backend:
# add user script = /usr/sbin/useradd -s /bin/false '%u'
# delete user script = /usr/sbin/userdel '%s'
# add user to group script = /usr/bin/gpasswd -a '%u' '%g'
# delete user from group script = /usr/bin/gpasswd -d '%u' '%g'
# set primary group script = /usr/sbin/usermod -g '%g' '%u'
# add group script = /usr/sbin/groupadd %g && getent group '%g'|awk -F: '{print $3}'
# delete group script = /usr/sbin/groupdel '%g'

# Scripts for LDAP backend (assumes nss_ldap is in use on the domain controller,
# and needs configuration in
# add user script = /usr/share/samba/scripts/ '%u'
# delete user script = /usr/share/samba/scripts/ '%u'
# add user to group script = /usr/share/samba/scripts/ -m '%u' '%g'
# delete user from group script = /usr/share/samba/scripts/ -x '%u' '%g'
# set primary group script = /usr/share/samba/scripts/ -g '%g' '%u'
# add group script = /usr/share/samba/scripts/ '%g' && /usr/share/samba/scripts/ %g|awk '/^gidNumber:/ {print $2}'
# delete group script = /usr/share/samba/scripts/ '%g'

# The add machine script is use by a samba server configured as a domain
# controller to add local machine accounts when adding machines to the domain.
# The script must work from the command line when replacing the macros,
# or the operation will fail. Check that groups exist if forcing a group.
# Script for domain controller for adding machines:
# add machine script = /usr/sbin/useradd -d /dev/null -g machines -c 'Machine Account' -s /bin/false -M '%u'
# Script for domain controller with LDAP backend for adding machines (please
# configure in /etc/samba/ first):
# add machine script = /usr/share/samba/scripts/ -w -d /dev/null -g machines -c 'Machine Account' -s /bin/false '%u'

# Domain groups:
# Domain groups are now configured by using the 'net groupmap' tool

# Samba Password Database configuration:
# Samba now has runtime-configurable password database backends. Multiple
# passdb backends may be used, but users will only be added to the first one
# Default:
# passdb backend = smbpasswd guest
# TDB backen with fallback to smbpasswd and guest
# passdb backend = tdbsam smbpasswd guest
# LDAP with fallback to smbpasswd guest
# Enable SSL by using an ldaps url, or enable tls with 'ldap ssl' below.
# passdb backend = ldapsam:ldaps:// smbpasswd guest
# Use the samba2 LDAP schema:
# passdb backend = ldapsam_compat:ldaps:// smbpasswd guest

# Idmap settings (set idmap uid and idmap gid above):
# Idmap backend to use:
# idmap backend = ldap:ldap://

# LDAP configuration for Domain Controlling:
# The account (dn) that samba uses to access the LDAP server
# This account needs to have write access to the LDAP tree
# You will need to give samba the password for this dn, by
# running 'smbpasswd -w mypassword'
# ldap admin dn = cn=root,dc=mydomain,dc=com
# ldap ssl = start_tls
# start_tls should run on 389, but samba defaults incorrectly to 636
# ldap port = 389
# ldap suffix = dc=mydomain,dc=com
# Seperate suffixes are available for machines, users, groups, and idmap, if
# ldap suffix appears first, it is appended to the specific suffix.
# Example for a unix-ish directory layout:
# ldap machine suffix = ou=Hosts
# ldap user suffix = ou=People
# ldap group suffix = ou=Group
# ldap idmap suffix = ou=Idmap
# Example for AD-ish layout:
# ldap machine suffix = cn=Computers
# ldap user suffix = cn=Users
# ldap group suffix = cn=Groups
# ldap idmap suffix = cn=Idmap

# 7. Name Resolution Options:
# 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
restrict anonymous = no
domain master = no
preferred master = no
max protocol = NT
ldap ssl = No
server signing = Auto
case sensitive = no
msdfs proxy = no
paranoid server security = no
winbind enable local accounts = yes
netbios aliases = xolo
nis homedir = yes

# 8. File Naming Options:
# 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

# Enabling internationalization:
# you can match a Windows code page with a UNIX character set.
# Windows: 437 (US), 737 (GREEK), 850 (Latin1 - Western European),
# 852 (Eastern Eu.), 861 (Icelandic), 932 (Cyrillic - Russian),
# 936 (Japanese - Shift-JIS), 936 (Simpl. Chinese), 949 (Korean Hangul),
# 950 (Trad. Chin.).
# UNIX: ISO8859-1 (Western European), ISO8859-2 (Eastern Eu.),
# ISO8859-5 (Russian Cyrillic), KOI8-R (Alt-Russ. Cyril.)
# This is an example for french users:
#   dos charset = 850
#   unix charset = ISO8859-1

#============================ Share Definitions ==============================
comment = Home Directories
read only = no
guest ok = yes
# You can enable VFS recycle bin and on-access virus-scanning on a per
# share basis:
# Uncomment the next 2 lines (make sure you create a .recycle folder in
# the base of the share and ensure all users will have write access to it.
# For virus scanning, install samba-vscan-clamav and ensure the clamd service
# is running
#   vfs objects = vscan-clamav recycle
#   vscan-clamav: config-file = /etc/samba/vscan-clamav.conf

# Un-comment the following and create the netlogon directory for Domain Logons
# [netlogon]
#   comment = Network Logon Service
#   path = /var/lib/samba/netlogon
#   guest ok = yes
#   writable = no

#Uncomment the following 2 lines if you would like your login scripts to
#be created dynamically by ntlogon (check that you have it in the correct
#location (the default of the ntlogon rpm available in contribs)
#root preexec = /usr/bin/ntlogon -u '%u' -g '%g' -o %a -d /var/lib/samba/netlogon/
#root postexec = rm -f '/var/lib/samba/netlogon/%u.bat'

# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
#    path = /var/lib/samba/profiles
#    browseable = no
#    guest ok = yes
#    writable = yes
# This script can be enabled to create profile directories on the fly
# You may want to turn off guest acces if you enable this, as it
# hasn't been thoroughly tested.
#root preexec = PROFILE='/var/lib/samba/profiles/%u'; if [ ! -e $PROFILE ]; \
#                then mkdir -pm700 $PROFILE; chown '%u':'%g' $PROFILE;fi
# If you want read-only profiles, fake permissions so windows clients think
# they have written to the files
# vfs objects = fake_perms

# NOTE: If you have a CUPS print system there is no need to
# specifically define each individual printer.
# You must configure the samba printers with the appropriate Windows
# drivers on your Windows clients or upload the printer driver to the
# server from Windows (NT/2000/XP). On the Samba server no filtering is
# done. If you wish that the server provides the driver and the clients
# send PostScript ("Generic PostScript Printer" under Windows), you have
# to use 'printcap name = cups' or swap the 'print command' line below
# with the commented one. Note that print commands only work if not using
# 'printing=cups'
comment = All Printers
path = /var/spool/samba
# to allow user 'guest account' to print.
guest ok = yes
printable = yes
create mask = 0700
# =====================================
# print command: see above for details.
# =====================================
print command = lpr-cups -P %p -o raw %s -r   # using client side printer drivers.
#   print command = lpr-cups -P %p %s # using cups own drivers (use generic PostScript on clients).
# If you install drivers on the server, you will want to uncomment this so
# clients request the driver
use client driver = yes

# This share is used for Windows NT-style point-and-print support.
# To be able to install drivers, you need to be either root, or listed
# in the printer admin parameter above. Note that you also need write access
# to the directory and share definition to be able to upload the drivers.
# For more information on this, please see the Printing Support Section of
# /usr/share/doc/samba-<version>/docs/Samba-HOWTO-Collection.pdf
# A special case is using the CUPS Windows Postscript driver, which allows
# all features available via CUPS on the client, by publishing the ppd file
# and the cups driver by using the 'cupsaddsmb' tool. This requires the
# installation of the CUPS driver (
# on the server, but doesn't require you to use Windows at all :-).
path = /var/lib/samba/printers
write list = @adm root
guest ok = yes
inherit permissions = yes
# Settings suitable for Winbind:
# write list = @"Domain Admins" root
# force group = +@"Domain Admins"

# A useful application of samba is to make a PDF-generation service
# To streamline this, install windows postscript drivers (preferably colour)
# on the samba server, so that clients can automatically install them.
# Note that this only works if 'printing' is *not* set to 'cups'

path = /var/tmp
printable = Yes
comment = PDF Generator (only valid users)
printing = bsd
#print command = /usr/share/samba/scripts/print-pdf file path win_path recipient IP &
print command = /usr/share/samba/scripts/print-pdf "%s" "%H" "//%L/%u" "%m" "%I" "%J" &
lpq command = /bin/true
guest ok = yes

hide dot files = no
guest ok = yes
read only = no
comment = ProFTPd Root
path = /var/ftp/

hide dot files = no
guest ok = yes
read only = no
comment = Apache Root
path = /var/www/

As you can see itīs very long and I donīt fully understand the context and meaning of each entry in this -very-
detailed configuration... my only real goal is to have the ability to add shares as I please, that can be viewed
and written to at leasure without actually requiring a login before something becomes visible and/or writeable.
Samba wonīt be publicly available on my server, I merely want my machine to show up in a Windows based
LAN (Network Neighborhood) and be browseable/writeable.
Two shares that are important to me to have are /var/www and /var/ftp, as these are the main two services I
want to use later on.
I've changed the machineīs security level to a lower setting, namely 'Higher', instead of 'Paranoid'.
I have noticed that Samba is still in Paranoid mode, which might be inconveniant.
Either way.. since iīve been kept busy the past two months I havenīt tinkered with this at all and even
managed to lose my notes. iīd appreciate a little help getting back on track, thanks in advance

Have a good day.
Old 02-14-2005, 04:22 PM   #7
Registered: Jul 2004
Location: The Netherlands
Distribution: Mandrake, Knoppix, Coyote Linux, RedHat
Posts: 354
Blog Entries: 3

Original Poster
Rep: Reputation: 31
Plus what I forgot to mention, is iīve been using KcmSambaConf, a KControl module, to change the
settings for the Samba server. I donīt know whether or not this will make any difference for the change
in settings or not, thought Iīd mention it either way.

Have a nice day.


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
win xp home edition and samba home shares scheidel21 Linux - Software 8 10-09-2008 12:47 AM
Browsing Samba shares - slow :( MikeScott Linux - Software 5 06-08-2005 07:41 AM
Browsing shares in samba slow? kleptophobiac Linux - Software 7 08-07-2004 09:57 AM
Browsing administrative shares within a samba domain elements Linux - Software 0 01-02-2004 03:43 PM
Why can't I see the files in the directories on my Samba-Shares? Asuka Tabi Linux - Software 1 06-21-2001 01:10 PM

All times are GMT -5. The time now is 06:19 AM.

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