{ 0x00ea0001, 0xc0000016 },
        { 0x08bf0002, 0xC0000193 },
        { 0x08c00002, 0xC0000070 },
        { 0x08c10002, 0xC000006f },
        { 0x08c20002, 0xC0000071 },
    };

    /* These aren't really used by jCIFS -- the map above is used
     * to immediately map to NTSTATUS codes.
     */
    static final String[] DOS_ERROR_MESSAGES = {
        "The operation completed successfully.",

        }, {
            0x08c00002, 0xC0000070
        }, {
            0x08c10002, 0xC000006f
        }, {
            0x08c20002, 0xC0000071
        },
    };

    /*
     * These aren't really used by jCIFS -- the map above is used
     * to immediately map to NTSTATUS codes.
     */
    static final String[] DOS_ERROR_MESSAGES = {

        "The security ID structure is invalid.", "The file system is full.", "All pipe instances are busy.", "All pipe instances are busy.",
        "The pipe state is invalid.", "All pipe instances are busy.", "No process is on the other end of the pipe.", "The pipe is being closed.",

    protected int attributes;


    /**
     * This filter can be considerably more efficient than other file filters
     * as the specified wildcard and attributes are passed to the server for
     * filtering there (although attributes are largely ignored by servers
     * they are filtered locally by the default accept method).
     * 
     * @param wildcard
     * @param attributes
     */

 * "The .NET Developer's Guide to Windows Security" (which is also
 * available online).
 * <p>
 * Direct ACEs are evaluated first in order. The SID of the user performing
 * the operation and the desired access bits are compared to the SID
 * and access mask of each ACE. If the SID matches, the allow/deny flags
 * and access mask are considered. If the ACE is a "deny"
 * ACE and <i>any</i> of the desired access bits match bits in the access

     * <tt>NtlmPasswordAuthentication</tt> object against the domain controller
     * specified by the <tt>UniAddress</tt> parameter. If the credentials are
     * not accepted, an <tt>SmbAuthException</tt> will be thrown. If an error
     * occurs an <tt>SmbException</tt> will be thrown. If the credentials are
     * valid, the method will return without throwing an exception. See the
     * last <a href="../../../faq.html">FAQ</a> question.
     * <p>

             *
             * This is where we recursively invoke the provided andx smb
             * object to write it's parameter words and bytes to our outgoing
             * array. Incedentally when these andx smbs are created they are not
             * necessarily populated with header data because they're not writing
             * the header, only their body. But for whatever reason one might wish

    /**
     * Guess called name to try for session establishment. These
     * methods are used by the smb package.
     * 
     * @return guessed name
     */
    String firstCalledName ();


    /**
     * Guess next called name to try for session establishment. These
     * methods are used by the smb package.
     * 
     * @param tc
     * 
     * @return guessed name
     */

import java.net.UnknownHostException;

/**
 * This class will allow a Java program to read and write data to Named
 * Pipes and Transact NamedPipes.
 *
 * <p>There are three Win32 function calls provided by the Windows SDK
 * that are important in the context of using jCIFS. They are:
 *
 * <ul>
 * <li> <code>CallNamedPipe</code> A message-type pipe call that opens,
 *      writes to, reads from, and closes the pipe in a single operation.

 * overwriting properties from the file. Thus properties provided on the
 * commandline with the <code>-Dproperty.name=value</code> VM parameter
 * will override properties from the configuration file.
 * <p>
 * There are several ways to set jCIFS properties. See
 * the <a href="../overview-summary.html#scp">overview page of the API
 * documentation</a> for details.
 */

public class Config {

public static int socketCount = 0;