050-696 · Question #37
You're implementing a network for your company from scratch. You've just completed installing the CAT-5 wiring, RJ-45 jacks, and Fast Ethernet switches that will service your network. During the…
The correct answer is A. 802.2. When no existing IPX traffic is detected on the network during OES NetWare installation, the installer defaults to binding IPX with the Ethernet_802.2 (802.2) frame type.
Question
Options
- A802.2
- B802.3
- C802.5
- DEthernet_II
- EEthernet_SNAP
How the community answered
(48 responses)- A77% (37)
- B6% (3)
- C2% (1)
- D2% (1)
- E13% (6)
Why each option
When no existing IPX traffic is detected on the network during OES NetWare installation, the installer defaults to binding IPX with the Ethernet_802.2 (802.2) frame type.
NetWare's IPX auto-detection works by listening for active IPX frames on the network segment. Because the only system on the network is the server being installed, no existing IPX traffic is present, so the installer falls back to the default frame type of Ethernet_802.2. This has been the NetWare default since version 4.x, replacing the older Ethernet_802.3 (Ethernet_RAW) default used in NetWare 2.x and 3.x.
802.3 (Ethernet_RAW) was the default IPX frame type for legacy NetWare 2.x and 3.x but is not the default for OES NetWare or any version 4.x and later.
802.5 is a Token Ring frame type and is inapplicable to a Fast Ethernet environment built with CAT-5 cabling and RJ-45 connectors.
Ethernet_II is primarily used for TCP/IP encapsulation and is not the default frame type selected when IPX auto-detection finds no existing traffic.
Ethernet_SNAP is not the default IPX frame type; it is used for specific protocol encapsulation and is not automatically chosen when no traffic is detected.
Concept tested: Default IPX frame type auto-detection in OES NetWare
Topics
Community Discussion
No community discussion yet for this question.