[jcifs] Using jCIFS across sub-net boundaries?

[Eric Glass]

With the configuration he's got, he shouldn't need WINS (I don't
think); he's specifying an IP address for jcifs.http.domainController,
so the jcifs.smb.client.domain setting is actually superfluous (unless
he's also going to specify username/password for signing).  I would
think he would just need TCP/139 (and maybe 445?) to 10.106.105.39.


Eric



On 10/24/06, Christopher R. Hertel <crh at ubiqx.mn.org> wrote:
> Michael B Allen wrote:
> > On Tue, 24 Oct 2006 12:11:19 -0500
> > "Christopher R. Hertel" <crh at ubiqx.mn.org> wrote:
> >
> >> things work properly.  UDP/137 will need to be open in order to assure that
> >> the NBNS server actually gets the name registrations.  Check the NBNS
> >> database to see if the entries are currently there.
>
> I meant the server registrations.
>
> If the server and NBNS are on the same side of the firewall, then the port
> needs to be open so that jCIFS can query the NBNS.  If the server and NBNS
> are on opposite sides, then the port will need to be open so that the server
> can register.
>
> > JCIFS doesn't register names. But 137 is needed to lookup the name(s)
> > of the DC using WINS.
>
> Yep.
>
> Chris -)-----
>
> --
> "Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
> Samba Team -- http://www.samba.org/     -)-----   Christopher R. Hertel
> jCIFS Team -- http://jcifs.samba.org/   -)-----   ubiqx development, uninq.
> ubiqx Team -- http://www.ubiqx.org/     -)-----   crh at ubiqx.mn.org
> OnLineBook -- http://ubiqx.org/cifs/    -)-----   crh at ubiqx.org
>