Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/100548

From BetaArchive Wiki

Windows for Workgroups and Windows NT Interoperability

Q100548

3.10 3.11
WINDOWS
kbnetwork kbinterop



The information in this article applies to:


  • Microsoft Windows NT Server version 3.1
  • Microsoft Windows NT Workstation version 3.1
  • Microsoft Windows for Workgroups versions 3.1, 3.11





SUMMARY

To ensure smooth interoperability between Windows NT and Windows for Workgroups, there are several issues that must be addressed. When setting up your network, be aware of the following issues:


  • Browsemaster Conflicts
  • Guest Accounts
  • User Name Duplication

This article discusses each of these issues.



MORE INFORMATION

Browsemaster Conflicts

Browsemaster contentions can occur between Windows for Workgroups workstations and Windows NT workstations when a workgroup or domain contains at least one machine of each type. You may have difficulty seeing servers in a Windows NT network from a Windows for Workgroups workstation if the workstation is a backup browsemaster and not registered in the Windows NT network. To work around this problem, add the following line to the [network] section of the SYSTEM.INI files in all Windows for Workgroup machines on the network:

      MaintainServerList=no 

This workaround stops all Windows for Workgroups workstations from trying to be browsemasters. If you use this workaround, you need to ensure that at least one Windows NT machine (workstation or server) in the workgroup or domain is running at all times. Until a Windows NT machine is running or a user changes the value of the MaintainServerList variable to "auto" and reboots, no browsing can occur (you receive error 6118). Another way to enable browsing in this situation is to log onto the domain or workgroup with a valid account (even a guest account works).

Guest Accounts

Guest accounts should remain enabled on domain controllers. Instead of removing guest accounts to restrict access to certain services, simply remove any undesired guest account rights in User Manager.

User Name Duplication

There should not be user name duplicates on different domains. If a user name is duplicated across different domains, there will be inconsistent results when a logon is attempted from a Windows for Workgroups workstation on that Windows NT network.

Additional query words: 3.10 introp 3.11

Keywords :
Issue type :
Technology : kbWinNTsearch kbWinNTWsearch kbWinNTW310 kbWinNTSsearch kbWinNTS310 kbWinNTS310xsearch kbAudDeveloper kbWinNT310xSearch kbWinNTW310Search kbWFWSearch kbWFW310 kbWFW311


Last Reviewed: October 27, 2000
© 2001 Microsoft Corporation. All rights reserved. Terms of Use.