3 cifs - Microsoft™ Windows network filesystem client
36 translates between Microsoft's file-sharing protocol
37 (a.k.a. CIFS or SMB) and 9P, allowing Plan9 clients to mount file systems
38 (shares or trees in MS terminology) published by such servers.
40 The root of the mounted directory contains one subdirectory per share,
41 and a few virtual files give additional information.
43 .TF "-a\fI auth-method"
50 by default, but alternative strategies may be
51 selected using this option.
53 eschews cleartext authentication, however
54 it may be enabled with the
57 The list of currently-supported methods is printed
58 if no method name is supplied.
60 .I "Windows server 2003"
63 method by default, though it can be configured to be more flexible.
66 Enable file ownership resolution in
69 This requires an open and close per file and thus will slow
71 considerably; its use is not recommended.
74 followed by non-whitespace separated list of debug options
76 writes specific debug output to file descriptor 2. See source
85 attempts to enforce case significance file and directory names, though objects
86 which differ only in their case still cannot co-exist in the same directory. The
88 option disables this behaveiour.
91 lists extra parameters which will be passed to
93 to select a specific key.
94 The remote servers's domain is always included in the keyspec,
96 that all servers in a Windows domain share an authentication domain;
105 key proto=pass dom=THEIR-DOMAIN service=cifs
106 user=MY-USERNAME !password=XYZZY
111 set the mount point for the remote filesystem;
115 .BI -n " called-name"
116 The CIFS protocol requires clients to know the NetBios name of the
117 server they are attaching to, the
119 If this is not specified on the command line,
121 attempts to discover this name from the remote server.
122 If this fails it will then try
124 and finally it will try the name
131 .BI -t " dfs-timeout"
132 sets the timeout in for DFS redirections - it defaults to 100ms.
133 This is a reasonable minimum, it should have a value just greater than
134 the RTT to the most distant server being accessed.
137 The address of the remote server to connect to.
140 A list of share names to attach on the remote server; if none is given,
142 will attempt to attach all shares published by the remote host.
143 .SS "Synthetic Files"
144 Several synthetic files appear in the root of the mounted filesystem:
149 Contains a list of the currently attached shares,
150 with fields giving the share name, the share type, disk free space / capacity,
151 and a descriptive comment from the server.
154 Contains the username used for authentication,
155 server's called name, server's domain,
156 server's OS, the time slip between the local host and the server,
157 the Maximum Transfer Unit (MTU) the server requested, and optionally a flag
158 indicating only guest access has been granted.
159 The second line contains a list of capabilities offered by the server which is
160 mainly of use for debugging
164 Each line contains a user's name, the user's full name,
165 and a descriptive comment.
168 Each line gives a group's name, and a list of the names of the users who
169 are members of that group.
172 Lists the users authenticated, the client machine's NetBios name or IP address,
173 the time since the connection was established,
174 and the time for which the connection has been idle.
177 One line per domain giving the domain name and a descriptive comment.
180 One line per domain giving the domain name and a descriptive comment,
181 the version number of the OS it is running, and comma-separated list of flags
182 giving the features of that OS.
185 Lists the top level DFS domains and the servers that
189 Contents of the DFS referal cache, giving the path prefix,
190 the expiry time (or -1 for never), the measured RTT to the server
191 in milliseconds, the server proximity (0 is local), the server name,
192 and the share name on that server.
195 has been tested against aquarela,
197 Windows 95, NT4.0sp6,
198 Windows server 2003, Windows server 2003, WinXP pro,
199 Samba 2.0 (Pluto VideoSpace), and Samba 3.0.
201 Windows Vista require a hotfix (registry change)
202 to support NTLMv2 without GSSAPI, see http://support.microsoft.com/kb/957441.
205 option can be used to force
207 to use one of the less secure authentication mechnisms.
209 Windows 7 has dropped support for RAP, which is used to generate
210 the synthetic files offered by
212 RAP is also used to enumerate the shares offered by the remote host so
213 remote share names must always be specified on the command line.
215 The NetApp Filer was supported by earlier releases, however recent
216 attempts to mount one have failed. Should a server be available it is
217 likely that this could be easily fixed.
225 DFS support is unfinished, it will not follow referals that span servers.
227 Kerberos authentication is not supported.
229 NetBios name resolution is not supported, though it is now rarely used.
232 first appeared in Plan 9 from Bell Labs. It was updated to the author's
233 latest revision for 9front (January, 2012).