The Microsoft IPX/SPX-compatible protocol is installed automatically when Client for NetWare Networks is installed. You can also install this protocol to support other network clients, including Client for Microsoft Networks.
When you install the IPX/SPX-compatible protocol, Windows 95 automatically detects and sets appropriate values for the frame type, network address, and other settings. However, in some cases you might need to configure settings for this protocol manually.
If the computer has multiple network adapters, the list will contain an instance of the IPX/SPX-compatible protocol for each network adapter. You must configure each adapter with its own settings.
Property | Value |
Force even-length IPX packets | Enabled only for Ethernet 802.3 on monolithic implementations that cannot handle odd-length packets. |
Frame type1 | Specifies the frame type based on detection. This value is used for network adapters that support multiple frame types. The possible values are: Auto-detect (recommended) Ethernet 802.2 (default for NetWare 3.12 and later) Ethernet 802.3 Ethernet II Token ring Token ring SNAP |
Maximum connections | Specifies the maximum number of connections that IPX will allow. Configured dynamically. |
Maximum sockets | Specifies the maximum number of IPX sockets that IPX assigns. Configured dynamically. |
Network address | Specifies the IPX network address as a four-byte value. Configured dynamically. |
Source routing2 | Specifies the cache size to use with source routing. This parameter is used only on token ring networks, where it is used to turn on source routing. Important Cache size is specified by entry count, not byte count. The recommended value of 16 entries is the most efficient and best setting for most installations. |
1 Each time the computer starts, Windows 95 detects the frame type by sending a general RIP request in each frame format. Based on the responses received from routers, Windows 95 determines the most prevalent frame type used and sets that as the default frame type.
2 Source routing is a method of routing data across bridges. For NetWare networks, this means forwarding NetWare frames across an IBM token-ring bridge. With NDIS protocols, source routing is done by the protocol. With ODI-based protocols, source routing is configured with the network adapter driver or using the NetWare ROUTE.COM utility.
You should not need to change bindings in most circumstances. However, you can disable the bindings for a protocol if you do not want other computers using that protocol to see this computer. At least one protocol, however, must be bound to the network client for the computer to communicate with the network.
If the option is checked, it is bound to the protocol. If it is not checked, that network component is not using the IPX/SPX-compatible protocol. For more information, see "Configuring Network Adapters" earlier in this chapter.
Note Microsoft Client for NetWare Networks is always bound only to the IPX/SPX-Compatible Protocol. This network client cannot use another protocol.