The information in this article applies to:
SUMMARY
In some cases, you may have problems accessing Windows NT servers from
Windows for Workgroups (WfWG) computers. This article covers some of
the better known connectivity issues. WORKAROUNDUse quotation marks around the computer name and share name. This will allow the connections. For example: NET USE F: "\\Computer Name\share" MORE INFORMATIONUsing Lowercase Extended Characters for PasswordsLower level machines such as WFWG 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 BrowserIf 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:
Using International Characters in the Windows NT Share NameIf 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 ErrorsWindows for Workgroups does not send out domain information when:
Error 2242A Windows for Workgroups computer may be unable to connect to a Windows NT or Windows NT Advanced server computer, for the purposes of sharing resources. When you try to connect, the Windows for Workgroups computer generates the following error message: Error 2242.Windows for Workgroups computers need accounts on Windows NT computers to use shared resources on the Windows NT computers. Error 2242 is generated if the given password on that account has expired. This error can also be generated if the "User must change password on next logon" box was checked when the account was created. To correct this error use the following procedure:
Additional query words: wfw wfwg prodnt WC 3.10 3.11 browse
Keywords : NTInterop |
Last Reviewed: September 24, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |