DOCUMENT:Q102782  20-AUG-1993  [W_NT]
TITLE   :Troubleshooting RAS Problems and Using the DEVICE.LOF File
PRODUCT :Windows NT
PROD/VER:3.10
OPER/SYS:WINDOWS
KEYWORDS:

----------------------------------------------------------------------
The information in this article applies to:
 
 - Microsoft Windows NT operating system, version 3.1
 - Microsoft Windows NT Advanced Server, version 3.1
----------------------------------------------------------------------
 
If you experience problems connecting to Remote Access Services (RAS),
try to identify the specific problem by doing the following:
 
1. If you are receiving error messages, choose Help and follow the
   suggested steps.
 
2. Check to see if you can access your modem from the Terminal
   program. If the modem works with Terminal, do the following:
 
   a. Make sure your modem is on the list of modems supported by
      Windows NT Remote Access. (See the Windows NT Hardware
      Compatibility List.)
 
   b. Make sure you have the correct cabling required by Remote
      Access. For more information on RAS cabling requirements, check
      Remote Access Help. (Search on: Cabling Requirements.)
 
3. Enable device logging on Remote Access by doing the following:
 
   a. Start Registry Editor.
 
   b. Go to the following subkey:
 
         hkey_local_machine\system\currentcontrolset
         \services\remoteaccess\parameters
 
   c. If the key does not exist, choose Add Value from the Edit menu.
 
   d. For the following fields, enter these values:
 
         Value Name: logging
         Data Type: REG_DWORD
         String: 1
 
   e. Stop and start Remote Access Service and Phone Book to enable
      the DEVICE.LOF file.
 
   The RAS DEVICE.LOF file will be created in the SYSTEM32\RAS
   subdirectory. See the next section for information on using
   DEVICE.LOF.
 
Using DEVICE.LOF
----------------
 
The DEVICE.LOF file contains the strings that are sent to and received
from the serial device (either a modem or an X.25 PAD). DEVICE.LOG is
useful for troubleshooting problems with serial devices, and for
testing new entries added to the MODEM.INF or PAD.INF files.
 
NOTE: You may want to view the DEVICE.LOF file in a text editor that
can display both character and hexadecimal output as some of the
information will not be printable characters. Also, DEVICE.LOF
contains a carriage return (h0D) and line feed (h0A) byte at the end
of each line. These bytes are provided by the program that creates the
DEVICE.LOF file and do not represent information communicated from or
to the device.
 
The DEVICE.LOF file contains:
 
 - The command string sent to the device.
 - The echo of the command.
 - The response from the device.
 - The connect and carrier bps (bits per second) (modems only).
 
For each bps pair, there may be several sets of command, echo, and
response data. If the command and echo (on a modem) do not match, a
hardware error message will be generated.
 
The Connect string from the modem (the last response string from the
modem when a connection is established) will normally contain the
connect bps, the carrier bps, or both. If the Connect string contains
both, the connect bps and the carrier bps lines will give the values
from the Connect string. If the Connect string does not have one of
the bps values, a best estimate of the actual bps value is given. Both
of these values are used by RAS; for this reason, RAS initializes the
modem to include both values in its response.
 
NOTE: "Connect bps" refers to the DTE (data terminal equipment) speed
of the modem. This information is required by RAS. The "carrier bps"
refers to the DCE (data communication equipment) or modem-to-modem
speed. This value is not used internally by RAS, but is displayed if
available.
 
If your modem cannot return both the DTE and DCE speeds, configure it
to at least return the DTE speed. Without knowledge of the DTE speed,
RAS cannot reset the port appropriately, thus resulting in
transmission errors.
 
Additional reference words: 3.10
KBCategory:
KBSubCategory: NTRMT

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.  MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.  SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1993.