NetWare Client 4.5 Does Not Pass Terminal Server Home Path (200364)


The information in this article applies to:

  • Microsoft Windows NT Server 4.0 Terminal Server Edition SP4
This article was previously published under Q200364

SYMPTOMS

When using the NetWare 4.5 client (this client is Windows Terminal Server aware), the user's HOME path environment is not passed to the operating system.

Many login scripts rely on this variable.

CAUSE

When you use the Windows NT client v 4.5 and initiate a Terminal Server connection through Windows 95 or Windows NT Terminal Server Client, the login is sucessful but the HOME_PATH variable is not set. This variable should be set to the same path that is set for the user's Terminal Server home directory. In addition, the Terminal Server profile path is not read.

Novell cannot address this issue until the new fields are made avilable to them through an API call. Currently, the API does not exist.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows NT Server 4.0, Terminal Server Edition that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.


STATUS

Microsoft has confirmed that this is a problem in Windows NT Server 4.0, Terminal Server Edition.

MORE INFORMATION

The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Modification Type:MinorLast Reviewed:10/5/2005
Keywords:kbbug kbdocfix kbpending KB200364
©2004 Microsoft Corporation. All rights reserved.