This tip is designed to help keep up to date with patches AFTER you have applied the latest release service pack. All the files are available from http://support.novell.com/filefinder. If a patch listed here is not available, it may have been replaced by a newer version. Often, a newer version may have a similar file name, such as when NICID156.EXE was replaced with NICID157.EXE. This tip tries to cover patches that are general in nature, and do not consider specific products installed on a server. DS patches are considered 'general' in nature.I should mention that I am finding this to be almost an impossible task as there are so many internal, beta, and field test patches being released for various products by Novell. In the past, Novell would produce a patch, and at some point release it for internal testing at Novell. Internal patches were not available for download. If they performed well in internal testing, the patch would be changed to filed test status, and the public could download it as long as you knew the file name to download. Eventually, a patch might be put onto released status, and some of them would also be put on the minimum patch list. A change in policy has been made, and Novell now allows ALL the patches to be downloaded by the public. You can keep up with the new patches at this URL:
http://support.novell.com/filefinder/Look on the beta patches link, or the 'new this week' or 'new this month' links. Be aware that beta patches may or may not cause problems as well as solve them, with the most likely issue being that something else breaks because it was not yet tested in conjunction with the beta patch.Some of the patches listed here are field test or beta status. Check the readme files carefully before installing these, or any, patches! Some patches may not be indicated depending on what software you run on your server. Some patches are very difficult to back up from.
Procedure
Before applying service packs issue this set command to dramatically speed up installation time, if you are installing over compressed files.set "dirty disk cache delay time" to 0.1 secondsNext, be sure to flag all the files on the SYS volume as Normal, to get rid of Read-Only status on files to be overwritten. This is particularly important with the NW51SP3 patch as it relies on an unzip process to copy files, and the unzip process may not overwrite read-only files, and the unzip process doesn't produce error messages. If you copied any files to the DOS partition (such as SERVER.EXE) from a CD, those files also will probably be Read-Only and need to be reflagged.Also, it is highly advisable to use this command:
LOAD CONFIG /Sbefore installing a patch. Afterwards, copy the resulting SYS:SYSTEM/CONFIG.TXT file to a PC. This will document your server somewhat, including the NLM's running. Repeat the process after installing a patch, and keep each version of CONFIG.TXT separate for later review.NetWare 5.0, with NW50SP6A.EXE installed, consider adding these patches:
1) Add "set client file caching enabled=off" to startup.ncfNetWare 5.1, with NW51SP2A installed, consider adding these patches & settings:
2a) For NetWare 5.0 - OS5PT2A.EXE
2b) For Small Business Server 5.0 - SBS5PT2A.EXE
3) NICID157.EXE
4) <latest NDS patch> - varies for DS 6, 7, 8 and 85.
5) SLPINSP3.EXE (Note, this file is the same as the previously available SLP107C.EXE)There are two additional, field test patches you may also want to install:
6) FLSYSFT3.EXE
7) WSOCK4.EXE.
WSOCK4.EXE is highly recommended - FLSYSFT3.exe is optional -in some circumstances it introduces problems.The current released Service Pack for NW 5.1 is NW51SP3.EXE -- the notes below doNetWare 5.1, with NW51SP3 installed, consider adding these patches & settings:
NOT apply to it.1) Add "set client file caching enabled=off" to startup.ncf
2) set "dirty disk cache delay time" to 0.1 seconds (If not done previously).
3) NICID157.EXE
4a) For NetWare 5.1 - OS5PT2A.EXE
4b) For Small Business Server 5.1 - SBS5PT2A.EXE
5) <latest NDS patch> - varies for DS 6, 7, 8 and 85.
6) NDP2XP7.EXE (If you use NDPS) (BUT NOT if you have applied SP3)
7) SLPINSP3.EXE (Note, this file is the same as the previously available SLP107C.EXE)
8) TCP542U.EXE - TCPIP patchThere are two additional, field test patches you may also want to install:
9) FLSYSFT3.EXE
10) WSOCK4.EXE.
WSOCK4.EXE is highly recommended - FLSYSFT3.exe is optional -in some circumstances it introduces problems.1) <latest NDS patch> - varies for DS 6, 7, 8 and 85.
2) If you desire the Dead Gateway Detection feature from the WEBREL1.EXE patch for TCPIP.NLM, the version of TCPIP.NLM in NW51SP3 (5.52u) is capable, but you need to copy the TCPCFG.NLM and TCPCON.NLM files from the WEBREL1.EXE patch in order to configure it. I have (temporarily) made the two necessary files available for download HERE. Copying these files over the SP3 versions in the SYS:SYSTEM directory should make a Dead Gateway Detection menu option show up in INETCFG, Protocols, TCP/IP.
3) As mentioned in tip #1, the SP3 patch adds SET statements for minimum and maximum receive buffers. These settings are too low for BorderManager, and may be too low for non-BorderManager servers as well. I recommend deleteing the commands from AUTOEXEC.NCF and manually setting the values to whatever is best for your server.Note: All 5.52 versions of TCPIP.NLM currently (again) have the bug where they ignore valid IP addresses ending in .0 and .255 (as if they were Class C addresses). Another patch to fix this issue is supposed to be coming out at some point.