If the FTP service does not work after it has been started, switch to passive mode with the following command:

FTP> SET PASSIVE ON
Passive is ON

In passive mode, the FTP client always initiates a data connection. This is useful in virtual machine environments when there is network address translation (NAT) in your network.

To run this command automatically when you invoke FTP, put it into SYS$LOGIN:FTPINIT.INI. For the full description of the SET PASSIVE command, refer to the VSI TCP/IP Services for OpenVMS User’s Guide.

You cannot run the DHCP and the failSAFE IP client on the same NIC on VSI TCP/IP Services for OpenVMS V6.0. If a customer is running the DHCP client on a NIC, then failSAFE IP should not be configured on this NIC. Since the assigned address is actually controlled by DHCP, VSI TCP/IP Services for OpenVMS should not reassign this address. If a customer needs to run the DHCP client and provide a failover mechanism, they should configure the NIC in a lan failover set.

NTPDATE is no longer supported and will be removed from an upcoming release of VSI TCP/IP Services. To perform the equivalent of NTPDATE, run NTPD making use of the -q and "-G" options.

$ ntpd :== $tcpip$ntp 
$ ntpd "-G" -q
ntp.exe[538969120]: ntpd 4.2.8p15@1.3728 Fri Sep 22 07:00:58 UTC 2020 (2): Starting
ntp.exe[538969120]: Command line: tbd$dka200:[sys0.syscommon.][sysexe]tcpip$ntp.exe -G -q -4
ntp.exe[538969120]: ----------------------------------------------------
ntp.exe[538969120]: ntp-4 is maintained by Network Time Foundation,
ntp.exe[538969120]: Inc. (NTF), a non-profit 501(c)(3) public-benefit
ntp.exe[538969120]: corporation.  Support and training for ntp-4 are
ntp.exe[538969120]: available at https://www.nwtime.org/support
ntp.exe[538969120]: ----------------------------------------------------
ntp.exe[538969120]: proto: precision = 1000.000 usec (-10)
ntp.exe[538969120]: proto: fuzz beneath 0.710 usec
ntp.exe[538969120]: basedate set to 2022-05-21
ntp.exe[538969120]: gps base set to 2022-05-22 (week 2211)
ntp.exe[538969120]: Listen and drop on 0 v4wildcard 0.0.0.0:123
ntp.exe[538969120]: Listen normally on 1 LO0 127.0.0.1:123
ntp.exe[538969120]: Listen normally on 2 WE0 10.10.116.182:123
ntp.exe[538969120]: Listening on routing socket on fd #4 for interface updates
ntp.exe[538969120]: ntpd: time set -50.590756 s
ntpd: time set -50.590756s
$

The following lines in the TCPIP$BIND_CONF.TEMPLATE_FORWARD template file set up the forwarders' addresses and the DNSSEC validation:

//Specifies the IP addresses to be used for forwarding.
//The default is the empty list (no forwarding).
forwarders {
    8.8.8.8;
    8.8.4.4;
};
 
dnssec-validation auto; //Enable DNSSEC validation.
                        //Note dnssec-enable also needs to be set to
                        //yes to be effective. The default is yes.

However, if forwarders are changed to DNS servers that do not support DNSSEC or have it disabled, DNS lookup replies will be discarded when the DNSSEC validation fails.

dnssec-validation auto

Occasionally, the attributes of a file just written from a client under stress testing are briefly inconsistent with the server's copy, despite having been properly stored on the server.

The error SS$_BADIRECTORY is occasionally returned when deleting a file.

The default timeout value of 1 second is problematic. It is recommended that a larger timeout value is used (5 seconds), and a future release will increase the default value.

A stale file is occasionally reported by OPCOM, usually with an NFS client delete request.

Some NFS servers report a WRITE error with the NFS client. On rare occasions, the client sends a request with a bad stability option value.

The QIO operations on the NFS client may fail with an unexpected TIMEOUT error when the operations on the server side take longer than expected.

One of such situations may occur when VSI OpenVMS is running on a guest virtual machine, and the NFS client sends server requests too frequently. The solution in this case would be to increase the timeout interval to a larger value, around 5 seconds.

TCPIP$CONFIG no longer fails in the extended parse mode when a user attempts to configure interfaces from the VSI TCP/IP Services Configuration Menu.

Previously, it would fail with the following error:

%DCL-W-IVCHAR, invalid numeric value - check for invalid digits

If a server does not support the READDIRPLUS operation or does not return the file attributes, the DNFS client automatically switches from using READDIRPLUS to using the basic READDIR operation followed by the LOOKUP operation. This ensures that the correct set of file attributes is cached.

The switch stays in effect until the DNFS device is dismounted.

Previously, the DNFS client handled the return codes from certain internal functions and QIO operations incorrectly, which could potentially lead to an incorrect path of execution and crash the DNFSACP process.

This issue has been fixed in the current release.

Previously, under certain conditions, the DNFS client could fail to serialize access to the state data, which would cause the NFSACP process to crash.

This issue has been fixed in the current release.

Previously, the DNFS client incorrectly processed the file handles that were over 32 bytes long. This issue has been fixed in the current release.

Previously, the DNFS client failed to correctly encode the server requests where the file handle size was not a multiple of 4. This resulted in incorrect parsing of the subsequent fields.

This issue has been fixed in the current release.

Previously, the DNFS client incorrectly handled failed memory allocations, especially when processing the UNSTABLE WRITE operations, potentially leading to a DNFSACP crash.

This issue has been fixed in the current release.