LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 08-12-2004, 11:47 AM   #16
redhatgeek
LQ Newbie
 
Registered: Jun 2004
Distribution: redhat/fedora
Posts: 24

Rep: Reputation: 15

he wants webftp as the user not guest

i posted guest as an option using a specified user would better than allowing guest

For instance windows defaults to ntlm usually current user or guest. if the person had an unencrypted wireless router. any one close enough to get a signal could easily have free reign on that share


btw i don't think you need to create a unix user for every samba user

Code:
 smbpasswd -a webftp
should be enough

Last edited by redhatgeek; 08-12-2004 at 11:58 AM.
 
Old 08-12-2004, 05:23 PM   #17
the_agent
LQ Newbie
 
Registered: Aug 2004
Location: michigan
Distribution: redhat 9
Posts: 10

Original Poster
Rep: Reputation: 0
ok, i used smbpasswd -a and -e for webftp. i changed smb.conf to be what steiza said

Code:
smb.conf
-----------
[global]
workgroup = workgroup
server string = redhatserver
encrypt passwords = yes
security = share

[junk]
path = /var/www/html/junk/
valid users = webftp
writeable = yes
public = no
i just rebooted the system because i told it to use a different workgroup [ workgroup = workgroup, the same as my machine ]

*crosses fingers*

======================

nope. it still shows the user as being defaulted as guest, and i cant change it. i know i could just take the easy way out and make the user guest [maybe even password it] but i think it would be more beneficial to get it right. any ideas?
 
Old 08-12-2004, 05:37 PM   #18
redhatgeek
LQ Newbie
 
Registered: Jun 2004
Distribution: redhat/fedora
Posts: 24

Rep: Reputation: 15
Quote:
nope. it still shows the user as being defaulted as guest, and i cant change it. i know i could just take the easy way out and make the user guest [maybe even password it] but i think it would be more beneficial to get it right. any ideas
can't change it?...what os you running...

are you using the gui map network drive or cli net use?
 
Old 08-12-2004, 05:40 PM   #19
redhatgeek
LQ Newbie
 
Registered: Jun 2004
Distribution: redhat/fedora
Posts: 24

Rep: Reputation: 15
if you are using a NT kernel os you will have to use connect as
9x will require logging on to the pc as webftp
 
Old 08-13-2004, 03:28 PM   #20
the_agent
LQ Newbie
 
Registered: Aug 2004
Location: michigan
Distribution: redhat 9
Posts: 10

Original Poster
Rep: Reputation: 0
i'm trying to connect from a windows xp machine to the redhat 9 server. i'm going to get my smb.conf file and post anything in it that is active, perhaps something is conflicting
 
Old 08-13-2004, 06:15 PM   #21
the_agent
LQ Newbie
 
Registered: Aug 2004
Location: michigan
Distribution: redhat 9
Posts: 10

Original Poster
Rep: Reputation: 0
ok, this is kindof huge, but its my whole smb.conf file [because its probably screwing itself up somewhere - thanks for your help in advance]

Code:
# 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 = network

# server string is the equivalent of the NT Description field
;       server string = redhat server

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
;       hosts allow = 192.168.0. 127.

# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
#   printcap name = /etc/printcap
#   load printers = yes

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

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

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

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

# Security mode. Most people will want user level security. See
# security_level.txt for details.
;       security = SHARE
;-------------------------------------------------------------------
;===================================================================
;!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
        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 system password also.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
#        the encrypted SMB passwords. They allow the Unix password
#        to be kept in sync with the SMB password.
        unix password sync = Yes
        passwd program = /usr/bin/passwd %u
        passwd chat = *New*password* %n\n *Retype*new*password* %n\n 

*passwd:*all*authentication*tokens*updated*successfully*

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

        pam password change = yes

# Unix users can map to different SMB User names
;  username map = /etc/samba/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 = 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

# 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 = no
#   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
#       guest ok = yes
#       guest account = guest
#       map to guest = bad user

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


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


# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
;[printers]
;   comment = All Printers
;   path = /var/spool/samba
;   browseable = no
# Set public = yes to allow user 'guest account' to print
;   guest ok = no
;   writable = no
;   printable = yes

# This one is useful for people to share files
;[shares]
;       comment = Shares on RH9 Server
;       path = /shares
;       only guest = yes
;       writeable = no
;       printable = no
;       browseable = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
;   comment = Public Stuff

;   path = /home/samba
;   public = yes
;   writable = yes
;   printable = no
;   write list = @staff

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

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

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

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

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

[myshare]
        comment = try
        path = /home/agent
        valid users = root agent backup sol
        public = no
        browseable = no
        writable = yes
        printable = no
        guest ok = no

;bad attempt on my part, but an attempt no less
;[mapdrive]
;       comment = Junk Folder
;       path = /var/www/html/junk/
;       valid users = webftp
;       public = no
;       writable = yes
;       printable = no

        hosts allow = 192.168. 127.

;lets try this again
[global]
        workgroup = workgroup
        server string = redhatserver
        encrypt passwords = yes
        security = share

[junk]
        path = /var/www/html/junk/
        writeable = yes
        valid users = webftp
        public = no
 
Old 08-14-2004, 11:05 AM   #22
redhatgeek
LQ Newbie
 
Registered: Jun 2004
Distribution: redhat/fedora
Posts: 24

Rep: Reputation: 15
rename your smb.conf
Code:
mv smb.conf smb.conf.orig
then create a new file called smb.conf

This is all you need in the file
  • [global]
    workgroup = workgroup
    server string = redhatserver
    wins support = yes
    encrypt passwords = yes
    security = share

    [junk]
    path = /var/www/html/junk/
    writeable = yes
    valid users = webftp
    public = no
    browseable = yes
 
Old 08-14-2004, 11:07 AM   #23
redhatgeek
LQ Newbie
 
Registered: Jun 2004
Distribution: redhat/fedora
Posts: 24

Rep: Reputation: 15
make sure when you map the drive in windows you are using connect as otherwise it won't work
 
Old 08-14-2004, 03:28 PM   #24
the_agent
LQ Newbie
 
Registered: Aug 2004
Location: michigan
Distribution: redhat 9
Posts: 10

Original Poster
Rep: Reputation: 0
thanks a lot, it works now. i guess i didnt know it would only work with 'connect as' from the map network drive, i thought i'd be able to browse my way in if it would work.

arent s fun?

thanks a lot everyone. case closed!
 
Old 08-14-2004, 03:34 PM   #25
redhatgeek
LQ Newbie
 
Registered: Jun 2004
Distribution: redhat/fedora
Posts: 24

Rep: Reputation: 15
np
 
  


Reply



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
Map network Drive across WAN mattp Linux - Networking 2 11-16-2005 07:27 PM
Linux map network drive across internet Linux6574 Linux - Networking 6 04-12-2004 11:01 PM
How to map a network drive in Fedora? RCook Fedora 7 12-10-2003 10:04 AM
map network drive indy317 Linux - Networking 2 09-04-2003 04:07 PM
How do I map a network drive? MeatClown Linux - Distributions 2 08-10-2003 04:17 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 12:45 AM.

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