3 cifs - Microsoft™ Windows network filesystem client
30 translates between Microsoft's file-sharing protocol
31 (a.k.a. CIFS or SMB) and 9P, allowing Plan9 clients to mount file systems
32 (shares or trees in MS terminology) published by such servers.
34 The root of the mounted directory contains one subdirectory per share,
35 always named in lower case, and a few virtual files of mixed case which
36 give additional server, session, share, and user information.
38 .TF "-a\fI auth-method"
45 by default, but alternative strategies may be
46 selected using this option.
48 eschews cleartext authentication, however
49 it may be enabled with the
52 The list of currently-supported methods is printed
53 if no method name is supplied.
55 .I "Windows server 2003"
58 method by default, though it can be configured to be more flexible.
61 Enable file ownership resolution in
64 This requires an open and close per file and thus will slow
66 considerably; its use is not recommended.
75 lists extra parameters which will be passed to
77 to select a specific key.
78 The remote servers's domain is always included in the keyspec,
80 that all servers in a Windows domain share an authentication domain;
89 key proto=pass dom=THEIR-DOMAIN service=cifs
90 user=MY-USERNAME !password=XYZZY
95 set the mount point for the remote filesystem;
100 The CIFS protocol requires clients to know the NetBios name of the
101 server they are attaching to, the
103 If this is not specified on the command line,
105 attempts to discover this name from the remote server.
106 If this fails it will then try
108 and finally it will try the name
116 The address of the remote server to connect to.
119 A list of share names to attach on the remote server; if none is given,
121 will attempt to attach all shares published by the remote host.
122 .SS "Synthetic Files"
123 Several synthetic files appear in the root of the mounted filesystem:
128 Contains a list of the currently attached shares,
129 with fields giving the share name, disk free space / capacity, the share type,
130 and a descriptive comment from the server.
133 Contains the username used for authentication,
134 server's called name, server's domain,
135 server's OS, the time slip between the local host and the server,
136 the Maximum Transfer Unit (MTU) the server requested, and optionally a flag
137 indicating only guest access has been granted.
138 The second line contains a list of capabilities offered by the server which is
139 mainly of use for debugging
143 Each line contains a user's name, the user's full name,
144 and a descriptive comment.
147 Each line gives a group's name, and a list of the names of the users who
148 are members of that group.
151 Lists the users authenticated, the client machine's NetBios name or IP address,
152 the time since the connection was established,
153 and the time for which the connection has been idle.
156 One line per domain giving the domain name and a descriptive comment.
159 One line per domain giving the domain name and a descriptive comment,
160 the version number of the OS it is running, and comma-separated list of flags
161 giving the features of that OS.
164 Top level DFS routing giving the DFS link type, time to live of the data,
165 proximity of the server, the Netbios or DNS name and
166 a physical path or a machine that this maps to.
168 DNS paths are usually assigned dynamicially as a form of load balancing.
175 NetApp Filer compatibility has not yet been tested; there may not be any.
177 DFS support is unfinished.
179 Kerberos authentication is unfinished.
181 NetBios name resolution is not supported, though it is now rarely used.
184 has only been tested against
185 aquarela, Windows 95, NT4.0sp6,
186 Windows server 2003, WinXP pro, Samba 3.0, and Samba 2.0 (Pluto VideoSpace).
187 No support is attempted for servers predating NT 4.0.