browsing across subnets

Avantel Systems alex at avantel.ca
Thu Oct 26 23:11:45 GMT 2000


Try this;

from a host on one network to the other subnet

echo hello | telnet remote-server-ip 139

where the remote-server-ip is the ip address of the remote samba server (=
use
the internal (private) address and try again with the external ip address=
=2E

if you get Connection refused, then;

either you're blocking the ports (firewall?)
or samba is not listening on the external interface (see interface option=
)

If, on the other hand you get a "Connected" message followed by
"Connection closed" message, then;

the problems is something else.

Try that & let me know what happens

Alex @ Avantel

On Thu, 26 Oct 2000, you wrote:
> I have changed around settings several times, right now each is the dom=
ain
> master browser, local master and preferred, one is setup as the wins se=
rver
> with all clients and the other samba server set to use it for wins.  In=
 its
> wins.dat file there is an entry for the other samba server and a client=
 on
> the other subnet setup to use it as wins but no one can see the second
> workgroup on the subnet where the wins samba server resides.  From that
> machine when I try this for the non-wins samba server:
>=20
> smbclient -L server
>=20
> I get this:
> added interface ip=3D127.0.0.1 bcast=3D127.255.255.255 nmask=3D255.0.0.=
0
> added interface ip=3D192.168.3.1 bcast=3D192.168.3.255 nmask=3D255.255.=
255.0
> Got a positive name query response from 127.0.0.1 ( 192.168.4.1 )
> session request to SERVER failed (Not listening for calling name)
> Got a positive name query response from 127.0.0.1 ( 192.168.4.1 )
> session request to *SMBSERVER failed (Not listening for calling name)
>=20
> 192.168.4.1 is the correct IP for that server.
>=20
> Any idea what to try next?
>=20
> Thanks
> Andy
>=20
> ----- Original Message -----
> From: "Avantel Systems" <alex at avantel.ca>
> To: "Andy Worthington" <andy at rockcity.com>
> Cc: <samba at samba.org>
> Sent: Wednesday, October 25, 2000 6:16 PM
> Subject: Re: browsing across subnets
>=20
>=20
> You need to make both samba servers domain master browsers.  And you're
> right
> about the wins server - disconnects can cause odd behaviour - especiall=
y
> since
> samba cannot (yet?) be a secondary wins server.
>=20
> Alex @ Avantel
>=20
> On Wed, 25 Oct 2000, you wrote:
> > I've read through the BROWSING*.txt files in docs/textdocs and I thin=
k I
> set
> > everything up right but I can't get this to work.
> >
> > I am using IPSEC to connect two lans that are seperated by the intern=
et
> and
> > use dsl lines for internet connection.  That is setup and working.  I=
 can
> > ping from a client on one subnet to a client on another subnet with n=
o
> > problems.  One subnet is 192.168.3.0 and the other is 192.168.4.0
> >
> > The 192.168.3.0 subnet has the workgroup of irish and the 192.168.4.0=
 has
> > the workgroup of msp.
> >
> > I want both of these subnets to see both workgroups.  All clients are
> win98
> > and there is a samba server on each network that is also doing the ip=
sec
> and
> > acting as the firewall(currently setup to accept everything).  Each s=
ubnet
> > has the samba server setup as the WINS server for that subnet.
> >
> > in the smb.conf file on 192.168.3.1 I added:
> >
> >    remote browse sync =3D 192.168.4.1
> >    remote announce =3D 192.168.4.1
> >
> > and on 192.168.4.1 I added:
> >    remote browse sync =3D 192.168.3.1
> >    remote announce =3D 192.168.3.1
> >
> > Any ideas how to solve this so that each subnet can see and use both
> > workgroups.  Another question about the WINS servers, I read that it =
is
> best
> > if only one is used for both subnets.  If I do this and the link drop=
s,
> the
> > subnet without samba setup for wins will of course no longer have a w=
ins
> > server.  Will this Win98, ME clients automatically start using broadc=
ast
> > based name resolution when the WINS server becomes inaccessable?
> >
> > TIA
> > Andy Worthington




More information about the samba mailing list