Nicolas Costes wrote:
Le Samedi 24 Juin 2006 18:44, [eMAXX] [EMAIL PROTECTED] a écrit :
Whenever I click on "My Network places >> Microsoft Windows-network"
(swift translation out of Dutch), Windows tells me I have no rights to
open the Samba host. If I connect to the host directly (eg: \\vs01\foo)
there is no problem (will need user/pass, but that's ok).
Mmmm, the error message musn't be about rights, but certainly about "host not
found", is it ?
I discovered Windows is sending broadcast packages[...]
Yes, just a little :D !!!
Many of them, if not all, are related to machine discovery and name
resolution. But you can avoid most of these broadcasts by using a WINS server
(WIndows Name Service). This acts like a kind of DNS, where every machine
(even servers) registers itself upon bootup, and is deleted when going down.
So, the WINS server keeps IP <=> NetBIOS name correspondance records.
I use this at work, and it works with a mix of NT, 2000, Samba, vserver+Samba
clients and servers without any problem. And my vservers have _no_
capabilities !
That's great! That was an option if this mailinglist wouldn't provide a
solution :), but Herbert came (via privat e-mail I just saw) with the
following solution:
try adding the broadcast
ip (192.168.1.255) to the list of ips assigned
to the guest (i.e. add another interfaces subdir
with a nodev entry and the broadcast ip)
So I did add an extra interface:
../interfaces/1/nodev >> 'empty'
../interfaces/1/ip >> 192.168.1.255
And that worked! ... but ... I want to run several samba servers in
different in vserver guests and though I'm setting "bind interfaces
only", samba (nmbd/smbd) is still binding to 0.0.0.0 in both guests:
vs01:
Proto Recv-Q Send-Q Local Address Foreign Address
State
tcp 0 0 192.168.1.8:901 0.0.0.0:*
LISTEN
tcp 0 0 192.168.1.8:22 0.0.0.0:*
LISTEN
udp 17600 0 0.0.0.0:137
0.0.0.0:*
udp 17600 0 0.0.0.0:138 0.0.0.0:*
vs02:
Proto Recv-Q Send-Q Local Address Foreign Address
State
tcp 0 0 192.168.1.9:901 0.0.0.0:*
LISTEN
tcp 0 0 192.168.1.9:22 0.0.0.0:*
LISTEN
udp 17600 0 0.0.0.0:137
0.0.0.0:*
udp 17600 0 0.0.0.0:138 0.0.0.0:*
Guess a wins server (winbind in Debian I suppose) will not fix this :)
Is running samba servers the way I want to (several vserver guests with
each it's own sambaserver) even possible?
It is very useful, even if you have two machines : Just setup one as a WINS
server, the other as a client and the NetBIOS resolution problems will go
away (like to wait 14 minutes for machine discovery) !
On the server's smb.conf :
wins support = yes
On the clients' smb.conf (which can be file or print servers ;-)) :
wins server = ip.of.wins.server
Will try winbind later on, it seems to be a good option!
Regards,
Vince.
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
