Re: XP and Fedora Core 3 through router - share resources?

Nico Kadel-Garcia wrote:

M. Trimble wrote:
Nico Kadel-Garcia wrote:

M. Trimble wrote:




Monkeypie was the email address of the original poster. Check the thread.
It may be that missing that kind of little detail on your part, and the
failure of someone like me to make it clear what they were talking about,
is leading to your difficulties with Samba.

Pls remind me to read carefully. [writer pulls mallet out of null-space and
whacks self on head for being a complete tardling, then returns same]

I save personal insults for people who've richly earned them: you've done
nothing of the kind. I disagree massively with you, but hope that we can
convince you by walking through your setup and finding the problem. That's
much more fun

No argument there

....
Item: Access from XP into Linux is chopped off, irrespective of
security model chosen, and further irrespective of a samba user
created specifically for the purpose

OK. Windows 2000 works and XP doesn't? Or have you compared them directly
this way?

Uh, no, just 98, over top of which I installed XP. I've never gotten a
chance to play with 2k, for a wide variety of reasons

Are the Windows XP machines already members of a domain, run by a
different controller?

Have you walked through the steps in the troubleshooting.html, available
in the Samba source tarball and which Mandriva may put somewhere odd or
leave out?

As near as I can tell, Mandriva did nothing obtuse. I can report, that
mandr* 9.1 worked sorta, then I installed 10.1 over, and that's when I
started having problems. I suppose it's reasonable to guess that there was
some really obscure change from 9.1 to 10.1, one that didn't show up in the
man pages, because I set up 10.1 identical to 9.1

