NetWare Client 4.5 Does Not Pass Terminal Server Home Path

• Microsoft Windows NT Server versions 4.0, 4.0 SP4, Terminal Server Edition

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 that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Windows NT Server 4.0, Terminal Server Edition that contains this fix.

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 on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

STATUS

Microsoft has confirmed this to be a problem in Windows NT Server 4.0, Terminal Server Edition.

MORE INFORMATION

The third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

Additional query words:

Keywords : kbdocfix
Version : winnt:4.0,4.0 SP4
Platform : winnt
Issue type : kbbug