smbmount and "canonicalized pathnames"?
David Wuertele
dave-gnus at bfnet.com
Mon Sep 20 19:22:10 GMT 2004
I'm trying to figure out why Windows can access shares with Japanese
names, but smbmount can't. tethereal shows me a few differences in
the Tree Connect AndX commands.
Why doesn't smbmount set "Canonicalized Pathnames"? Windows does.
What is this for?
Also, how do I force smbmount to encode strings as unicode instead of
ASCII?
I'm attaching the complete frames for the tree connect request and
response. Here is a summary of the flags:
Windows:
SMB (Server Message Block Protocol)
SMB Header
Server Component: SMB
SMB Command: Tree Connect AndX (0x75)
NT Status: STATUS_SUCCESS (0x00000000)
Flags: 0x18
0... .... = Request/Response: Message is a request to the server
.0.. .... = Notify: Notify client only on open
..0. .... = Oplocks: OpLock not requested/granted
...1 .... = Canonicalized Pathnames: Pathnames are canonicalized
.... 1... = Case Sensitivity: Path names are caseless
.... ..0. = Receive Buffer Posted: Receive buffer has not been posted
.... ...0 = Lock and Read: Lock&Read, Write&Unlock are not supported
Flags2: 0xc807
1... .... .... .... = Unicode Strings: Strings are Unicode
.1.. .... .... .... = Error Code Type: Error codes are NT error codes
..0. .... .... .... = Execute-only Reads: Don't permit reads if execute-only
...0 .... .... .... = Dfs: Don't resolve pathnames with Dfs
.... 1... .... .... = Extended Security Negotiation: Extended security negotiation is supported
.... .... .0.. .... = Long Names Used: Path names in request are not long file names
.... .... .... .1.. = Security Signatures: Security signatures are supported
.... .... .... ..1. = Extended Attributes: Extended attributes are supported
.... .... .... ...1 = Long Names Allowed: Long file names are allowed in the response
Smbclient:
SMB (Server Message Block Protocol)
SMB Header
Server Component: SMB
SMB Command: Tree Connect AndX (0x75)
Error Class: Success (0x00)
Reserved: 00
Error Code: No Error
Flags: 0x08
0... .... = Request/Response: Message is a request to the server
.0.. .... = Notify: Notify client only on open
..0. .... = Oplocks: OpLock not requested/granted
...0 .... = Canonicalized Pathnames: Pathnames are not canonicalized
.... 1... = Case Sensitivity: Path names are caseless
.... ..0. = Receive Buffer Posted: Receive buffer has not been posted
.... ...0 = Lock and Read: Lock&Read, Write&Unlock are not supported
Flags2: 0x0001
0... .... .... .... = Unicode Strings: Strings are ASCII
.0.. .... .... .... = Error Code Type: Error codes are DOS error codes
..0. .... .... .... = Execute-only Reads: Don't permit reads if execute-only
...0 .... .... .... = Dfs: Don't resolve pathnames with Dfs
.... 0... .... .... = Extended Security Negotiation: Extended security negotiation is not supported
.... .... .0.. .... = Long Names Used: Path names in request are not long file names
.... .... .... .0.. = Security Signatures: Security signatures are not supported
.... .... .... ..0. = Extended Attributes: Extended attributes are not supported
.... .... .... ...1 = Long Names Allowed: Long file names are allowed in the response
-------------- next part --------------
A non-text attachment was scrubbed...
Name: windows-tree-connect
Type: application/octet-stream
Size: 9648 bytes
Desc: not available
Url : http://lists.samba.org/archive/samba-technical/attachments/20040920/63ea4c86/windows-tree-connect.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smbclient-tree-connect
Type: application/octet-stream
Size: 9291 bytes
Desc: not available
Url : http://lists.samba.org/archive/samba-technical/attachments/20040920/63ea4c86/smbclient-tree-connect.obj
More information about the samba-technical
mailing list