XCLN: Expired Passwords, Windows 3.x Client, and ShivaRemote

MORE INFORMATION

There are two issues to be considered here: informing you of conditions that require corrective action and providing a mechanism to take corrective action.

Informing you:

When using the Microsoft Exchange Client remotely and/or working offline, "Tools, Deliver Now..." is not the best option for initiating a connection to a Microsoft Exchange Server and transferring mail.

"Tools, Deliver Now..." operates in a mode that minimizes dialog popup. It is the same mode used for scheduled connections. The assumption is that no one may be present to respond to error dialogs or conditions, and therefore, communication, authentication, or operational errors returned during these operations do not result in dialog popups.

When working remotely or offline, the "Remote Mail, Tools, Connect" mechanism or "Tools, Synchronize, <option>" mechanism operates in a mode that assumes the user is present and thus returns communication, authentication, and operational errors to the user. These options are the recommended mechanisms for initiating a connection to a Microsoft Exchange Server and transferring mail when working remotely or offline.

The problem documented in this article is that the error handling chain from ShivaRemote to the Microsoft Exchange Client was not returning the proper error message when using the "Remote Mail" or "Synchronize" mechanisms.

The "expired domain password" condition can be confirmed by launching a Shiva Remote dial-up connection within Windows or Windows for Workgroups, outside of Microsoft Exchange. If the domain password has expired, you will receive the following dialog: Alternatively, after applying the latest service pack, the following messages are returned when using the corresponding mechanisms: Corrective actions:

There is no mechanism in the Microsoft Exchange Client to allow you to change your NT domain password after it has expired. The client's password change mechanism assumes a connection to the Microsoft Exchange Server is available. In the case of remote dial-up, you must first have a valid network connection before you can access either your Microsoft Exchange Server or your Primary Domain Controller (PDC).

The ShivaRemote software installed with the Microsoft Exchange Windows 3.x client does not support Windows NT Networking APIs for password changes.

Workarounds:

The best option for accommodating remote mail users is to use Windows 95 or Windows NT for dial-in clients because they natively support NT RAS dial-in and NT password change APIs. However, marginal workarounds exist for specific cases when using Windows for Workgroups or when dialing into a Shiva LanRover.

1. Start the Shiva connection outside of Microsoft Exchange and establish a connection.
2. In Control Panel, Network, Logon(\Off), log off and then Log on. This should engage the mechanism for changing an expired Windows NT domain password.
3. Start the Microsoft Exchange Client and provide the new domain credentials. If your profile has disabled the Tools, Services, Microsoft Exchange Server, Advanced, Use Network Security During Logon checkbox. You will still have to synchronize all the passwords that Windows caches in the <username>.PWL or elsewhere.

1. Start the Shiva connection outside of Microsoft Exchange and establish a connection.
2. On the Windows 3.1 computer, run the Chngpass.exe utility included with FPNW. This should change the Windows NT domain password and FPNW password. Chngpass.exe requires an SPX connection to the PDC.
3. Start the Microsoft Exchange Client and provide the new domain credentials if your profile has disabled the Tools, Services, Microsoft Exchange Server, Advanced, Use Network Security During Logon checkbox.