I have it setup that way, with the clients behind each gateway to use
the gateway as their wins server. But I can't see them through my
network places. Any ideas? How long does it take to sync? Can I force
it to sync? Thanks for your help.
Jason
Charles Hamel wrote:
Jason,
Option A is the good way.
You could use remote browse sync according the the manpage since you only have
Samba servers. We have a mixed network here so it is not a solution. So your
configuration could be, anybody correct me if this is wrong :
For the 192.168.0.1 server :
remote browse sync = 192.168.2.1
wins support = yes
For the 192.168.2.1 server :
remote browse sync = 192.168.0.1
wins support = yes
The manpage doesn't mention that WINS is required for remote browse sync,
since it is based on the workgroup master browser. So maybe you don't need
WINS server at all.
Charles
On Wed, 30 Jun 2004 10:53:02 -0400, Jason C. Waters wrote
Charles,
The clients behind each gateway, do they point to the local wins
server then? So for the clients on the 192.168.0.0 network, they
would point to 192.168.0.1, where samba is running a wins server and
announces to 192.168.2.255? You have wins server = 192.168.1.50,
would I just have wins support = yes if its on the same machine?
Let me clear up what I'm trying to say.
Should my network look like this: Option A
Clients on network A(192.168.0.0) have a wins server of
192.168.0.1(the vpn gateway for them as well as a samba wins server)
192.168.0.1(Samba wins server with these settings, wins support =
yes, remote announce = 192.168.2.255) 192.168.2.1(Samba wins server
with these settings, wins support = yes, remote announce =
192.168.0.255) Clients on network B(192.168.2.0) have a wins server
of 192.168.2.1(the vpn gateway for them as well as a samba wins
server)
Or this: Option B
Clients on network A(192.168.0.0) have a wins server of
192.168.0.1(the vpn gateway for them as well as a samba wins server)
192.168.0.1(Samba wins server with these settings, wins support =
yes, remote announce = 192.168.2.255) 192.168.2.1(Samba wins server
with these settings, wins server = 192.168.0.1, remote announce =
192.168.0.255) Clients on network B(192.168.2.0) have a wins server
of 192.168.2.1(the vpn gateway for them as well as a samba wins
server)
Or this: Option C
Clients on network A(192.168.0.0) have a wins server of
192.168.0.1(the vpn gateway for them as well as a samba wins server)
192.168.0.1(Samba wins server with these settings, wins support =
yes, remote announce = 192.168.2.255) 192.168.2.1(Samba wins server
with these settings, wins server = 192.168.0.1, remote announce =
192.168.0.255) Clients on network B(192.168.2.0) have a wins server
of 192.168.0.1(the vpn gateway for them as well as a samba wins
server)
Thanks for your help
Charles Hamel wrote:
Hi Jason,
I have a similar setup and all I need to do was to enable ip directed
broadcast on the router and enter the following settings in smb.conf:
wins server = 192.168.1.50
remote announce = 192.168.1.255
HTH
Charles
On Wed, 30 Jun 2004 09:23:18 -0400, Jason C. Waters wrote
I'm having a hard time figuring this one out. I've done this before
when I had a PDC on one end of the VPN, and a BDC on the other.
This is what my setup looks like now.
Clients(XP)
|
PDC(192.168.0.4), windows 2000
|
|
WINS Server Samba(192.168.0.1), also the gateway for this network
|
|
Internet
|
|
WINS Server Samba(192.168.2.1), also the gateway for this network
|
|
Clients(XP)
With this setup I'm not sure how I'm suppose to setup each wins
server. Do I need to have one on each subnet, and then have them
both remote announce and remote browse sync to each other? Or
maybe some like that? When I'm using remote announce, should it be
192.168.0.1 or 192.168.0.0 or 192.168.0.255? Same with remote
browse sync, does it need to be the actual address of the other wins
server? or do I just send it to that subnet? Does anyone have a
working configuration with this setup(Domain on one side of the
tunnel and just a workgroup on the other, both are the same
workgroup). All the machines can ping each others ip, so I know
its not a tunnel issue. Thanks for your guys help.
Jason
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
--
Open WebMail Project (http://openwebmail.org)
--
Open WebMail Project (http://openwebmail.org)
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
