Search
Support & Downloads
Networking Connectivity
Token Ring Adapters
Driver not a Promiscuous Mode Driver

Symptom:
LANalyzer* reports TokenExpress™ adapter driver not a promiscuous mode driver.

Description:
LANalyzer only works with ODI drivers. Windows* 95 uses an NDIS driver. NDIS drivers are not certified by Novell.

Solution:
If available, replace VMLID.NLM in the Client32 directory with the updated version from the LANalyzer diskette. Or, download TE16DISK.EXE from Intel's Online Services and Client 32 from Novell . Install both under Windows* 95 for ODI driver support, which will now work with LANalyzer.

Note: If you switch network drivers or reinstall NetWare* Client 32, the VMLID.NLM file might revert to an older version. Copy VMLID.NEW to VMLID.NLM and restart your system. If you are running on a token ring network and using an NDIS driver, you cannot capture your own workstation's transmitted packets from protocols bound to the NDIS driver (for example, Microsoft TCP/IP).

Microsoft* NDIS Drivers:
The NDIS drivers listed below require the VMLID.NLM file, which is included in Novell NetWare Client 32 for Windows 95. For your convenience, we include a new version of VMLID.NLM on LANalyzer for Windows 2.2 Diskette 3. If you use any of the NDIS drivers listed here, be sure to use the version of VMLID.NLM provided on Diskette 3.

  • EE16.SYS
  • EE16MINI.SYS
  • MDGMPORT.SYS
  • NE2000.SYS
  • SMC8100W.VXD

   This link will take you off of the Intel Web site. Intel does not control the content of the destination Web Site.

This applies to:
TokenExpress™ 16/p Adapter
TokenExpress™ EISA 16/4 Adapter
TokenExpress™ EISA 32 Adapter
TokenExpress™ MCA Adapter



Solution ID: CS-012022
Date Created: 31-May-2004
Last Modified: 23-Oct-2006
Back to Top