TCPIP-32 on Client with IPXODI Can Only Ping Itself (135462)
The information in this article applies to:
- Microsoft TCP/IP-32 for Windows for Workgroups 3.11
- Microsoft TCP/IP-32 for Windows for Workgroups 3.11a
- Microsoft TCP/IP-32 for Windows for Workgroups 3.11b
- Microsoft Windows 95
This article was previously published under Q135462 SYMPTOMS
After you install Microsoft's TCP/IP-32 stack on your computer running
Windows for Workgroups 3.1x and the NetWare IPXODI real-mode stack, the
client can PING itself, but attempts to PING other IP addresses result in
"Request timed out" messages.
CAUSE
The NetWare client file, NET.CFG, does not contain entries for all of the
four ethernet frame types or the two token-ring frame types.
RESOLUTION
Open the NetWare file, NET.CFG, with a text editor. Under the Link Driver
section heading make sure all four frame types are specified. Make sure the
first frame type listed is the primary frame type you use to connect to
NetWare servers. For example:
- If you have an Ethernet network:
Link Driver NE2000
Frame Ethernet_802.2
Frame Ethernet_802.3
Frame Ethernet_II
Frame Ethernet_SNAP
PORT 320
INT 5
MEM D0000
NetWare DOS Requester
FIRST NETWORK DRIVE = F
NOTE: By default Microsoft's TCP/IP-32 stack uses the ETHERNET_II Frame
to communicate on the network.
-or-
- If you have a Token-ring network:
Link Driver TOKEN
Frame Token-ring
Frame Token-ring_SNAP
PORT 320
INT 5
MEM D0000
NetWare DOS Requester
FIRST NETWORK DRIVE = F
| Modification Type: | Major | Last Reviewed: | 10/13/2003 |
|---|
| Keywords: | KB135462 kbAudDeveloper |
|---|
|