<div class="content" name="NetrServerTransportDel" uuid="4f8f58af-efa3-420a-953f-cbcfc8d2e3f3"><p>The NetrServerTransportDel method unbinds (or disconnects)
the transport protocol from the <a href="1709f6a7-efb8-4ded-b7ae-5cee9ee36320#gt_434b0234-e970-4e8c-bdfa-e16a30d96703" data-linktype="relative-path">server</a>. If this method
succeeds, the server can no longer communicate with <a href="1709f6a7-efb8-4ded-b7ae-5cee9ee36320#gt_60e0e1fa-66fe-41e1-b5e3-ceab97e53506" data-linktype="relative-path">clients</a> by using the
specified transport protocol (such as TCP or XNS).</p><dl>
<dd>
<div><pre> NET_API_STATUS NetrServerTransportDel(
   [in, string, unique] SRVSVC_HANDLE ServerName,
   [in] DWORD Level,
   [in] LPSERVER_TRANSPORT_INFO_0 Buffer
 );
</pre></div>
</dd></dl><p><b>ServerName: </b>An <a href="5f8329ee-1965-4ea1-ad35-3b29fbb63232" data-linktype="relative-path">SRVSVC_HANDLE (section 2.2.1.1)</a>
pointer that identifies the server. The client MUST map this structure to an
RPC binding handle (see <a href="https://go.microsoft.com/fwlink/?LinkId=89824" data-linktype="external">[C706]</a>
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 SHOULD be zero and MUST be ignored on receipt.</p><dl>
<dd>
<table><thead>
  <tr>
   <th>
   <p>Value</p>
   </th>
   <th>
   <p>Meaning</p>
   </th>
  </tr>
 </thead><tbody><tr>
  <td>0</td>
  <td>The buffer is of type SERVER_TRANSPORT_INFO_0.</td>
 </tr></tbody></table>
</dd></dl><p><b>Buffer: </b>A pointer to the
SERVER_TRANSPORT_INFO_0 structure that contains information about the
transport.</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 <a href="../ms-erref/1bc92ddf-b79e-413c-bbaa-99a5281a6c90" data-linktype="relative-path">[MS-ERREF]</a>
section <a href="../ms-erref/18d8fbe8-a967-4f1c-ae50-99ca8e491d2d" data-linktype="relative-path">2.2</a>.
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>0x00000000 NERR_Success</td>
  <td>The client request succeeded.</td>
 </tr><tr>
  <td>0x00000005 ERROR_ACCESS_DENIED</td>
  <td>Access is denied.</td>
 </tr><tr>
  <td>0x00000057 ERROR_INVALID_PARAMETER</td>
  <td>The parameter is incorrect.</td>
 </tr><tr>
  <td>0x00000008 ERROR_NOT_ENOUGH_MEMORY</td>
  <td>Not enough storage is available to process this command.</td>
 </tr></tbody></table>
</dd></dl><p>The NetrServerTransportDel message MUST be processed in the
same way as the <a href="6f4faa22-fb0d-474f-9434-09b1ce5c1a95" data-linktype="relative-path">NetrServerTransportDelEx</a>
message, except that it MUST allow only level 0 (that is,
SERVER_TRANSPORT_INFO_0). The processing for this message is specified in
section 3.1.4.26.</p><p>The server MAY<a id="Appendix_A_Target_98"></a><a aria-label="Product behavior note 98" href="ebb74ff2-abb1-4e1b-a76a-563a5cbbea9a#Appendix_A_98" data-linktype="relative-path">&lt;98&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_99"></a><a aria-label="Product behavior note 99" href="ebb74ff2-abb1-4e1b-a76a-563a5cbbea9a#Appendix_A_99" data-linktype="relative-path">&lt;99&gt;</a> fail the call.</p></div>