home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Encyclopedia 96-1
/
novell-nsepro-1996-1-cd2.iso
/
download
/
netware
/
41rtr2.exe
/
41RTR2.TXT
next >
Wrap
Text File
|
1995-06-16
|
7KB
|
209 lines
NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: 41RTR2.EXE; NetWare 4.10 OS Protocol Update
README FOR: 41RTR2.EXE
NOVELL PRODUCTS and VERSIONS:
NetWare 4.1
ABSTRACT:
This release contains several fixes for numerous protocol-related
NLM(TM) files in the NetWare 4.10 release. Various problems with
TCP/IP, AppleTalk, IPXRTR, or INETCFG are addressed. Actual
problems and solutions are detailed later in the readme technical
information document.
-----------------------------------------------------------------
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO
NOVELL. NOVELL
MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION.
HOWEVER, THE
INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION
ONLY. NOVELL
MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS
INFORMATION.
-----------------------------------------------------------------
SYMPTOM:
Problems with TCP/IP, AppleTalk, IPXRTR, or INETCFG.
NOTE: See SOLUTION SPECIFICS for more symptoms and solutions.
SOLUTION:
Self-Extracting File Name: 41RTR2.EXE Revision: A
Self-Extracting File Name: 41rtr2.exe
Files Included Size Date Time
..\
41RTR2.TXT (This file)
ADSP.MSG 10494 1-13-95 1:46:44 pm
ADSP.NLM 74217 1-13-95 1:46:48 pm
APPLETLK.MSG 35488 3-31-95 7:55:50 pm
APPLETLK.NLM 346809 3-31-95 7:56:14 pm
AURP.MSG 11236 3-31-95 8:05:18 pm
AURP.NLM 80698 3-31-95 8:05:22 pm
BRIDGE.NLM 60442 5-4-95 4:02:56 pm
INETCFG.NLM 330230 2-2-95 5:25:40 pm
IPXCFG.NLM 266056 2-2-95 5:14:04 pm
IPXCON.NLM 345530 5-10-95 11:21:34 am
IPXRTR.NLM 317202 5-10-95 11:11:48 am
IPXRTRNM.NLM 50658 5-10-95 11:15:08 am
LLC8022.NLM 35922 12-19-94 11:40:04 am
PARSER.NLM 7906 5-4-95 4:04:24 pm
TCPIP.NLM 392005 5-8-95 11:52:22 am
Installation Instructions:
1. Make a backup copy of each NLM file and MSG file.
2. Copy the new NLM files to the SYS:SYSTEM directory.
3. Copy the new MSG files to the SYS:SYSTEM\NLS\4 directory.
NOTE: BRIDGE, PARSER, and LLC8022 are required only on NetWare
for OS/2 servers.
SOLUTION SPECIFICS:
AppleTalk:
Resolves problems resulting in hung or aborted print jobs for
applications using the AppleTalk 3.x APIs.
Improves error detection on SFT III(TM) systems.
Fixes a problem that might cause an invalid DDP checksum of
0xFFFF to be transmitted when DDP checksums are enabled.
AURP:
Now waits up to five minutes for transmissions to complete
before unloading. This prevents a server from abending because
transmissions are still pending when AURP is unloaded.
ADSP:
Corrects a problem where a NetWare 4.1 server abends because
ADSP released an invalid memory resource.
BRIDGE and PARSER:
Allows bridging to work concurrently over X.25 and Frame Relay.
INETCFG:
Improves the conversion of load commands from NetWare for
Macintosh to the INETCFG database.
IPXCFG:
Corrects a problem where the frame type is set incorrectly for
IPX if the default is not selected.
IPXRTR:
Corrects a problem with load balancing. If you want to use load
balancing, set the Maximum Number of Path Splits parameter under
the Expert IPX Protocol Options to a value greater than 1. A new
SET command has been added for additional configuration of load
balancing when a server has multiple bindings to the same LAN
without going through a router. The syntax of the new SET command
is as follows:
SET LOAD BALANCE LOCAL LAN = <OFF/ON>
The default state is OFF.
This SET command should be used in the following instances:
- Turn on load balancing if a server is connected to a LAN
through multiple interfaces and the interfaces are either on the
same media or attached to different ports of a switch.
- Turn off load balancing if a server has multiple interfaces to
two segments of the same LAN that is also bridged.
NOTE: The values 0, -1, and -2 are reserved and should never be
assigned as IPX network numbers.
Corrects a problem where the SAP from a print server was not
aged out if RIP and SAP were operating in AUTO mode.
Prevents an abend that occurs if an SPX application sends a
packet to the internal network and load balancing for the local
LAN is turned on using the SET command described above.
Adds a feature that enables NLSP to switch automatically from
broadcast to multicast when all NLSP nodes on the LAN support
multicast.
Corrects a problem where wildcard filters were applied
inappropriately to the source of the packet to all interfaces.
Corrects the handling of the Get Nearest Server request so that
it does not respond with the nearest Directory Server if the SET
REPLY TO GET NEAREST SERVER option is off. IPXRTR does not allow
static routes or services to be added to a link that is not using
static routing.
IPXRTRNM:
Corrects a problem where IPXRTRNM abended on NetWare for
Windows.
IPXCON:
Corrects a problem where IPXCON was not displaying a level 2
neighbor.
LLC8022:
Provides LAN Network Manager (LNM) functionality.
NOTE: Before you install any NetWare for SAA patches, check the
current version of LLC8022. Be sure to make a backup of LLC8022
before installing any NetWare for SAA patches. (Some SAA patches
incorrectly overwrite newer versions of LLC8022. If this happens,
just restore the backup.)
TCP/IP:
Supports OSPF on SFT III IO Engines. The Autonomous System
Boundary Router parameter must be enabled in the OSPF
configuration. Use INETCFG to enable and configure OSPF.
Corrects a problem with directed broadcasts that caused
broadcasts to be forwarded in only one direction.
Allows routes learned from SNMP to be advertised by the IP
routing protocol.
Fixes a problem with route filter exceptions. Depending on the
order in which the filters were set, an exception could be
ignored.
Fixes a problem that might cause a page fault if a TCP or UDP
stream is aborted while data is in transmission.
Fixes a race condition that might cause an abend when running
SFT III on a large IP internet.
PATCH HISTORY:
Patch 41RTR1.EXE was formerly available on NetWire; this
41RTR2.EXE patch supersedes it.
-----------------------------------------------------------------
Any trademarks referenced in this document are the property of
their
respective owners. Consult your product manuals for complete
trademark
information.
-----------------------------------------------------------------