browsing across subnets

[Avantel Systems]

Well, actually ipsec should be carrying those netbios packets through on =
ports
used for the ipsec tunnel so do *not* open your firewall for ports 137-13=
9.  You
verified that there was access to those ports by the last test I suggeste=
d and
that test passed.

Since you can see (all?) the hosts in the browse list, that tells me the
samba servers are communicating OK which means those netbios packets are =
getting
through that ipsec tunnel.

Have you tried turning domain logons OFF - or are you truly trying to mak=
e
samba do domain logons?  I suspect the source of your problem at this poi=
nt (now
that you can at least see the machines on the other subnet in your browse=
 list)
is simply permissions & user/password issues - have you checked that? Are=
 you
using share or user level security?  Try creating a share that's open to
everyone and see if you can browse that.  Also try turning on debug and c=
heck
the log files for possible errors.  (yes, you may have to dig into some o=
f the
docs)

Also, what -if anything- did you have to chage to get the hosts to be vis=
ible in
your browse list? =20

Alex @ Avantel Systems

On Fri, 27 Oct 2000, you wrote:
> >
> >By that I am assuming it is either a routing or firewall problem=20
> >keeping the connection from working.  Pinging the client works fine=20
> >though.  How can I find where the problem is to solve it?  The=20
> >connection between 192.168.3.0 and 192.168.4.0 is via a freeswan=20
> >ipsec tunnel.
>=20
> Make sure ports 137, 138, 139, both tcp and udp get through.
>=20
> Regards,
>         Robert
>=20
>=20