Possible Configuration ODI Problem -- Multiple NET.CFG files
CURRENT SITUATION
- The network drivers generate visible and audible errors while loading; or
- The network drivers behave in an unexpected manner after successfully loading.
POSSIBLE CAUSES
You are using LAN WorkPlace with the NetWare Client and the two configurations are not integrating correcting.
TROUBLESHOOTING RESOLUTION
- Use the DOS command lsl -S (capital S) to find your active NET.CFG.
- Look in AUTOEXEC.BAT to determine the STARTNET.BAT is being called:
- LAN WorkPlace uses \NET\BIN\STARTNET.BAT.
- NetWare uses \NWCLIENT\STARTNET.BAT.
- If your AUTOEXEC.BAT calls the STARTNET.BAT on the DOS PATH (STARTNET.BAT is invoked without an explicit path), do one of
the following to determine if you have multiple STARTNET.BAT files.
- With MSDOS, use the command: DIR \STARTNET.BAT /S
- With Novell DOS, use the command: TREE \STARTNET.BAT
- Make sure the NET.CFG reported by LSL.COM is the NET.CFG that you should be using.
RECOMMENDATION
- Merge multiple NET.CFGs into one NET.CFG file.
- Don't keep multiple NET.CFGs on your file system.
- Make sure that STARTNET.BAT invokes LSL.COM with the command line lsl /C=NET.CFG (using the full path to NET.CFG).
[