readme2k.htm

学习书籍

    <strong>any</strong> response from your service provider. You
    should check the following things in order:</p>
    <ol>
        <li>Check if your broadband modem has successfully
            established a link with its counterpart. Most DSL
            modems have a <strong>Sync</strong> LED on them which
            indicates this status. If your modem has such an LED
            and it indicates that the link is down, contact your
            service provider for assistance.</li>
        <li>Check in <strong>Device Manager</strong> if the <strong>network
            adapter</strong> your broadband modem is connected to
            is enabled and working properly.</li>
        <li>Check if your network adapter is correctly configured:
            Bring up <strong>Device Manager</strong>, select the
            network adapter your broadband modem is connected to
            and click <strong>Properties</strong>. In the <strong>Properties</strong>
            window, select the <strong>Advanced</strong> tab,
            look through the options and make sure that the
            correct <strong>Line Speed</strong> and <strong>duplex
            mode</strong> is selected (most DSL modems only
            support <strong>10Mbps half duplex</strong> mode). If
            your network adapter has several connectors at the
            back, make sure the correct connector is selected,
            which is most likely <strong>Twisted Pair (TP)</strong>.</li>
        <li>Check that the cable connecting your broadband modem
            to your network adapter is properly attached and of
            the correct type. Note that broadband modems
            typically have a <strong>&quot;crossed&quot;</strong>
            connector on them, so you will need a <strong>straight</strong>
            cable to connect it <strong>directly</strong> to a
            network adapter, while you need to use a <strong>crossed</strong>
            cable <strong>or</strong> use an <strong>uplink</strong>
            port to connect it to a <strong>hub</strong> or <strong>switch</strong>.</li>
        <li>Check with your service provider whether they
            currently have a service outage.</li>
    </ol>
    <h4><a name="Trouble4"><u>6.4</u></a><u> Connection attempt
    fails with &quot;Error 797: The connection failed because the
    modem (or other connecting device) was not found.&quot;</u></h4>
    <p>This can be the result of unbinding the protocol from an
    adapter and then re-binding it, which may not have taken
    effect (see <a href="#KnownIssue2">Known Issues</a>). Follow
    these steps to put the change into effect:</p>
    <ul>
        <li>Right-click the <strong>My Network Places</strong>
            icon on your desktop and select <strong>Properties</strong>
            to bring up the <strong>Network and Dial-up
            Connections</strong> window.</li>
        <li>Go to the menu and select <strong>View</strong> then <strong>Details</strong>
            to bring up a detailed view of the network
            connections on your machine.</li>
        <li>You should find one or more <strong>Local Area
            Connection</strong> objects. Locate the one for the
            network adapter in question, right-click it and
            select <strong>Disable</strong>.</li>
        <li>Right-click the <strong>Local Area Connection</strong>
            again and select <strong>Enable</strong>.</li>
        <li>Make another connection attempt and see if it works.</li>
    </ul>
    <p>If that did not help, the <strong>dial-up connection</strong>
    you created may be configured to connect through a <strong>&quot;ghost&quot;</strong>
    dial-up device that no longer exists. Do the following to
    remedy this:</p>
    <ul>
        <li>Right-click the <strong>dial-up connection</strong>
            that failed to connect and select <strong>Properties</strong>.</li>
        <li>In the <strong>Connect using:</strong> list view,
            take a close look at the name of the dial-up device
            that is checked. A <strong>&quot;ghost&quot;</strong>
            dial-up device has the name format <strong>ISDN
            channel - </strong><em><strong>Adapter Name</strong></em><strong>
            (xx)</strong>, while a <strong>correct</strong> entry
            is of the format <strong>ISDN channel - </strong><em><strong>Adapter
            Name</strong></em>, i.e. the extra <strong>(xx)</strong>
            identifies a <strong>&quot;ghost&quot;</strong>
            device.</li>
        <li>If the checked device is indeed a <strong>&quot;ghost&quot;</strong>
            device, clear it, look through the list for the <strong>correct</strong>
            dial-up device and check that one instead.</li>
        <li>Make another connection attempt.</li>
    </ul>
</blockquote>

