Help and Support
 

powered byLive Search

Adding an NDIS 3.1 Protocol Does Not Add Frame Type to NET.CFG

Article ID:124848
Last Review:November 15, 2006
Revision:1.1
This article was previously published under Q124848

SYMPTOMS

The NDIS 3.1 protocol that you added to Network Setup does not function properly.

Back to the top

CAUSE

If you add an NDIS 3.1 protocol to Windows 95 and you use ODI drivers, the appropriate frame type is not added to the NET.CFG file.

Back to the top

RESOLUTION

To correct this problem, manually add the appropriate frame type to the NET.CFG file.

Back to the top

MORE INFORMATION

The Network Setup for Microsoft Windows for Workgroups 3.11 adds four frame types to the NET.CFG file:
   FRAME ETHERNET_802.2
   FRAME ETHERNET_802.3
   FRAME ETHERNET_II
   FRAME ETHERNET_SNAP
				
When you install an NDIS protocol, it can find the frame type because it is already available. On some occasions, the behavior of Windows for Workgroups version 3.11 can block access to your Novell NetWare server.

Rather than add all frame types to the NET.CFG file, Windows 95 requires that you add them manually.

Back to the top


APPLIES TO
Microsoft Windows 95

Back to the top

Keywords: 
KB124848

Back to the top

Article Translations

 

Other Support Options

  • Need More Help?
    Contact a Support professional by Email, Online or Phone.
  • Customer Service
    For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
  • Newsgroups
    Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.