Fwd: [Samba] samba server in two lans
samba at the-wes.com
Wed Dec 24 18:31:01 GMT 2008
---------- Forwarded message ----------
From: John Mazza <maz at maznets.com>
Date: Wed, Dec 24, 2008 at 10:24 AM
Subject: Re: [Samba] samba server in two lans
To: wes <samba at the-wes.com>
Generally, I avoid multi-homing SAMBA (and Windows Servers too). It's always
seemed to cause browse list issues that are too troublesome to deal with.
I fix these issues at the network level by putting a firewall between the
subnets and placing the server in a DMZ. That way the two subnets have no
communication with each other, but both see the server at one IP
You may need to add a route to the server's subnet specifying the "firewall"
box's interface on each subnet to make it work.
On Wed, 24 Dec 2008 06:52:53 -0800, wes wrote:
>On Wed, Dec 24, 2008 at 4:56 AM, Vlastimil Šetka <
*setka at spsostrov.cz*> wrote:
>> Mohammad Reza Hosseini napsal(a):
>>> we have a samba server on centos 5.2 and 2 different lans. so we gave
>>> server to ips eth0:172.16.93.217 and eth1: 192.168.89.3
>>> but after this when we tried to join clients (windows xp) to the domain
>>> error: "the specified domain either does not exist or could not be
>>> contacted." what is the solution?
>> I had the same problem with Samba 3.0.24 - Debian Etch package. On PDC
>> server with 5 interfaces (VLAN) when I tried to join clients to domain,
>> sometimes I got several strange errors. Sometimes that errors came on at
>> From tcpdump output I found a problem that Samba server sometimes send
>> browse-reply UDP packets with source IP address of other interface than
>> outgoing interface. So the client can't locate PDC address.
>> This solution perfectly works for me:
>> smb.conf - global section:
>> interfaces = 192.168.1.0/24 lo
>> socket address = 192.168.1.5
>> where the 192.168.1.5/24 is address of one local interface. Be ware that
>> now Samba can be reached only on this 1 address.
>> On the clients is required to set the LMHOSTS file, so client knows
>> selected IP of PDC. I'm using this batch:
>> echo 192.168.1.5 PDCNAME #PRE #DOM:DOMNAME >
>> REM keep length = 16 chars including the \0x1b
>> echo 192.168.1.5 "DOMNAME \0x1b" #PRE >>
>> REM reload config
>> nbtstat -R
>> Maybe this issue is solved in some newer Samba version.
>I am having this issue also, running Samba 3.0.28a. But, I have a problem
>that the internal interface has a different IP than the external interface.
>So I can't tell Samba to listen only on the external interface, because
>Samba does not know that interface exists.
>How can I tell Samba to listen on 10.0.0.2, but tell its clients that its
>To unsubscribe from this list go to the following URL and read the
More information about the samba