[jcifs] Network name resolve time

[Christopher R. Hertel]

What it means is that all name resolution is being done via the LMHOSTS file
and never even going out over the network.  That should be faster, assuming
that all of the names are in the LMHOSTS file.

I'm not sure why you're setting a non-empty scope.  Unless you really
understand how NetBIOS scopes work, don't set scope.

See: http://ubiqx.org/cifs/NetBIOS.html
...for a full description of the NBT Name Service.

Chris -)-----

Michael B Allen wrote:
> On Sun, Aug 8, 2010 at 10:39 PM, yankings <yankings at hotmail.com> wrote:
>> Dear All,
>>
>> Thanks for both of you!
>>
>> I tried to convert my testing program to use DNS by adding the domain suffix
>> but no improvement on the logon process (still needs 2x seconds to logon).
>>
>> I found that if the following properties set, the performance will be the
>> same as ver 1.1.11.  I will go for this workaround before i figure out what
>> happen to those twenties seconds,
>>
>>          Config.setProperty( "jcifs.netbios.scope","test_scope_id");
>>          Config.setProperty( "jcifs.resolveOrder", "LMHOSTS" );
> 
> That makes no sense. I'm surprised this even worked.
> 
> Get WireShark and figure out how to use it. It will improve your
> quality of life.
> 
> Mike
> 
>> Christopher R. Hertel wrote:
>>> Michael B Allen wrote:
>>>> Hi yankings,
>>>>
>>>> Your program doesn't make any sense. You set resolveOrder to do WINS
>>>> but you don't set a WINS server. Then the next method in the list is
>>>> DNS but the name given is not DNS name.
>>>>
>>>> In general, you should no longer be using NetBIOS names. You should
>>>> use DNS only and always use a fully qualified DNS hostnames. Sometimes
>>>> you can use only the first label of the DNS hostname but in this case
>>>> your OS must be configured with a suitable DNS search suffix.
>>>>
>>>> A proper JCIFS program should probably just set resolveOrder=DNS. But
>>>> LMHOSTS and WINS are still enabled by default just in case someone's
>>>> trying to connect to a Windows 98 machine.
>>> Mike is quite right about problems of confusing NetBIOS and DNS names.
>>> Don't confuse the two.  They're different name spaces.
>>>
>>> Unfortunately, the use of the NBT (NetBIOS over TCP) transport is still
>>> widespread.  Many shops run NBT without even knowing that they are doing
>>> so,
>>> and the SoHo NAS market still relies on it.  Many uses of jCIFS (including
>>> apps for my cellphone) expect to use NBT transport.
>>>
>>> So, while I agree that it would be nice to move everyone off of NBT and on
>>> to Naked TCP, it's not likely to happen any time soon.  Similarly, we
>>> should
>>> all give up on SMB/CIFS and move to SMB2, but that's not going to happen
>>> soon either.
>>>
>>> We still get requests for help with OS/2 on the Samba Tech mailing list.
>>>
>>> (no, really!)
>>>
>>> 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
>>>
>>>
>> --
>> View this message in context: http://old.nabble.com/Network-name-resolve-time-between-ver-1.1.11---1.3.14-tp29356405p29384219.html
>> Sent from the Samba - jcifs mailing list archive at Nabble.com.
>>
>>
> 
> 
> 

-- 
"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