TROUBLESHOOTING

TCP/IP frame types
Most UNIX®, AS/400, or S/390 systems offer both frame types for 802.3 (Ethernet) to Ethernet V2 (DIX) and SNAP by default. You can remove the SNAP frame support if you have a routed network with Token-Ring or FDDI topologies where the router will translate the frame types (free up non-needed resources).

With Microsoft® Windows® based TCP/IP protocol services, the default frame type for 802.3 (Ethernet) network topology is v2 DIX and for Token-Ring and FDDI it is SNAP over LLC.

With Novell ODI-based TCP/IP protocol services, all systems using the TCP/IP protocol on 802.3 Ethernet should be using the same frame type. The table below lists the frame types compatible across the different LAN topologies.
LAN topology and frame servicesNovell frame typesNovell compatible frame types *Comments
Ethernet v2 (DIX)Ethernet_IINot applicableRecommended for TCP/IP
IEEE 802.3 (Ethernet)Not applicableNot applicableNot applicable
SNAPEthernet_SNAPToken-Ring_SNAP and FDDI_SNAPNot applicable
IEEE 802.5 (Token-Ring) and FDDINot applicableNot applicableNot applicable
SNAPToken-Ring_SNAP & FDDI_SNAPEthernet_SNAPRequired for TCP/IP for Token-Ring and FDDI networks
* If the bridge or router offers frame translation, other combinations may be possible.

Note If using a NetWare server as a TCP/IP router, make sure that the NetWare and IBM® Lotus® Domino™ server systems are using the same common frame type for TCP/IP and that only one frame type is being used to support the TCP/IP protocol in a flat or bridged network.

See also