This article was previously published under Q162694
This article has been archived. It is offered "as is" and will no longer be updated.
Interrogating modem commands sent from the RAS client or server can beuseful troubleshooting tools for diagnosing communications problems.
In Windows NT 3.51, the method for capturing modem commands is to enablethe Device.log file. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
102782 Troubleshooting RAS Problems and Using the Device.log File
However, in Windows NT 4.0 and Windows 2000, when you use UniModem, the Device.log no longercaptures modem commands.
You can still use the Device.log in Windows NT 4.0 and Windows 2000 to troubleshoot problemswith Switch.inf and script files.
Windows NT 4.0
To troubleshoot modem commands in Windows4.0, perform the following steps:
From the Start menu, point to Settings and click Control Panel, then double-click Modems.
Click the modem you want to create a log file for.
Click the Connection tab.
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% folder, with a name ofModemlog_model.txt, where model is your modem's model. For example, aUSR Sportster modem will generate a text file with a name likeModemLog_Sportster 28800-33600 External.txt.
To troubleshoot modem commands in Windows 2000, perform the following steps:
From the Start menu, point to Settings and click Control Panel. Double-click Phone and Modem Options.
Click the Modems tab.
Select the modem for which you want to view the log file.
Click the Diagnostics tab.
Click View Log. NOTE: This may be unavailable if the modem has never been used.
The log file will be created in the %Systemroot% folder, with a name of ModemLog_model.txt, where model is your modem's model. For example, a Blatzheim Starline 28k8 modem will generate a text file with a name like ModemLog_Blatzheim Starline 28k8.txt.