<div class="content"><p> </p><p>The NetrServerTransportAdd method binds the <span><a href="1709f6a7-efb8-4ded-b7ae-5cee9ee36320#gt_434b0234-e970-4e8c-bdfa-e16a30d96703" data-linktype="relative-path">server</a></span>
to the transport protocol.</p><dl>
<dd>
<div><pre> NET_API_STATUS NetrServerTransportAdd(
   [in, string, unique] SRVSVC_HANDLE ServerName,
   [in] DWORD Level,
   [in] LPSERVER_TRANSPORT_INFO_0 Buffer
 );
</pre></div>
</dd></dl><p><b>ServerName: </b>An <span><a href="5f8329ee-1965-4ea1-ad35-3b29fbb63232" data-linktype="relative-path">SRVSVC_HANDLE (section 2.2.1.1)</a></span>
pointer that identifies the server. The <span><a href="1709f6a7-efb8-4ded-b7ae-5cee9ee36320#gt_60e0e1fa-66fe-41e1-b5e3-ceab97e53506" data-linktype="relative-path">client</a></span> MUST map this
structure to an RPC binding handle (see <span><a href="https://go.microsoft.com/fwlink/?LinkId=89824" data-linktype="external">[C706]</a></span> sections
4.3.5 and 5.1.5.2). The server MUST ignore this parameter.</p><p><b>Level: </b>Specifies the information level of the
data. This parameter MUST be zero.</p><p><b>Buffer: </b>A pointer to the <span><a href="7f7ab460-848a-4053-b311-fe56b53d628a" data-linktype="relative-path">SERVER_TRANSPORT_INFO_0</a></span>
structure that describes the data.</p><p><b>Return Values: </b>The method returns 0x00000000
(NERR_Success) to indicate success; otherwise, it returns a nonzero error code.
The method can take any specific error code value, as specified in <span><a href="../ms-erref/1bc92ddf-b79e-413c-bbaa-99a5281a6c90" data-linktype="relative-path">[MS-ERREF]</a></span>
section <span><a href="../ms-erref/18d8fbe8-a967-4f1c-ae50-99ca8e491d2d" data-linktype="relative-path">2.2</a></span>.
The most common error codes are listed in the following table.</p><dl>
<dd>
<table><thead>
  <tr>
   <th>
   <p>Return value/code</p>
   </th>
   <th>
   <p>Description</p>
   </th>
  </tr>
 </thead><tbody><tr>
  <td>
  <p>0x00000000</p>
  <p>NERR_Success</p>
  </td>
  <td>
  <p>The client request succeeded.</p>
  </td>
 </tr><tr>
  <td>
  <p>0x00000005</p>
  <p>ERROR_ACCESS_DENIED</p>
  </td>
  <td>
  <p>Access is denied.</p>
  </td>
 </tr><tr>
  <td>
  <p>0x00000034</p>
  <p>ERROR_DUP_NAME</p>
  </td>
  <td>
  <p>A duplicate name exists on the network.</p>
  </td>
 </tr><tr>
  <td>
  <p>0x0000007C</p>
  <p>ERROR_INVALID_LEVEL</p>
  </td>
  <td>
  <p>The system call level is not correct.</p>
  </td>
 </tr><tr>
  <td>
  <p>0x00000057</p>
  <p>ERROR_INVALID_PARAMETER</p>
  </td>
  <td>
  <p>The parameter is incorrect.</p>
  </td>
 </tr><tr>
  <td>
  <p>0x00000008</p>
  <p>ERROR_NOT_ENOUGH_MEMORY</p>
  </td>
  <td>
  <p>Not enough storage is available to process this
  command.</p>
  </td>
 </tr></tbody></table>
</dd></dl><p>The NetrServerTransportAdd message MUST be processed in the
same way as the <span><a href="ecb0f45f-9184-439e-aa62-2735cf220f2a" data-linktype="relative-path">NetrServerTransportAddEx</a></span>
message, except that it MUST allow only level 0 (that is, <i>SERVER_TRANSPORT_INFO_0</i>).
The NetrServerTransportAddEx message is specified in section 3.1.4.23.</p><p>The server MAY<a id="Appendix_A_Target_91"></a><a aria-label="Product behavior note 91" href="ebb74ff2-abb1-4e1b-a76a-563a5cbbea9a#Appendix_A_91" data-linktype="relative-path">&lt;91&gt;</a> enforce
security measures to verify that the caller has the required permissions to
execute this call. If the server enforces these security measures and the
caller does not have the required credentials, the server SHOULD<a id="Appendix_A_Target_92"></a><a aria-label="Product behavior note 92" href="ebb74ff2-abb1-4e1b-a76a-563a5cbbea9a#Appendix_A_92" data-linktype="relative-path">&lt;92&gt;</a> fail the call.</p></div>