<blockquote>
    <h4><a name="Trouble5"><u>6.5</u></a><u> Connection attempt
    fails with &quot;Error 678: There was no answer.&quot;</u></h4>
</blockquote>

<blockquote>
    <p>First, you should check whether you can get <strong>any</strong>
    reply from your service provider with the <strong>Dial-up
    Connection Setup </strong>application provided with the
    protocol:</p>
    <ul>
        <li>Click the <strong>Start</strong> button on the
            taskbar and select <strong>Run...</strong> to bring
            up the <strong>Run</strong> dialog box.</li>
    </ul>
    <ul>
        <li>Type <strong>RASPPPOE</strong> in the edit field and
            click the <strong>OK</strong> button to run the <strong>Dial-up
            Connection Setup</strong> application.</li>
    </ul>
    <ul>
        <li>If the application quits with an error message,
            follow the advice it gives.</li>
    </ul>
    <ul>
        <li>A dialog box comes up with a combo box labeled <strong>Query
            available PPP over Ethernet Services through Adapter:</strong>
            at the top. Select the network adapter your broadband
            modem is connected to from the list. If the protocol
            is only operating on one network adapter, the box
            will be grayed out as there is no choice to make.</li>
    </ul>
    <ul>
        <li>Click the <strong>Query Available Services</strong>
            button. If an error message is displayed, continue <a
            href="#Trouble3">here</a> for further help.</li>
    </ul>
    <ul>
        <li>If the list view shows one or more offered services
            and you had tried to connect to a <strong>specific</strong>
            <strong>Service</strong> and/or <strong>Access
            Concentrator</strong>, make sure the one you had
            tried to connect to is listed. If you find your
            provider has changed the Service Name and/or the
            Access Concentrator name, simply create a new
            connection with the new name(s) or edit the <strong>Phone
            number</strong> field in your existing dial-up
            connection accordingly.</li>
    </ul>
    <ul>
        <li>Click the <strong>Exit</strong> button to quit the
            application.</li>
    </ul>
</blockquote>

<blockquote>
    <p>If you do <strong>not</strong> want to connect to a
    specific <strong>Service</strong> and/or <strong>Access
    Concentrator</strong>, make sure the <strong>Phone number</strong>
    field of your dial-up connection is really <strong>completely
    blank</strong>.</p>
    <h4><a name="Trouble6"><u>6.6</u></a><u> Connection attempt
    fails with &quot;Error 651: The Modem (or other connecting
    device) has reported an error.&quot;</u></h4>
    <p>If you have not rebooted since the installation of the
    protocol and the machine was in <strong>Standby</strong> mode
    since, this is a <a href="#KnownIssue6">known issue</a>.
    Simply click the <strong>Redial</strong> button. The second
    connection attempt will proceed without this error. You'll
    get it once each time after waking the machine from <strong>Standby</strong>
    until you reboot the machine. Then the protocol will work
    flawlessly even right after waking the machine.</p>
</blockquote>

