Windows nt 4 technical support

Microsoft does not perform testing against versions of Windows that are no longer supported. This will prevent Windows NT 4. Computer Objects exist in Active Directory that indicate they are running Windows or earlier. These could be old computer objects or they could be active servers or workstations that still exist in the environment. The default security settings , starting with with Windows Server , were improved.

Those security options are not available with Windows NT 4. Trust relationships with Windows NT 4. When a Windows NT 4. The Microsoft Cryptography application programming interface CryptoAPI provides developers with core cryptographic and certificate functions. CryptoAPI 1. CryptoAPI 2. Developers can use certificates with these public-key operations and perform the necessary encapsulations and encoding to apply certificates within their applications.

This model allows developers to easily adapt their applications to evolving cryptographic technologies and government export policies. This allows applications using CryptoAPI to operate with other certificate-based systems that adhere to these standards. The release version of CryptoAPI 2. These changes are reflected in the Crypt Please consult the CryptoAPI 2. Service Pack 3 contains a complete software implementation of DirectX 3. This translates into the following major feature changes since the release of DirectX 2.

DirectInput COM interface supporting mouse and keyboard data with documentation and sample programs. Direct3D Software emulation for the Direct3D 3.

In Windows NT 4. ODBC 3. This updated version of ODBC also introduces the concept of a file data source that can be shared or placed on a central server. With the appropriate drivers installed, ODBC 3. For more information on ODBC 3. The updated protocol has two main improvements: it supports mutual authentication, which closes a "man-in-the-middle" attack, and it supports message authentication, which prevents active message attacks.

SMB signing provides this authentication by placing a digital security signature into each SMB, which is then verified by both the client and the server. In order to use SMB signing, you must either enable it or require it on both the client and the server. If SMB signing is enabled on a server, then clients that are also enabled for SMB signing will use the new protocol during all subsequent sessions and clients that are not enabled for SMB signing will use the older SMB protocol.

If SMB signing is required on a server, then a client will not be able to establish a session unless it is enabled for SMB signing.

SMB signing is disabled by default on a server system when you install the Service Pack; it is enabled by default on a workstation system when you apply the Service Pack.

This incompatibility will be most obvious when you have direct host IPX clients and you require SMB signing on the server. Requiring SMB signatures on the server will cause the server to not bind to the direct host IPX interface, which will then force all connections to the server to be signed. Also, SMB signing will impose a performance penalty on your system.

Although it doesn't consume any more network bandwidth, it does use more CPU cycles on the client and server side. This Service Pack includes a password filter Passfilt. The password filter should be copied to the primary domain controller for the domain, and to any backup domain controllers in the event the server role in the domain changes. To use the password filter, the following registry entry must exist.

If it doesn't exist you must create it. Microsoft cannot guarantee that any problems resulting from the use of the registry editor can be solved. Use this tool at your own risk. Notification Packages contains a list of DLLs to be loaded and notified of password changes and password change requests. You can audit the loading of Notification Packages by setting the audit policy in User Manager. To do this, start User Manager and then click Audit on the Policies menu. Custom password filter DLLs can be written to implement different password rules.

Windows NT has a feature where anonymous logon users can list domain user names and enumerate share names. Some customers who want enhanced security have requested the ability to optionally restrict this functionality. Service Pack 3 provides a mechanism for administrators to restrict the ability for anonymous logon users also known as NULL session connections to list account names and enumerate share names. On the client side, Windows and XP have been out for quite a while," Erlandson said.

We still have customer support arrangements for those who do need that support. Erlandson said Microsoft's former life-cycle plan, announced on Feb. When Microsoft announced its new Support Lifecycle plan last fall, it didn't "retrofit" all of its older products to the new five-year mainstream and two-year extended support cycles, he said.

No-charge assisted support and extended hot fix support for Windows 98 -- which was released five years ago -- also ended yesterday. But Microsoft is providing paid support through Jan. It doesn't buy enterprises much to extend the assisted support without the hot fix support.

Erlandson said the support decision involving Windows 98 wasn't aimed at enterprise customers but at consumers. He said the call volume for enterprise customers needing support with Windows 98 has been very light.

Online self-help support for Windows 98 will be available at least until June 30, , according to Microsoft's Web site. Here are the latest Insider stories. More Insider Sign Out.