How to Capture Modem Commands in Windows NT 4.0 and Windows 2000

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, click the article number below to view the article in the Microsoft Knowledge Base: However, in Windows NT 4.0 and Windows 2000, when you use UniModem, the Device.log no longer captures modem commands.

You can still use the Device.log in Windows NT 4.0 and Windows 2000 to troubleshoot problems with Switch.inf and script files.

Windows NT 4.0

To troubleshoot modem commands in Windows 4.0, perform the following steps:

1. From the Start menu, point to Settings and click Control Panel, then double-click Modems.
2. Click the modem you want to create a log file for.
3. Click Properties.
4. Click the Connection tab.
5. Click Advanced.
6. 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 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.

Windows 2000

To troubleshoot modem commands in Windows 2000, perform the following steps:

1. From the Start menu, point to Settings and click Control Panel. Double-click Phone and Modem Options.
2. Click the Modems tab.
3. Select the modem for which you want to view the log file.
4. Click Properties.
5. Click the Diagnostics tab.
6. 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.