RAS Errors in Dial Up Networking

I have been recieving several RAS Errors in Dial Up Networking i.e. "RAS Error 0". I have searched the MS Website but cant find anything on them.  
Would anybody have a listing of these Errors ??
Who is Participating?
The file raserror.h defines RASBASE+0 as being "PENDING".
<a href="http://premium.microsoft.com/msdn/library/tools/wcesdk/appendix_5.htm">For the link on the MS site.</a>

PSS ID Number: Q148499
Article last modified on 03-18-1996

The information in this article applies to:
 - Microsoft Windows 95
 - Microsoft Plus! for Windows 95
This article contains information describing technical aspects and the
usage of the SLIP and PPP line-control protocols with Dial-Up Networking.
                            MORE INFORMATION
Microsoft's Windows 95 implementation of the SLIP and PPP protocols is
based on the standards set forth by the Internet Engineering Task Force
(IETF). These standards are contained in technical documents called
Requests For Comments (RFC) and are widely available on the Internet. By
adhering closely to these standards, connectivity to other SLIP or PPP
servers similarly designed is virtually guaranteed.
Brief outlines of the protocols themselves are provided below, with
information pertinent to their operation with Windows 95 following.
If more information on either protocol is required, the following RFCs
are good sources of information:
   RFC-1055: SLIP Implementation
   RFC-1661: PPP Implementation
   RFC-1700: Internet Assigned Numbers
The following URL contains the RFC Index, which is constantly updated, and
contains links to all the RFC documents:
Serial Line Internet Protocol - SLIP
SLIP can be defined as an encapsulation method for transmitting IP packets
over a serial connection. From its creation until the present time, the
recommended method for implementing SLIP has remained a de facto standard.
Packet Framing:
   Special Characters
      END (C0h,192d) Signals the end of a packet's transmission.
      ESC (DBh,219d) Special character used when characters
                      duplicate the END character.
   NOTE: If a data byte has the same value as the END character, a
   two-byte sequence of ESC and DCh is sent instead. If a data
   byte is the same as an ESC character, a two-byte sequence of ESC
   and DDh is sent instead.
Packet Size:
   IP (headers and data) + transport protocol headers - framing
   characters <= 1006 bytes
Other Information
SLIP does not have the ability to transmit more than one network protocol
at a time. Its architecture does not provide a method of differentiating
between network protocols. TCP/IP is the protocol that is typically used
with SLIP, which made it ideal for connecting a remote computer to the
Internet using a dial-up SLIP server. However, because TCP/IP is the only
network protocol SLIP can carry makes it of limited use in other
SLIP also provides no mechanisms for error correction. It relies on
the hardware used to make the connection, and the error-correction
capabilities of TCP/IP to determine if a packet's information is bad
and needs to be resent.
There are no compression algorithms built into SLIP. There are variants of
SLIP (for example, CSLIP, or Compressed SLIP) that provide some degree of
streamlining, but the majority of SLIP connections do not use compression.
Point to Point Protocol - PPP
PPP can be defined as an encapsulation method for transmitting multiple-
protocol datagrams over point-to-point links. It is more robust and
versatile than its predecessor, SLIP. PPP provides a data-link layer,
the Link Control Protocol (LCP), for setting up, configuring, and
monitoring the connection to ensure that the connection remains reliable.
In addition, by using Network Control Protocols (NCPs), different network-
layer protocols can be used dynamically.
Packet Framing:
   Protocol Field (xxxxxxxx,yyyyyyyy)
      The Protocol field is one or two octets, and its value
      identifies the datagram encapsulated in the Information field
      of the packet. The field is transmitted and received most-
      significant-octet first.
   Information Field (0 - n[xxxxxxxx])
      The Information field is zero or more octets. The Information
      field contains the datagram for the protocol specified in the
      Protocol field. The maximum length for the Information field,
      including padding, but not including the Protocol field, is
      termed the Maximum Receive Unit (MRU), which defaults to 1500
      octets. By negotiation, consenting PPP implementations may
      use other values for the MRU.
   Padding (0 - n[xxxxxxxx])
      On transmission, the Information field may be padded with an
      arbitrary number of octets up to the MRU.  It is the
      responsibility of each protocol to distinguish padding octets
      from real information.
