DOCUMENT:Q102775  01-SEP-1993  [W_NT]
TITLE   :Problems with WFW to Windows NT Connectivity
PRODUCT :Windows NT
PROD/VER:3.10
OPER/SYS:WINDOWS
KEYWORDS:

----------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Windows NT operating system, version 3.1
 - Microsoft Windows NT Advanced Server, version 3.1
----------------------------------------------------------------------

SUMMARY
=======

In some cases, you may have problems accessing Windows NT servers from
Windows for Workgroups (WFW) machines. This article covers some of
the better known connectivity issues.

MORE INFORMATION
================

Using Lowercase Extended Characters for Passwords
-------------------------------------------------

Lower level machines such as WFW should not use lowercase extended
characters for passwords on Windows NT servers. By convention, the
down level client converts the password to uppercase before it is sent
to Windows NT. Some of the international characters do not have an
uppercase equivalent, which causes Windows NT to fail to validate the
password.

Using a Windows for Workgroups Machine as a Backup Browser
----------------------------------------------------------

If Windows NT is the master browser and Windows for Workgroups is the
backup browser, you may get an empty browser list under the following
conditions:

 - A user logs on to the Windows for Workgroups machine and does not
   have a valid username/password for the domain.

 - The Windows NT master browser goes down and promotes the Windows
   for Workgroups browser.

The Windows for Workgroups machine may have a empty browser list
caused by a failure to authenticate with the master before Windows for
Workgroups was promoted.

Using International Characters in the Windows NT Share Name
-----------------------------------------------------------

If you try to connect to a Windows NT share that contains one or more
international characters in the share name, you will receive an error
message.

Access Denied Errors
--------------------

Windows for Workgroups does not send out domain information when:

 - It attempts to log on to the Windows for Workgroups system

 - You issue a "NET USE" command for a Windows NT server causing a
   logon to an Windows NT system

This may cause access denied errors in the case where you have primary
accounts with different passwords in more than one trusted domain.
Your access to the server will depend on which trusted domain can
authenticate the users credential first.

Additional reference words: 3.10 browse
KBCategory:
KBSubCategory: INTEROP

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.  MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.  SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1993.