|
Introduction
------------
The following versions of the DNAS load image are superseded by ECO #04
of DNAS V2.0.
DECserver | Obsolete Versions | New Version
----------+---------------------+---------------
DS900GM | (notes 2 and 3) |
DS900TM | V1.0 through V1.5 |
DS700 | all baselevels |
DS90M | V2.0 BL10-40 | V2.0 BL10D-40
(note 1) | V2.0 BL10A-40 |
| V2.0 BL10B-40 |
| V2.0 BL10C-40 |
----------+---------------------+---------------
The ECO has been submitted to CSC under the following kit names. However,
as of February 3, 1997 none of the kits have been released by the CSC.
NAECO04020.A
NAOSF04020.TAR
NAULT04020.TAR
NAUNX04020.TAR
Two alternate methods for obtaining kits have also been provided: anonymous
FTP, and DECnet file copy.
Anonymous ftp:
==============
ftp to feenix.lkg.dec.com (16.20.180.1) using "anonymous" as the
username and your internet mail address as the password. Then, ...
ftp> cd dnas
250 CWD command successful.
ftp> cd kits
250 CWD command successful.
Now, enter one of the following commands depending on which kit you need:
ftp> cd openvms - OpenVMS BACKUP savesets
ftp> cd osf - Digital Unix TAR file
ftp> cd ultrix - ULTRIX TAR file
ftp> cd unix - Generic Unix TAR file
ftp> cd win32 - Windows 95 and NT
Then drop into the patch subdirectory using the following command.
ftp> cd patch
Don't forget to set binary mode before copying non-ASCII files!
DECnet:
=======
FEENIX::NA$ROOT:[OPENVMS.PATCH] - OpenVMS BACKUP savesets
FEENIX::NA$ROOT:[OSF.PATCH] - Digital Unix TAR file
FEENIX::NA$ROOT:[ULTRIX.PATCH] - ULTRIX TAR file
FEENIX::NA$ROOT:[UNIX.PATCH] - Generic Unix TAR file
FEENIX::NA$ROOT:[WIN32.PATCH] - Windows 95 and NT
Notes
-----
The new DNAS images supplied by this ECO include all software corrections
made since the release of DNAS V1.0 BL45-15. However the following section
describes only the corrections made after the release of V1.5 BL95D-34.
Please refer to the release notes for a more detailed description.
The ECO'd images contain all the functionality available in DNAS V2.0
BL10-40 and are backward compatible with earlier images except for the
extra memory requirements. It's required that the DNAS V2.0 BL10-40 kit be
installed prior to installing this ECO.
Please read the cover letter before installing the kit. The OSF, Ultrix,
Unix and Windows kits do not use the normal installation procedures.
We're still working on building a kit for Windows 95 and NT. For now the
Windows 95 and NT patch directory contains the load images WWENG2 (DS900
and DS700), MNENG2 (DS90TL and DS90M), and release notes Eco04020.not.
Problems Corrected in This ECO
------------------------------
- TSM$NA_V20_GET_CHAR.COM was not able to restore Dialer Services, Telnet
client terminal type, and Telnet server SLIP and PPP hot keys.
- DSV$CONFIGURE.COM did not verify the compatibility between DECnet and
DSV$SERVER_DEFINE.COM prior to adding, deleting, or modifying servers.
- The server would sometimes bugcheck with a code of 299 during a DNS lookup
if the DNS cache contained a root nameserver and at least one, but not all,
of the local nameservers for the default domain name had expired.
- The server would sometimes bugcheck with a code of 500 if an asynchronous
port detected a BREAK while creating a PPP session.
- Severs would occasionally bugcheck with a code of 830 when SNMP was used to
read the accounting log.
- Severs would occasionally bugcheck with a codes of 978 and 969.
- Under certain conditions the server would bugcheck with a code of 1234 if
the DIAL feature or PPP was being used.
- The use of the '*' in the {SET | CHANGE | DEFINE} DIALER SERVICE foo MODE
command was too vague. The command will now accept the string "ANY".
- Authenticated ports with an access type of LOGIN would hang if the port was
not preconfigured with a default protocol of LAT, Telnet, or ANY.
- A port type of HARD or SOFT caused some SHOW and MONITOR displays to be
truncated.
- Executing the command {PURGE | CLEAR} TELNET LISTENER 23 cleared the
listener's Identification string. It should have set it to "Telnet Console".
- Entering a ^Z while being prompted for a telephone number while establishing
a dialback session generated a Dial Session Failure accounting event.
- The LIST USERACCOUNT command caused a small memory leak.
- Attempting to connect to an unknown dialer service would cause the port to
hang.
- The SHOW QUEUE PORT port-number command didn't show queued LAT connections
for the correct port.
- The PURGE DIALER SCRIPT, PURGE DIALER SERVICE, PURGE USERACCOUNT, DEFINE
DIALER SERVICE, and DEFINE USERACCOUNT all caused small memory leaks.
- RADIUS re-authentication during dialback did not always generate a RADIUS
accounting START or STOP message.
- A RADIUS supplied name for a LAT service or Telnet host would be misread by
the access server causing the connection attempt to be misdirected.
- The text supplied in RADIUS access-rejected reply messages was not always
displayed to the user.
- The UI did not allow hyphens in node names. Attempting to connect to node
PPP-TEST would cause a PPP connection to be started.
- LAT sessions could not restore flow control following a session switch.
As a result the port occasionally got into a state where it would display
what appeared to be random data on the user's terminal.
- Servers configured to use Kerberos authentication would experience
insufficient resource errors after several days of operation.
- The server's asynchronous ports would not generate an XON when a remote LAT
or Telnet connection was terminated.
- None of the server's SHOW displays gave the local TCP port number.
- The server did not handle the Force XON bit in LAT attention slots.
- If a framed user was authenticated by a realm which did not specify an
access type, the authentication attempt would fail and the user's client
would report a "CHAP/PAP failure"
- A successfully authenticated login attempt using PPP would result in two
login accounting events: one with a username and one without.
- PPP connection attempts would either fail with a code of 503 or fail without
displaying an error message.
- The server sometimes bugchecks with a code of 977 if a user enters the
break while being authenticated via Kerberos.
- The SET INTERNET ADDRESS command was not restricted to privileged users.
- RAW TCP listeners were not included in the LIST TELNET LISTENER ALL display.
- LAT group code supplied via Radius were not applied to the port properly.
- The server would not always select the next highest rated node if it's first
choice of a host was unavailable due to insufficient resources.
- Using Radius caused an intermittent loss of 1000 bytes of DRAM.
- 32 port servers would sometimes bugcheck if one of the upper 16 ports (port
17 through 32) could not keep up received data.
- The server would sometimes bugcheck with codes of 299 or 540 while trying to
establish an IP connection.
- Telnet client connections were restricted to a limited number of TCP ports
determined by the number of ports supported by the server.
- DS900GM servers would sometimes bugcheck with a code of 0002 when a port
detected that DSR had changed state.
- Authentication enforced callbacks sometimes failed to re-authenticate the
user following the callback.
|