Redial on Link Failure Problems After Upgrade

View products that this article applies to.

This article was previously published under Q153376

Expand all | Collapse all

SYMPTOMS

If you upgrade Microsoft Windows NT 3.51 to Windows NT 4.0, the Redial On Link Failure option may not work properly.

Back to the top

This behavior was observed in builds through 1345.03 (RC1) and may occur in subsequent builds of Microsoft Windows NT 4.0. After the upgrade from 3.51, the new TAPI API set is not used for modems already defined in Remote Access Service (RAS).

Instead, the older style components are left in place and the Modem.inf file is used instead of UNIMODEM. Without using UNIMODEM, the TAPI API set may not monitor the status of the connection properly. RAS may attempt to redial if a connection attempt fails, but may not redial on failure of an established connection.

Back to the top

RESOLUTION

Click the Start button, point to Settings, and click Control Panel. Double-click the Network icon.
Click the Services tab and select Remote Access Service.
Click Remove, and then click OK.
Restart the computer.
Rename the System32\Ras directory to System32\Ras.old.
Click the Start button, point to Settings, and click Control Panel. Double-click the Network icon.
Click the Services tab, and then click Add.
Select Remote Access Service to re-install RAS, and then click OK.
Restart the computer.
Copy the phonebook files from System32\Ras.old to the System32\Ras directory.
Make any other necessary configuration changes to RAS as required.

Back to the top