I believe that I have my samba setup correctly. I have samba users that are the same as my linux users. I also have my smb.conf file set correctly. My only problem now is that when i start the smb service and then try and click on the computer icon that is in my windows network neighborhood I get a network path not found error I had to change my host name from localhost.localdomain to a new hostname. Now I have read in other samba posts that to things have to be started inorder for samba to work correctly, smb and nmbd. Am I right? Every time I have started Samba before I have never started the nmbd service. Is this my problem. If so how do I start the nmbd service?
thanks for the help
pepper
Sledge1954
08-15-2002, 03:53 AM
Go here:
Samba How To... (http://de.samba.org/samba/ftp/docs/htmldocs/Samba-HOWTO-Collection.html#AEN80)
pepper
08-15-2002, 04:45 AM
I just looked in the samba how-to file it says to put two lines of code into the /etc/inetd.conf file. However when I opened emacs to edit that file, emacs told me that it was a new file. I have found a file that is close to that. The name of the file is xinetd.conf do put those lines of code in that file? I am running Red Hat Linux 7.3
Thanks,
Pepper
baz2
08-15-2002, 09:05 AM
Yes, on RH xinetd takes the place of inetd.
But I don't understand why you should have to do this. I have set up Samba on RH on numerous systems without doing this. Let's back up for a minute.
On RH, to start Samba, all you need to do is use the GUI service configuration tool (has a gear icon, kind of imitating Windows). Locate the check box for Samba in the list that is shown and make sure it is checked. If not, check it, and then click both "Save" and "Start." If you don't click "Save" it will not start automatically each time Linux starts. That should start both of the Samba daemons (smbd and nmbd). Should be no need to mess with xinetd for Samba.
If you can see your linux box in Windows' Network Neighborhood, then the error you are getting is puzzling, to me at least. You should either get in to your home shares -- if you are logged on to Windows using the same username and password of a samba account on the linux box -- or prompted for a username and password.
What is the Windows workstation running? I've done this only with NT and 2000. I would not expect a problem with XP Pro, but wouldn't be surprised if there was a problem using XP Home (though I'm not suggesting there should be one).
Can you ping the Linux box by name from Windows? I should think so, if you can see it in Network Neighborhood. But I would check.
You've changed the "Workgroup=" line in smb.conf to the same as your Windows network or domain, right? If not, that could be the problem. Relatedly, is your network a simple workgroup, NT domain, or Windows 2000 domain? I've only done this with the first two. I could imagine some problems with Windows 2000 domains if the localhost.localdomain name is not properly configured. For a workgroup or NT domain, "localhost.localdomain" should be just the name of the linux computer.
Assuming smb.conf is configured correctly, the next thing I would check are the network configurations for the linux box. Really, with RH configuring Samba for basic connectivity is very simple. It takes only one change to the smb.conf file -- changing the "workgroup=" directive to point to the Windows workgroup or domain you want the machine to be on. And starting smb is just as easy using the GUI tool as described above.
When I teach this stuff (been doing so for about a year now) the area where my students usually have trouble is with creating samba accounts and passwords, or with their basic network configuration. The steps to convert the linux accounts to samba accounts and create samba passwords are clearly spelled out in Chapter 11 of the RH "Configuration Guide" so it is just a matter of doing that carefully. While webmin is nice for this, I insist that students do it manually so they understand what is going on.
The other area of common problems getting the network info correctly configured, especially to replace the localhost.localdomain host name. Using the RH GUI network configuration tool, this has to be done on two tabs (don't remember for sure which two -- hosts for sure, and then one other). But if your linux box is booting up with a unique name, then you probably have this covered.
pepper
08-15-2002, 08:47 PM
First off I now have the samba service loading at boot time. Next, when linux is running the two computers that are on my network have windows XP running. One of them is the professional version and the other has the home version running. I have just a simple workgroup network setup. When I try to ping the linux machine's windows name from both operating systems and I get the network path not found error. Can someone please tell me what I am doing wrong. I have changed the hostname of the system and of the IP 127.0.0.1. I also checked to see if I can see the network from my linux box, I can. The version of samba that I am running is 2.2.5.
My samba users are not the same as my windows user names. The reason for this is because I have different user names on each computer. What I think should happen is that a username/passwd dialog box should come up. Am I right?
If you would like to see my smb.conf file or any other file that has to do with samba let me know and I will post it.
cowanrl
08-15-2002, 10:00 PM
If you want to test connectivity between your XP computer and your Samba server at the command line, try this command on your XP Pro machine:
net view \\sambaservername
Use the name of your Samba server. That should show you a list of all the shares available on your Samba server if it's working OK.
That would be a better test for Samba connectivity than ping. Ping would just test that TCP/IP is working. net view will test that Samba is working.
The fact that the error message you are getting with your ping command is "network path not found" indicates to me there is still a problem with your Samba setup.
Sledge1954
08-15-2002, 10:07 PM
Capture a packet trace in Ethereal on the Linux box when you test your setup. It should point you in the proper direction by showing you the negotiation between the two boxes.
It sure beats poking it with a stick till it works.
baz2
08-15-2002, 11:23 PM
Originally posted by pepper
First off I now have the samba service loading at boot time. Next, when linux is running the two computers that are on my network have windows XP running. One of them is the professional version and the other has the home version running. I have just a simple workgroup network setup. When I try to ping the linux machine's windows name from both operating systems and I get the network path not found error. Can someone please tell me what I am doing wrong. I have changed the hostname of the system and of the IP 127.0.0.1. I also checked to see if I can see the network from my linux box, I can. The version of samba that I am running is 2.2.5.
Well, if you cannot ping by name, then NetBIOS name resolution is not working on the Linux box. That means that nmbd is not running, or is improperly configured. Did you mention in another thread that you had mucked around with xinetd? You could have messed something up doing that.
As for the network configuration, I'm still not sure you have that down correctly. You should not have changed the name assigned to 127.0.0.1. This should stay "localhost." This is the loopback address, and many programs expect "localhost" to be mapped to 127.0.0.1.
My samba users are not the same as my windows user names. The reason for this is because I have different user names on each computer. What I think should happen is that a username/passwd dialog box should come up. Am I right?
That's right.
If you would like to see my smb.conf file or any other file that has to do with samba let me know and I will post it.
I am going to post the default RH smb.conf file in a separate reply. You can compare it to yours. There is only one line that you need to change for it to work (the WORKGROUP= line).
baz2
08-15-2002, 11:29 PM
#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 = YOURWORKGROUPNAMEHERE
# server string is the equivalent of the NT Description field
server string = Apache-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
load printers = yes
# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx
printing = lprng
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m.log
# Put a capping on the size of the log files (in Kb).
max log size = 0
# Security mode. Most people will want user level security. See
# security_level.txt for details.
security = user
# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password server = *
; password server = <NT-Server-Name>
# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
; password level = 8
; username level = 8
# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
# The following is needed to keep smbclient from spouting spurious errors
# when Samba is built with support for SSL.
; ssl CA certFile = /usr/share/ssl/certs/ca-bundle.crt
# The following are needed to allow password changing from Windows to
# update the Linux sytsem password also.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
# the encrypted SMB passwords. They allow the Unix password
# to be kept in sync with the SMB password.
; unix password sync = Yes
; passwd program = /usr/bin/passwd %u
; passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*success fully*
# 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
; 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
;[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 = /home/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
#File too long....continue in next post
baz2
08-15-2002, 11:32 PM
#the rest of the file
# 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
pepper
08-15-2002, 11:54 PM
I have reinstalled redhat a few times so I am not sure if I screwed with the xinetd file. I am pretty sure that I haven't. But to be sure I am including it in this post.
#
# Simple configuration file for xinetd
#
# Some defaults, and include /etc/xinetd.d/
while I was looking for this file I also spotted a yp.conf file. I think this is for domains however I just looked at the contents of the file, one of the lines in there is ypserver = HOSTNAME. does this have to be used if I am using a simple network.
How do I reconfigure the nmbd service?
pparks
08-16-2002, 03:18 AM
To start any service from a command line, type:
service nameofservice start
for nmb it would be "service nmb start" without the quotes
pepper
08-16-2002, 05:02 AM
Here is a clarification of my samba problem.
When I first had tried to configure Samba I had the problem with having localhost as my hostname/computer name. I had fixed that by changing the hostname in /etc/sysconfig/network file. I also added netbios name = NEWHOSTNAME to the global section of my smb.conf file. Once I did that I started to get my current error. My current error is that when I try and access my linux hard drive from windows.
I have changed my hostname back to localhost.localdomain and just leaving the netbios name in the smb.conf file hoping that it would work, but it didn't.
I don't know where to go from here. I was thinking of trying to use swat to configure this but all the HOW-TO's do not tell me how to configure it on a RedHat box.
thanks,
pepper
baz2
08-16-2002, 07:52 AM
Originally posted by pepper
I don't know where to go from here.
Well, here's what I'd do if I were you.
1. Reinstall RH. Make sure it is a Reinstall, and not an Upgrade. Choose the Server option during install. When given the option to select packages, be sure and select SMB. I select all of them except DNS (since I know I will not be using Linux for DNS -- at least for now). There are some others I'll probably never use, but always install everything "just in case."
2. After install, use the Network configuration GUI to change the localname.hostname to a single local computer name. This change must be made on both the HOST tab of the GUI, and the DNS tab. The DNS tab is where you put in your DNS server IP addresses for internet connectivity. With RH 7.2, I've found that it initially picks these up correctly from DHCP, but then loses then when I change localname.hostname, so I have to reenter them manually. You may not be using DHCP, and may have to do this anyway.
3. Use the file manager Tree to navigate to /etc/samba/smb.conf, right click, and open with gedit. Change the "workgroup=" to point to the name of your workgroup. Initially, this is the only change you need to make. This will expose the /home folders of users. You can go back and make additional shares, if you want, after you know things are working correctly.
4. Set up your linux user accounts. Convert them to samba accounts. First time out, I would do this using the command line steps outlined in Chapter 11 of the Red Hat Configuration guide. After you know samba is working, you might try to manage the conversions with webmin.
That should do it. FYI, I upgraded from RH 7.2 to RH 7.3 last night. The install did put in a new copy of smb.conf, with a slightly different file size than the old, so I am going to look and see what, if anything, changed. I am also probably going to install RH 7.3 from scratch on one or more boxes today, and configure Samba on them, so I post if I find that things are somehow different than 7.2. But I've guided numersous students through the installation of 7.2 and the configuration of Samba using the steps outlined above.
Good luck. Hang in there!
baz2
08-16-2002, 01:15 PM
I just had a student install RH 7.3 on three workstations and configure Samba as outlined in the preceding replies. It worked just as expected. So if you are game, I really think you should reinstall along the lines described above.
pepper
08-16-2002, 05:04 PM
Should I change the aliases part of the 127.0.0.1 IP as well as the hostname in the Hosts tab?
pepper
08-16-2002, 09:00 PM
I have now changed my linux machine to a linux server, I followed the instructions that baz2 gave me. Only problem is that I still have the same problem. I should tell you that my home network is wireless and that the network card that is in my linux machine is a wireless card. I don't know if that is the problem but at this point its the only thing that I can think of that it could be. But if I can access the internet with the wireless card, shouldn't I be able to share files with windows with the card? Has anyone had luck with samba and a wireless card?
pepper
cowanrl
08-17-2002, 06:43 AM
The fact that you are using wireless cards shouldn't keep Samba from working. If you can ping from the XP machines to the Linux machine using the IP address then basic TCP/IP connectivity is working.
When you re-installed Red Hat, did you disable the firewall? If you just selected the default firewall settings for a Red Hat install, it will block Samba traffic. That's the number 1 cause of problems with Samba, especially with Red Hat. To check, enter this from the command line on your Linux machine:
service iptables stop
That will shut down the firewall. Then try to access your Samba shares from your XP machines.
If stopping the firewall doesn't fix it, then execute this command from the command line of your XP professional machine:
net view \\nameofsambaserver
Substitute the name you put in the "netbios name =" line in your smb.conf file for nameofsambaserver in the command. If it doesn't show you the shares on your Samba server, post the exact error message you get here.
Then, execute:
net view xxx.xxx.xxx.xxx
on the XP Pro machine. Substitute the IP address of your Linux server for the x's. If that doesn't show you a list of shares on your Samba server, than either Samba isn't running properly or you just don't have any shares set as browseable in your smb.conf file.
Also, how about post the contents of these files here:
# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = HOME
# 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
load printers = yes
# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx
printing = lprng
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m.log
# Put a capping on the size of the log files (in Kb).
max log size = 0
# Security mode. Most people will want user level security. See
# security_level.txt for details.
security = user
# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password server = *
; password server = <NT-Server-Name>
# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
; password level = 8
; username level = 8
# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
# The following is needed to keep smbclient from spouting spurious errors
# when Samba is built with support for SSL.
; ssl CA certFile = /usr/share/ssl/certs/ca-bundle.crt
# The following are needed to allow password changing from Windows to
# update the Linux sytsem password also.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
# the encrypted SMB passwords. They allow the Unix password
# to be kept in sync with the SMB password.
unix password sync = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*success fully*
# 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
pepper
08-18-2002, 01:55 AM
# 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
; 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
pepper
08-18-2002, 02:06 AM
I finally got it to work. I had to shut down iptables and ipchains inorder for it to work. Thanks for your help everyone, is there a way that I can have the firewall running and have SAMBA working at the same time?
justlinux.com
Copyright Internet.com Inc. All Rights Reserved.