Possible ODI Configuration Problem -- Multiple STARTNET.BAT files.
CURRENT SITUATION
- Some network driver (TCP/IP, SLIP/PPP, IPX, NFS Client) does not load when it should load.
TROUBLESHOOTING RESOLUTION
- Look in AUTOEXEC.BAT to see if the correct 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.
- Use the MS DOS command DIR \STARTNET.BAT /S
- Use the Novell DOS command TREE \STARTNET.BAT
RECOMMENDATION
- Use an explicit path to invoke STARTNET.BAT.
- When working on a problem, load the network drivers last so that you can maintain a consistent environment when unloading and reloading network drivers.
- Don't keep multiple STARTNET.BAT files on your file system.
- If you must merge multiple STARTNET.BAT files into a single batch file, rename it to something else so that the configuration programs don't overwrite your batch file.
[
Main |
Diagnostic Tools |
Serial |
Dialer |
Mailer |
Protocol Stacks
]
Novell's LAN WorkPlace Product Team
Comments to LAN WorkPlace Product Team: http://www.novell.com/corp/aaa_supt/aaa.html
All contents copyright © 1995.
Novell, Inc.
All Rights Reserved.
$Header: c:/uw2/aaa/rcs/startnet.htm 5.0.0.2 95/08/16 17:49:19 system Exp $