FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i'm at a loss, i'm running FC4. i can connect to pc's from my FC4 machine with smb:\\ using the ip address of the computers i'm connecting to but not the computer names. on windows computers the name works, but not in linux.
# 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 = IRKSHOUSE
# 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 = 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_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
# 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 = yes
# 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
# 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 = yes # 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
Windows XP SP2? Microsoft's KB 884020 should help. Also I see one error in the hosts allow line:
hosts allow = 192.168.1.<missing an octet><need a seperator here> 192.168.2. 127.<no space and remove the extra dot at the end> should read 192.168.1.0, 192.168.2.127
From the www.faqs.org site it states:
"hosts deny = ALL
The option hosts deny specifies the list of hosts that are not permitted access to Samba services unless the specific services have their own lists to override this one. For simplicity, we deny access to all hosts by default, and allow specific hosts in the hosts allow = option below.
hosts allow = 192.168.1.4 127.0.0.1
The option hosts allow specifies which hosts are permitted to access a Samba service. By default, we allow hosts from IP class C 192.168.1.4 and our localhost 127.0.0.1 to access the Samba server. Note that the localhost must always be set or you will receive some error messages."
And from the 2nd site it shows this table:
Example Explanation
hosts allow 192.168.10.0/255.255.255.0 Allow all hosts in the given network/netmask
hosts allow 160.210 EXCEPT 160.210.24.56 Allow all hosts beginning with 160.210 except 160.210.24.56
hosts allow 192.168.10 192.168.20 Allow all hosts beginning with 192.168.10 or 192.168.20
hosts deny 130.74 Deny all hosts beginning with 130.74
Myself I would follow the first example from faqs.org it looks more correct. I think they omitted the .zero(s) assuming people would understand they need to be there. If you scroll down on the page it shows you should have these lines added to your smb.conf file also:
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
What does a packet sniff from ethereal say?
You should be able to filter that by using smb in the sniff results filter.
BTW thanks for the links to those sites, found some other useful stuff for things I am trying to configure
F
What does a packet sniff from ethereal say?
You should be able to filter that by using smb in the sniff results filter.
BTW thanks for the links to those sites, found some other useful stuff for things I am trying to configure
sorry, i don't understand this
i'm still not able to get to my printers. i haven't tried the loop back patch for XP. i'm still able to access printers from windows to windows.
hp laserjet 6l - this is the one i'm trying to connect to which is attached to "thunder"
epson stylus 200?? attached to shadow
hp inkjet 1700 attached to gammer
as of yet i don't think i'm able to communicate with the windows boxes or smb is not able to resolve the machine names to ip address. or could be something with permissions.
i am able to see my FC4 box in "my network places" list in WinXP, but not able to access it since i haven't shared anything out as of yet.
thank you for your help so far, it is greatly appreciated.
eric
Ok if you go into:
in Gnome
Desktop (in the task bar) -> System Settings -> Server Settings - > Services -> network high light it and then click on restart, if you have DHCP enabled on the interface for the NIC it should do a DHCP renew.
To check your Internet configuration System Tools -> Network Device Control and see if it shows DHCP next to eth0 or PPP0 what ever your Internet connection is.
In KDE
Menu -> System Settings -> Server Settings - > Services -> network high light it and then click on restart, if you have DHCP enabled on the interface for the NIC it should do a DHCP renew.
still no luck. i can access the internet from my linux computers, other shares using smb://192.168.1.XXX but not using the computer names. It seems linux isn't doing a dns lookup from the router. My router is a linksys befsr81, if I log into the router none of my linux computers show up in the dhcp table.
the ethernet device, eth0, is set to "automatically obtain ip address settings with dhcp" and set to automatically obtain dns information from provier.
It sounds like the router isn't adding the Linux machine(s) to the DNS table. Follow this link if you don't know that much about DNS's functionality http://www.stamey.nu/DNS/DNSHowItWorks.asp
It might be that you need to define a WINS (Windows Internet Naming something, Schema I think) name for your SAMBA server so the Linksys thinks the Linux machines are Windows machines. Linksys assumes you are only using Windows with thier router because that's what the majority (in theory) of users are.
Follow the SAMBA server link (in the previous post from me) configuration file for a work group completely, from start to finish, and define that work group in the SAMBA server. Then, (I'm going to assume you are doing this at home) I would try giving all your computers Static IPs (but leave the DHCP from the ISP enabled) and define them in the SAMBA .conf file as well. Then define them in the Routers Routing Table so that they are getting mapped properly. Myself I would use something.localdomain so it's easier to define on the Router.
If you have SELinux, and/or a Firewall enabled on your Linux machine(s) you have two options; disable it, 2) edit the policy to allow ports 137-139 and 445 for only those addresses and ONLY the SMB protocol, an approximate example: allow=smb://10.10.10.10/255.255.255.255.255:137,138,139,445 (the 4 "octets of 255 locks it to only that IP, if you use 10.10.10.10/255.0.0.0 it allows the whole sub net).
Also ensure that all machines are using the Linksys as the default gateway, and set that as the primary DNS server first. To my knowlege that should force the local machines to look to the table on the Router for DNS information instead of the ISP's Table first and force them to go to your SAMBA shares by DNS name locally instead of searching the Internet first.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.