Link Negotiation:
   Phase I
      Each side exchanges LCP packets that test the integrity of
      the link and configure the operational parameters the
      connection will use at the data-link layer.
   Phase II
      Each side negotiates for and participates in user
      authentication. This phase is only a suggestion to the
      standard implementation of a point-to-point protocol, and as
      such, may not be included in all implementations.
   Phase III
      Each side negotiates for the set of NCPs that will be used. For
      each different type of datagram to be exchanged (IPX, IP, and so
      on), an NCP must be configured and operational. This provides the
      method for transmission of network-layer information.
Other Information
The most important thing to remember about PPP is that it can support
multiple network protocols simultaneously, or any individual protocol by
itself. In addition, it provides error correction and compression of a
very sophisticated nature. While it has more overhead and additional
information, the compression and error control make PPP much faster than
SLIP and far more reliable.
Using SLIP and PPP with Windows 95
Windows 95 automatically supports dialing into servers that allow PPP,
RAS, or NRN (NetWare Connect) connections. SLIP support must be installed
separately. If you are using the CD-ROM version of Windows 95, you can
install SLIP support (along with scripting support) by following these
1. In Control Panel, double-click Add/Remove Programs.
2. On the Windows Setup tab, click Have Disk.
3. In the Copy Manufacturer's Files From box, enter the following line
   and then click OK
   where <drive> is the CD-ROM drive containing the Windows 95 CD-ROM.
4. Click OK.
5. Click "SLIP and Scripting for Dial-Up Networking."
6. Click Install.
After you install SLIP support, SLIP and CSLIP are available as additional
server types when you specify the type of server being dialed into.
NOTE: If you do not have the CD-ROM version of Windows 95, see the
following articles in the Microsoft Knowledge Base for information about
obtaining SLIP support:
   ARTICLE-ID: Q135315
   TITLE     : CD-ROM Extras for Microsoft Windows 95 Upgrade
   ARTICLE-ID: Q146238
   TITLE     : Microsoft Windows 95 Service Pack 1 Admin.doc File
              (3 of 3)
When you are using SLIP, you are limited to the use of the TCP/IP
protocol. In addition, in the Dial-Up Networking connectoid, the Enable
Software Compression and Require Encrypted Password options will not be
available. These restrictions are limitations of the SLIP protocol, as
noted previously.
When you are using PPP, you can use the full flexibility of Dial-Up
Networking. You can select NetBEUI, IPX/SPX, TCP/IP, or any combination
thereof. The compression and password-encryption options are also
available. However, if the dial-up server does not support either of these
options, they will not be used. The use of these options is negotiated
during the second phase of the PPP connection.
With the addition of Microsoft Plus! for Windows 95, a computer running
Windows 95 can be used as a dial-up server. However, incoming SLIP
connections are not supported, as Windows 95 is not designed to route
TCP/IP packets. Incoming PPP connections using NetBEUI or IPX/SPX are
supported, and offer the remote computer access to the host's resources.
If the host computer is connected to a LAN, the remote computer can gain
access to network resources, and even be validated by a Microsoft Windows
NT or Novell NetWare server.
KBCategory: kbnetwork kbref
KBSubcategory: win95 winplus wincomm dun
Additional reference words: 95
Copyright Microsoft Corporation 1996.


PenfoldAuthor Commented:
Theh95 please read the question. I have already searched the MicroSoft Website, and am looking for a listing of known RAS Errors.
Technet CD is a posibble source but it's microssoft again. I've had a look around and I can't find error 0 either.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.