Windows 2000 Server with Gateway Service for NetWare cannot reach NetWare 4.0 servers. Which configuration change typically resolves frame-type mismatches on Ethernet?

Introduction / Context:
In Novell NetWare environments, IPX/SPX networking over Ethernet can use multiple frame types (Ethernet_802.2, Ethernet_II, Ethernet_802.3, Ethernet_SNAP). For Windows 2000's Gateway Service for NetWare (GSNW) and Client Services for NetWare (CSNW) to interoperate with NetWare 4.x servers, the frame type configured on Windows must match what the NetWare servers and routers use on that segment.

Given Data / Assumptions:

• Windows 2000 Server recently added with GSNW cannot connect to NetWare servers.
• Other Windows and NetWare nodes communicate successfully.
• Ethernet media is in use; IPX is the transport protocol.

Concept / Approach:
A frame-type mismatch prevents IPX traffic from being recognized on the wire because Windows may be listening/transmitting on a different IEEE encapsulation. Configuring NWLink IPX/SPX to the correct frame type (or to auto-detect correctly) resolves adjacency and Service Advertising Protocol (SAP) visibility to NetWare servers.

Step-by-Step Solution:

Verification / Alternative check:
Use IPX/SPX diagnostic tools (for example, ipxroute, slist) to verify SAP advertisements from NetWare servers are visible on the Windows host.

Why Other Options Are Wrong:

• NWLink NetBIOS is optional and unrelated to the frame type mismatch.
• RIP for IPX and SAP Agent are routing/advertisement components; they do not fix a local L2 encapsulation mismatch.
• ‘‘None of above’’ is incorrect because correcting the frame type is the standard fix.

Common Pitfalls:
Using Auto-detect on multi-frame segments can still fail; explicitly setting the frame type often stabilizes connectivity.

Final Answer:
Configure NWLink IPX/SPX/NetBIOS Compatible Transport to use the correct Ethernet frame type