Many problems can occur if Pathway is not properly configured. Here are some things to check in case of errors, slowness and lockups. Please be aware that some specific files may not be used; i.e., ODI installation does not use protocol.ini.
Installing
- ODI: lsl.com and a *.com network card driver must be loaded.
- NDIS: Use either the *.mac or *.dos driver and the protocol.ini supplied by the network card manufacturer.
- PDS: This is a packet driver. It’s often unstable in Windows, so not recommended.
- Dedicated: Only use a dedicated driver for one of the listed network cards. Even so, we recommend ODI or NDIS instead.
- ASI: This is used by token ring networks. It is similar to a normal NDIS installation and just as easy to troubleshoot.
Winsock.dll
There should be only one. Any others will need to be renamed. Make sure the winsock.dll you use belongs to the TCP/IP or transport layer in use.
The -I: option is the interrupt of the network card or COM port
Run the network card setup utility to verify the interrupt of the card. Also, verify that there are no conflicts with this IRQ and other hardware.
pwconfig.exe -N: should be different than the network card
This is an interrupt vector or software interrupt. The default for Wollongong is 65. Valid numbers are 60-66. Most network cards are on 60 or 61. Recommended numbers are 63, 65 and 66.
Check for errors on boot. Concentrate on the error description, not the number. The brief description tells more than the number. If a technician can find the error number, chances are it will be the same description. Do not worry if there are two error numbers and one description. They will be related.
NET.CFG syntax
Order and spacing are critical. In general, the order should be: “Wollongong” group, “Link driver” section, “Wollongong” group, and then extra additions such as buffers, Novell DOS requesters, etc. Make sure the frames are correct.
PROTOCOL.INI
Verify the ndis.exe -d: argument is pointing to the right [driver] section. You may also need to verify the protocol.ini file being used. You may find copies in multiple places: C:\Windows, C:\Pathway\Lanman, etc.
In Windows for Workgroups, make sure Windows has loaded the right network driver and that NetBEUI is running correctly.
IP addresses
Check to see if it is a duplicate or otherwise incorrect. Errors that occur from this are PC lockups, lost connection, and read/write errors.
A simple way to check for duplicate IP addresses is to change the PC’s address, then ping the old address.
Subnet mask bits
Make sure they are the same as other computers on the subnet. This will also cause PC lockups, lost connections and read/write errors.
STAT.EXE
Run this at a DOS prompt. Three parameters need to be checked:
- stat 2: Physical address of the network card. If it’s all zeroes, Pathway is not loaded or not loaded properly. Pathway needs to see the card, unless you are using PPP or SLIP.
- stat 3: Resolved IP addresses. If this reports no resolved addresses, the TCP stack could still be the problem. If there is a resolved address and there is still no reply from the ping, the problem is on the other end of the connection, not the PC.
- stat 4: This gives the local IP address and subnet mask bits.
Patch
Download the updated PCHRUN.EXE. Replace the existing copy on the PC with the new file.
Update the network card driver
Get latest drivers for network card from the manufacturer. Generally, the manufacturer’s website will have the files to download.
Watch for cards that do not support multiple protocols
Some older network cards only support one protocol at a time; e.g., IPX or NDIS. This is not common. If either protocol loads and connects properly when run alone, but combined one or the other fails, then it does not support multiple protocols.
Adjust Windows
See our other documents on NDIS, ODI and Windows 95 configuration.
This entry was posted
on Friday, May 11th, 2007 at 9:09 am and is filed under DOS, TCP/IP.
You can follow any responses to this entry through the RSS 2.0 feed.
Both comments and pings are currently closed.