Item: XP freezes solid, doesn't even respond to a 'three-fingered
salute' after printing from linux to windows. I assumed
virus/trojan/other malware on one box or another, except for one
minor detail: I run both hardware based (router) and software base
(Zonealarm) firewall; I run antivirus in real-time, which I update
not less than 2x/week; I run mal-ware detectors in real-time (Spybot,
in case you're curious), and I just finished running a complete virus
and security sweep using Symantec's online tools and using my own
tools.

Interesting. Note that virus detectors are generally re-active, not
pro-active: They get updated after the virus is in the wild. But yes, I'd
certainly be concerned about that.

Hmm.

Item: the last time I set things up, I was running Mandriva 10.1, and
Win 98, and had to go in and manually edit smb.conf to get access
from win into lin, and never did get access from lin into win.

Welcome to Mandrake^H^H^HMandriva, sometimes known as
Mandriva-you-instane. Seriously.

More like, good-bye mandriva, hello FC5. I just wish I had mp3 support, the
hardware support is far superior.

What did you have to change? Post your smb.conf if you need help with it,
and in particular look at the

Now I'm under FC5, and I have more or less exactly the same trouble,
after setting up exactly as the documentation and commentary say it
should.

You tell me.

Post your smb.conf, please! And let us know more about your setup. Is it
just one Linux box and one Windows box? Are there any actual other domain
controllers in your setup?

OK, here goes. Let's hope this asciibetical art doesn't go out of kilter.

|-linux box, running fc5, named rivendell
-cable modem ---- router ----
|-winxp box, named numenor

both boxen obtain their ip address from the router, which in turn is the
default gateway/nameserver, etc.

smb.conf file as follows:
<blockquote>

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

# 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
printcap name = /etc/printcap

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

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

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

# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m.log
# all log information in one file
# log file = /var/log/samba/log.smbd

# 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
; password server = <NT-Server-Name>

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

# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
; encrypt passwords = yes
; smb passwd file = /etc/samba/smbpasswd

# The following are needed to allow password changing from Windows to
# update the Linux system password also.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
# the encrypted SMB passwords. They allow the Unix password
# to be kept in sync with the SMB password.
; unix password sync = Yes
; passwd program = /usr/bin/passwd %u
; passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n
*passwd:*all*authentication*tokens*updated*successfully*

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

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /etc/samba/smb.conf.%m

# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
socket options = TCP_NODELAY SO_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 = 192.168.12.2/24 192.168.13.2/24

# Configure remote browse list synchronisation here
# request announcement to, or browse list sync from:
# a specific host or from / to a whole subnet (see below)
; remote browse sync = 192.168.3.25 192.168.5.255
# Cause this host to announce itself to local subnets here
; remote announce = 192.168.1.255 192.168.2.44

# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33

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

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

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

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat

# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U

# All NetBIOS names must be resolved to IP Addresses
# 'Name Resolve Order' allows the named resolution mechanism to be specified
# the default order is "host lmhosts wins bcast". "host" means use the unix
# system gethostbyname() function call that will use either /etc/hosts OR
# DNS or NIS depending on the settings
of /etc/host.config, /etc/nsswitch.conf
# and the /etc/resolv.conf file. "host" therefore is system configuration
# dependant. This parameter is most often of use to prevent DNS lookups
# in order to resolve NetBIOS names to IP Addresses. Use with care!
# The example below excludes use of name resolution for machines that are
NOT
# on the local network segment
# - OR - are not deliberately to be known via lmhosts or via WINS.
; name resolve order = wins lmhosts bcast

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS
Server
; wins support = yes

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
dns proxy = no
username map = /etc/samba/smbusers
encrypt passwords = no
; security = user
restrict anonymous = no
domain master = no
preferred master = no
netbios name = rivendell
max protocol = NT
ldap ssl = No
server signing = Auto
; security = user
; guest ok = no
; guest account = nobody
; security = user
; guest ok = no
; guest account = nobody
; guest ok = no
; guest account = nobody
; guest ok = no
; guest account = nobody

# 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

# Un-comment the following and create the netlogon directory for Domain
Logons
; [netlogon]
; comment = Network Logon Service
; path = /home/netlogon
; guest ok = yes
; writable = no
; share modes = no


# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /home/profiles
; browseable = no
; guest ok = yes


# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
; guest ok = no
; writeable = 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
; read only = yes
; write list = @staff

# Other examples.
#
# A private printer, usable only by fred. Spool data will be placed in
fred's
# home directory. Note that fred must have write access to the spool
directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes

# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %u option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes

# A publicly accessible directory, read/write to all users. Note that all
files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of
course
# be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In
this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765


[met12327]
path = /home/met12327/
writeable = yes
guest ok = yes
browseable = yes

</blockquote>

It's been a couple of years since I made the hand chnages in mandr* 9.1, but
if memory serves, I believe I had to set up some goofy mapping within the
hosts.allow section. I do recall that I had to set it up so that Samba
would allow connection from all ip in a given range/subnet mask. Beyond
that, I don't remember the details.

If you can help, I'd be grateful.

M
.

Relevant Pages

  • Re: XP and Fedora Core 3 through router - share resources?
    ... Samba has a huge number of configurable options (perhaps too ... server string = Samba Server ... # set local master to no if you don't want Samba to become a master ... # per user logon script ...
    (comp.os.linux.setup)
  • Re: XP and Fedora Core 3 through router - share resources?
    ... Samba has a huge number of configurable options (perhaps too ... server string = Samba Server ... # set local master to no if you don't want Samba to become a master ... # per user logon script ...
    (comp.os.linux.setup)
  • Re: Help for Samba configuration
    ... Samba has a huge number of configurable options (perhaps too ... # server string is the equivalent of the NT Description field ... # Log File let you specify where to put logs and how to split them up. ... # Domain Logons let Samba be a domain logon server for Windows workstations. ...
    (Fedora)
  • Re: Help for Samba configuration
    ... Samba has a huge number of configurable options (perhaps too ... # server string is the equivalent of the NT Description field ... # Log File let you specify where to put logs and how to split them up. ... # Domain Logons let Samba be a domain logon server for Windows workstations. ...
    (Fedora)
  • Re: Samba Problem
    ... samba configuration file, ... server string = Samba Server ... # set local master to no if you don't want Samba to become a master ... # per user logon script ...
    (freebsd-questions)