I have Samba setup on my desktop working very well between 11.0 and VirtualBox on my desktop. I used Swerdna’s excellent howto @ Samba and Suse: HowTo Set up an openSUSE-Windows Home Office LAN/Network. Versions 10, 11.
I would now like to expand that to include my laptop (Vista & 11.0) and the wife’s laptop (Vista).
Anyone know of a good guide for setting up Samba on multiple computers?
The HowTo you referenced was intended for separate computers in a home environment, like the trio formed by your wife’s, your laptop and the desktop. Samba should be able to cope with vista and with switching on the laptop between vista and Suse. Set them all with a similar IP like e.g. 192.168.0.x, perhaps by using the DHCP feature in a router (wired or wireless doesn’t matter). For a SOHO LAN the key things are IP addressing to be consistent and connectivity through a switch (or router, which contains a switch). I’m not sure what the problem is, can you be more specific?
I don’t have the laptops & various OSes setup yet & haven’t tried them; They may work out of the box.
As I have them set up on a static system (each with a different IP using both wired & wireless), I was thinking I needed to take that into account somehow, e.g., tell Samba where each resided.
Let’s say:
my router is 192.168.1.1
desktop is 192.168.1.10
wife’s laptop is 192.168.1.20
my laptop is 192.168.1.30
Is there something special I need to do to take that into consideration before I start?
A major point is already satisfied: they are all 192.168.1.x with only x varying – so that’s good.
Samba finds computers by the IP address + netbios name pair. So good name resolution is important:
IP addressing is already fine.
They need the same workgroup name on all.
They need a different netbios name on each (this separates them for samba browsing).
They need holes in the firewall in Suse. On 11 these are supposed to be open by default, but there was a slip up and one item was left closed, so easier to turn SuSEfirewall2 off until Samba works and then fix the firewall.
It is a vast improvement to add the line: name resolve order = bcast hosts lmhosts wins into smb.conf [global] and make each Suse a Local Master browser.
And you are correct, they just might work out of the box, so try that first of all.
swerdna wrote:
>
> snakedriver;1863391 Wrote:
<snip>
> It is a vast improvement to add the line: name resolve order = bcast
> hosts lmhosts wins into smb.conf [global] and make each Suse a Local
> Master browser.
Be careful here, there can be only one Local Master Browser (LMB) per subnet,
this LMB is determined by an election among all the machines (Windows or
Linux). By default, Samba will participate in this election. If you set the
parameter “preferred master = yes”, then when Samba comes on line it will force
an election and be given some preference in wining the election. If two or
more machines (Windows or Linux) are preferred masters, you can get a lot of
elections and damage performance. You should set this only on one machine.
See man smb.conf for the writeup on these three parameters “local
master”, “preferred master” and “domain master”
> And you are correct, they just might work out of the box, so try that
> first of all.
>
>
–
P. V.
Cogito cogito ergo cogito sum.
Thanks guys; it’s a great joy to start off with insight from the pros:)
Jim
Nothing could have been easier:
Changed my laptop’s workgroup name to MYNAME
rebooted
now I can see desktop 11.0; desktop Vbox winxp & laptop Vista and vice-a-versa
Vbox & laptop both work with 11.0 desktop 100%
File xfer rate is beyond my expectations.
Vbox & laptop sees each other, but, do not communicate; needs a tweak;)
I’ll do the desktop “preferred master = yes” after work:)
(also get the wife’s laptop up)
Thanks again for the confidence building.