Filter
Top Products
114
CHAPTER 4
Make sure your \WINDOWS\PROTOCOL.INI has proper bindings. The
MS$NDISHLP and NETBEUI sections should have a
BINDINGS=M32AMAC. Chances are, the binding statement is wrong. See
the sample PROTOCOL.INI file.
WFW works the first time I boot the machine, but after a warm
boot, it fails to see other machines.
Turn off the power to shut down the machine and do a COLD BOOT. See if
this fixes the problem.
When using WFW and ODI support for NetWare, I was able to
login before I installed the WFW support for ODI. Now I can’t
see the server anymore.
You were probably using frame ethernet_802.2 for the IPXODI to connect
to NetWare. The WFW network setup program shuffles the NET.CFG
frame types such that ethernet_802.3 becomes the first. To solve this
problem, just shuffle them back and make sure the first frame type is the
one your IPXODI needs to use; in this case it is ethernet_802.2.
When I do the NetWare ODI stack, VLM says “No server found.”
Or, when I use NDIS2, everything loads but I can’t see other
machines on the network.
1 If using NetWare, try changing the first frame type in the
C:\NWCLIENT\NET.CFG file. Make sure you know what frame
type your NetWare server supports. IPX binds to the first frame
type in the NET.CFG file.
2 Try without loading Card and Socket Services, and leave only the
PRO/100 CardBus adapter in the machine with no other cards in
there. This is always a good troubleshooting technique to create a
bare-bones environment.
3 Change INT setting in the C:\NWCLIENT\NET.CFG file. Some
machines use INT 5 for sound cards. Try changing the INT to 10
or 11 or 15.
If using ODI, use INT 11 in C:\NWCLIENT\NET.CFG.
If using NDIS2, use INT=11 in C:\WINDOWS\PROTOCOL.INI.
4 Check and make sure that the memory used by the PRO/100
CardBus adapter is excluded from the EMM386.EXE line in the
CONFIG.SYS.