Hi Irf,
I am running samba on Suse9 connected to the local network with no domain controller. I have samba set to make the Suse box the master browser.
the windows box IP is 192.168.0.2 netmask 255.255.0.0
the suse box IP is 192.168.1.2 netmask 255.255.255.0
these are connected through a linux gateway/firewall
with 3 ethernet cards which have the addresses 192.168.0.1 (to Windows box) and 192.168.1.1 (to Suse box)
plus my connection to my cable modem, so its a bit different than your setup.
Make certain that your windows firewall, or any machine connected directly to the outside world does not allow incoming or outgoing NETBIOS connections on any interfaces other than those on the internal network...you probably know this but its worth mentioning as it is the equivalent of an open barn door with a free beer sign, security-wise.
Here's the basic setup similar to what I am using:
Code:
[global]
# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = MYWORKGROUP
netbios name = susebox
# 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.2 192.168.0.2 127.0.0.1
# notice that I don't allow my gateway/firewall to access any shares
# just an extra precaution
# This must be a valid user on the linux box as well as a valid
# user generated by the smbadduser script
valid users = oOZe
# Security mode. Most people will want user level security. See
# security_level.txt for details.
security = user
# 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
# 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
socket address = 192.168.1.2
# 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 = eth0
bind interfaces only = yes
# 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 = yes
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
os level = 99
# 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
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
wins support = 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
# a typical share
[download]
comment = downloads
path = /mnt/store/download
valid users = oOZe
# public = yes
writeable = yes
printable = no
create mask = 0664
directory mask = 755
guest ok = no
follow symlinks = yes
browseable = yes
This is not a complete smb.conf, there are other settings that may need to be tweaked, but have no bearing on the domain/workgroup question.
On my XP box I do not have File and Printer Sharing enabled as I have no need to share whats on the XP box with any other system. What this prevents is allowing me to browse to the samba server directly through the network neighbourhood. I can see MYWORKGROUP, but it is inaccessible.
I access the samba shares by mapping network drives and connecting as a different user (in this case oOZe and checking the 'Reconnect at Logon" box to avoid retyping the password etc) and also using the "Search for Computers..." by right-clicking the My Network Places Icon to find "susebox", which lists all the enabled shares. I'm not sure if these methods will work properly with WinME or not. You may need to search for computers by IP address, although adding your NETBIOS names to the hosts file on XP and ME should (but doesn't always seem to) work.
I used to have the susebox IP listed as a WINS server in my Local Connection Properties/Internet Protocol(TCP), but disabling it has not noticably affected access to samba shares.
Once you have things set up there is a utility that is installed with samba called 'testparm' which will spit out a lot of info about your configuration.
If your machines are directly connected together or are on the same subnet (say the xp box has IP 192.168.0.2 and the Linux box has IP 192.168.0.3, both with the subnet mask 255.255.255.0) then they should have no trouble communicating. If this is not the case you will need to use the 'route' command to modify the routing tables so that the machines can speak to each other (ping to test).
In my case I had to do this on the XP box:
Code:
route -p ADD 192.168.1.0 MASK 255.255.255.0 192.168.0.1
^destination ^mask ^gateway
The -p is for Persistent, so that it remains between reboots.
and on the Suse box add:
192.168.0.0 192.168.1.1 255.255.0.0 eth0
to
/etc/sysconfig/network/routes
If you are using DHCP for IP address assignment on your internal network, you may want to change those to static IP's as it is less complicated that way (to me anyway).
Hopefully I covered everything you need to get it running.
Good luck,
.oOZe.
Newbie having problems with Suse 9 and Samba
