[jcifs] jCIFS and Share name length?
rjw
rob at wygand.com
Thu Nov 15 11:36:26 EST 2001
Actually, Samba appears to be 13 chars. jCIFS appears to be 16. My guess
is that this snippet might code might have soemthing to do with it:
jcifs.nbt.Name.writeWireFormat:
// write name
name = ( name.length() > 15 ) ?
name.substring( 0, 15 ).toUpperCase() :
name.toUpperCase();
I don't think this wouldn't explain why a browse would not return those
shares, though... I'm going to keep poking around.
rjw
Allen, Michael B (RSCH) wrote:
> I don't know much about the problem. I need to just try it and see what it looks like on the
> wire. If it's a RAP call it should work already (which suggests that it is not). If it's DCE RPC it
> will be a while before I get around to that (possibly never).
>
> Mike
>
>
>>-----Original Message-----
>>From: rjw [SMTP:rob at wygand.com]
>>Sent: Wednesday, November 14, 2001 6:47 PM
>>To: jcifs at samba.org
>>Subject: [jcifs] jCIFS and Share name length?
>>
>>Hey Mike,
>>
>>Are there any plans to support share names longer than 13 characters?
>>We've got some NT servers here with share names like
>>someshare_is_really_long.
>>
>>I assume this is a huge change? (A newer version of the protocol, I'd
>>imagine?
>>
>>Thanks,
>>rjw
>>
>>--
>>"They that can give up essential liberty to obtain a little
>> temporary safety deserve neither liberty nor safety."
>>
>>
>
--
"They that can give up essential liberty to obtain a little
temporary safety deserve neither liberty nor safety."
More information about the jcifs
mailing list