<blockquote>
    <h4><a name="Trouble7"><u>6.7</u></a><u> Connection is
    successfully established, but some (or all) Internet websites
    do not load properly</u></h4>
    <p>This is usually a sign of an <strong>MTU problem</strong>.
    You should determine the <strong>Path MTU</strong> to the
    problem site(s) (<strong>Note:</strong> The method described
    here does not work with all servers. If you get no reply at
    all from a server or a number below <strong>548</strong>, you
    cannot determine the Path MTU to this server):</p>
    <p>Connect, open a <strong>Command Prompt</strong> and run</p>
    <blockquote>
        <p><strong>ping -f -l xxxx </strong><em><strong>Address</strong></em></p>
    </blockquote>
    <p>Where <em>Address</em> is the <strong>name</strong> or <strong>IP
    address</strong> of the server you have problems accessing.
    For <strong>xxxx</strong>, start with <strong>1464</strong>
    and <strong>lower</strong> the number until you get a reply.
    Then add <strong>28</strong> to the highest number at which
    you get a reply. The result is the <strong>Path MTU</strong>.</p>
    <p><strong>Example:</strong> You start getting replies at <strong>ping
    -f -l 1372 </strong><em><strong>Address</strong></em>. The
    Path MTU is 1372 + 28 = <strong>1400</strong> bytes in this
    case.</p>
    <p>Normally, the Path MTU to all servers should be <strong>1492</strong>.
    However, some service providers appear to have a
    configuration problem which reduces the Path MTU. If you
    determine a Path MTU lower than <strong>1492</strong> to
    several (or all) servers on the Internet, you should enable
    the <a href="#Advanced2">MTU override</a> option and set it
    to the <strong>Path MTU</strong> you determined. After that
    setting has taken effect, all sites with a Path MTU greater
    than or equal to the value you set should load properly.</p>
    <h4><a name="Trouble8"><u>6.8</u></a><u> Cannot get the
    Routing and Remote Access Service (RRAS) to work with the
    PPPoE connection</u></h4>
    <p>A common cause of this is that <strong>RRAS</strong> was <strong>incorrectly</strong>
    set up to use a <strong>network adapter</strong> for Internet
    access, which <strong>bypasses</strong> the <strong>PPP over
    Ethernet Protocol</strong>. When setting up <strong>RRAS</strong>
    with the configuration wizard, you are first presented with a
    list of network adapters in your system. <strong>Do not</strong>
    select any of these entries. Instead, look for an option to
    create an <strong>on-demand dial connection</strong> below
    and select that. A few steps later, an <strong>on-demand dial
    wizard</strong> should come up, which offers a list of <strong>dial-up
    devices</strong>, in which you should find an <strong>ISDN
    channel</strong> with the name of your network card. Select
    this device to make <strong>RRAS</strong> work with your
    PPPoE connection.</p>
    <p>If the list of <strong>dial-up devices</strong> does <strong>not</strong>
    contain the mentioned device, you may first have to <strong>enable</strong>
    it for use with <strong>RRAS</strong>. Look through the <strong>RRAS
    Management Console</strong> for a list of <strong>ports</strong>.
    This list should contain the mentioned dial-up device. You
    can right-click the device in this list and find an option to
    enable it for use with <strong>RRAS</strong>.</p>
    <h4><a name="Trouble9"><u>6.9</u></a><u> The &quot;Override
    Maximum Transfer Unit&quot; option does not remain checked</u></h4>
    <p>This option will only &quot;stick&quot; if you enter an
    MTU <strong>other than 1492</strong>. If you only check the
    checkbox, but leave the MTU at <strong>1492</strong>, the
    protocol will recognize the default value and <strong>clear</strong>
    the checkbox the next time you open the properties dialog,
    because the MTU was not actually overridden.</p>
    <h4><a name="Trouble10"><u>6.10</u></a><u> The System Event
    Log contains &quot;Received a PPPoE Session packet for an
    unknown session&quot; warnings</u></h4>
    <p>This warning merely means that the protocol received a
    PPPoE packet it could not attribute to any of its connections
    and is usually <strong>not</strong> a sign of any malfunction.
    One possible cause of this is your service provider sending
    one more packets after the connection has been terminated.
    This can also be caused by using <strong>another</strong>
    PPPoE implementation on the <strong>same</strong> machine. In
    that case, the <strong>System Event Log</strong> may end up
    being flooded with these warnings. You can prevent this by
    disabling the <strong>Log Warnings</strong> checkbox in the
    protocol's <a href="#Advanced5">Event Logging options</a>.</p>
</blockquote>

<hr>

<h3><a name="Section7"><u>7.</u></a><u> Known Issues</u></h3>

<p>This section documents known issues with the protocol.</p>

<blockquote>
    <h4><a name="KnownIssue1"><u>7.1</u></a><u> Binding/unbinding
    the protocol to/from a network adapter takes effect
    immediately and cannot be canceled</u></h4>
    <p>When you bring up the <strong>Properties</strong> of a <strong>Local
    Area Connection</strong> and toggle the checkbox next to <strong>PPP
    over Ethernet Protocol</strong>, the binding change takes
    effect <strong>immediately</strong>, i.e. it is <strong>not</strong>
    deferred until you click <strong>OK</strong> or <strong>Cancel</strong>,
    and you cannot cancel the change. This is merely annoying
    when accidentally <strong>checking</strong> the checkbo