How to Capture Modem Commands in Windows NT 4.0

ID: Q162694

The information in this article applies to:

SUMMARY

Interrogating modem commands sent from the RAS client or server can be useful troubleshooting tools for diagnosing communications problems.

In Windows NT 3.51, the method for capturing modem commands is to enable the Device.log file. For additional information, please see the following article in the Microsoft Knowledge Base:

ARTICLE-ID: Q102782
TITLE : Troubleshooting RAS Problems and Using the Device.log File
However, in Windows NT 4.0, when you use UniModem, the Device.log no longer captures modem commands.


MORE INFORMATION

You can still use the Device.log in Windows NT 4.0 to troubleshoot problems with Switch.inf and script files. To troubleshoot modem commands in Windows 4.0, perform the following steps:

  1. Open Control Panel Modems.


  2. Select the modem you want to create a log file for.


  3. Click Properties.


  4. Click the Connection tab.


  5. Click Advanced.


  6. Click to select the "Record a log file" check box. You do not need to restart your computer for this setting to take effect.


The log file will be created in the %Systemroot% directory, with a name of Modemlog_<model>.txt, where <model> is your modem's model. For example, a USR Sportster modem will generate a text file with a name like ModemLog_Sportster 28800-33600 External.txt.

Additional query words: modemlog.txt prodnt remote access service 


Keywords          : kbusage ntras NTSrvWkst 
Version           : WINNT:4.0
Platform          : winnt 
Issue type        : kbhowto

Last Reviewed: February 4, 1999