[jcifs] MSBROWSE ?
J.Sugrue at pilz.ie
J.Sugrue at pilz.ie
Mon Oct 1 20:02:54 EST 2001
hi
I just found out that the second network card was not connected to the
network at all.
Is there any way of avoiding checking a network card such as this?
thanks
James
James Sugrue
|--------+--------------------------->
| | "Michael B. |
| | Allen" |
| | <mballen at erols.co|
| | m> |
| | Sent by: |
| | jcifs-admin at lists|
| | .samba.org |
| | |
| | |
| | 25/09/01 00:25 |
| | |
|--------+--------------------------->
>---------------------------------------------------------------------------------------------------------------------------------------------|
| |
| To: J.Sugrue at pilz.ie |
| cc: "Michael B. Allen" <mballen at erols.com>, "Christopher R. Hertel" <crh at ubiqx.mn.org>, jcifs at samba.org, |
| jcifs-admin at lists.samba.org |
| Subject: Re: [jcifs] MSBROWSE ? |
>---------------------------------------------------------------------------------------------------------------------------------------------|
On Mon, Sep 24, 2001 at 11:32:40AM +0100, J.Sugrue at pilz.ie wrote:
>
> Great, that worked.
> However, it is quite slow now, on the machine with 2 network cards,
> It works as normal on a machine with one network card.
>
> any ideas of how this could be speeded up?
Something's probably timeing out. To be honest, I have never tooled with
multiple interfaces. You'll need to flip on full logging and/or break
out Ethereal/NetMon to see what's happening. Chances are it's just some
name lookup failures. Whatching a log is the easiest way to see what
setting isn't quite right.
If you're not confident at looking at the traces, record a full log with
the -Dlog=ALL VM flag and send it to mballen at erols.com (if you send it
to the list s/secret/fake/).
Mike
> > For jCIFS to retrive the list of hosts or enumerate domains on a
NetBIOS
> > network, the Master Browser must be queried. This is done by
broadcasting
> > a for a special name that has the word MSBROWSE in it. If a master
browser
> > is not found it is likely that the network settings for jCIFS will need
> > to be adjusted. There are several properties available to do this. See
> > the bottom of the Overview Summary in the jCIFS API documentation for
> > details about all available jCIFS properties and how to set them.
> >
> > Here are some properties that are specific to the problem you describe:
> >
> > jcifs.netbios.baddr
> > jcifs.smb.client.laddr
> > jcifs.netbios.laddr
> >
> > Note, you can simply specify laddr=<ip of interface> without the prefix
> > and I believe that will set both the transport and netbios name service
> > interfaces. I believe baddr will also be important.
More information about the jcifs
mailing list