Troubleshooting Connection Problems with Microsoft DLC

If you encounter problems using the real-mode Microsoft DLC protocol, check the following items:

• When adding the Microsoft DLC protocol, make sure that there is only one net start entry in AUTOEXEC.BAT. Setup adds an entry for Microsoft DLC, even if an entry already exists. Also, make sure that AUTOEXEC.BAT is configured properly, as described in "Installing and Configuring Real-Mode Microsoft DLC" earlier in this chapter.
• Do not make direct entries or changes in PROTOCOL.INI for Microsoft DLC. Instead, make all changes in the Advanced properties for Microsoft DLC by using the Network option in Control Panel. If you make changes directly in PROTOCOL.INI, then the next time you change any values by using the Network option in Control Panel, all settings in PROTOCOL.INI for Microsoft DLC will be overwritten.
• Some terminal emulation applications use TSRs to communicate with the Microsoft DLC protocol. If your emulation application uses a TSR that runs from AUTOEXEC.BAT, then make sure that the entry for the TSR still exists (usually, the TSR entry occurs after the msdlc and net start lines). Windows 95 Setup removes or comments out many TSRs.
• The option named Set This Protocol To Be The Default Protocol in the Advanced properties for Microsoft DLC does not provide any functionality. This option should not be checked, because Microsoft DLC does not use LANA settings.
• Real-mode Microsoft DLC is an NDIS 2 protocol, so the network adapter must have an NDIS 2-compatible network adapter driver for use with Windows 95. Windows 95 includes many compatible drivers, but some Windows 95 drivers for certain PCI and PCMCIA cards do not have a corresponding NDIS 2 driver to allow loading real-mode Microsoft DLC.