Microsoft gibt folgende Antwort:Kurz nur: PDC darf nicht multihomed sein. PSS ID Number: Q191611Article last modified on 02-17-1999 winnt:4.0 winnt ======================================================================-------------------------------------------------------------------------------The information in this article applies to: - Microsoft Windows NT Server version 4.0 - Microsoft Windows NT Workstation version 4.0 - Microsoft Windows NT Server, Enterprise Edition version 4.0 ------------------------------------------------------------------------------- IMPORTANT: This article contains information about editing the registry.Before you edit the registry, make sure you understand how to restore itif a problem occurs. For information about how to do this, view the"Restoring the Registry" Help topic in Regedit.exe or the "Restoring aRegistry Key" Help topic in Regedt32.exe. SUMMARY======= The computer browser service was first introduced in Microsoft Windows forWorkgroups 3.1. The purpose of the browser service is to collect and report theexistence of other computers on the network that are sharing file, print, andother resources. The browser service greatly reduces the number of serverannouncements on a network, and it reduces the overhead of every network clientand server because clients and servers do not have to maintain their own list ofserver resources. The browser service was originally designed for computers connected on asingle-segment local area network (LAN) using a non-routable protocol, such asNetBIOS Extended User Interface (NetBEUI). If a client requested a list ofservers from a multihomed browser server, the browser service would provide onlythe list of servers gathered on the network adapter that received the browserequest. This was done because it could not be assumed that a client would beable to connect to servers on the other segment. When you use a non-routableprotocol, such as NetBEUI, a client also has to be multihomed to connect to aremote server. When you use a routable protocol, such as the TransmissionControl Protocol/Internet Protocol (TCP/IP), an infrastructure of routers needsto be in place for the physical connection to be possible. This was in additionto an LMHOSTS file configured for all clients that potentially could connect tothe remote servers. Microcomputer networks have since evolved into much larger environments thatrequire routable protocols, and distributed NetBIOS naming servers such as theWindows Internet Naming Service (WINS) for NetBIOS communication. With thegrowth of segmented LANs, the browser service has been updated to accommodatethe TCP/IP protocol in a domain environment. To obtain a single domain-widebrowse list, the primary domain controller (PDC) has the role of merging all thebrowse lists gathered by the master browsers on each segment across the widearea network (WAN). This role is called the domain master browser and can onlybe performed by the PDC. WINS allows clients to easily access remote serversthroughout the WAN, and each PDC periodically contacts the WINS server to obtaina list of all the domains throughout the network. This allows for full browsingof server resources throughout the WAN. The evolution of networking has also increased the number of servers and clientswith more than one network adapter. Multihomed servers can create unexpected andundesirable effects with the browser service. MORE INFORMATION================ Domain Master Browser Issues - PDC---------------------------------- The PDC cannot be multihomed for there to be a single domain-wide list of serversbecause the browser maintains a separate list of servers for each networkadapter and protocol combination. If the PDC is multihomed, there are twopartial cumulative lists built for the domain, and no one computer in thenetwork can access the full list of servers in the domain. Each master browsercan retrieve the list of servers from only one of the PDC's network adapters.The list of servers that the PDC builds on each network adapter is notdeterministic because it depends on which network adapter the PDC uses tocontact the master browser. Windows NT 4.0 introduced the UnboundBindings registry entry that effectivelyturns off the browser for each network adapter specified. Even with the browserrunning only on one network adapter on the PDC, there is no way to guaranteethat a master browser will only access the PDC through the active networkadapter. All master browsers that communicate with the unbound network adapteron the PDC cannot receive the list of additional servers in the domain, nor thelist of additional domains found in WINS or by other master browsers. Therefore, to build a single domain-wide list of servers, the PDC cannot bemultihomed. Master Browser Issues--------------------- After the master browser obtains a list of servers in the domain and the list ofadditional domain names from the PDC, it sends a MasterAnnouncement frame to thePDC. This signals the PDC to retrieve a list of servers and workgroupannouncements from the master browser. Because all NetBIOS sessions between any two servers over TCP/IP can only resideon a single IP connection, there is no way for the PDC to maintain more than oneIP address for the master browser's computer name. This means that any serverthat is a master browser cannot be multihomed because the PDC will contact onlythe master browser on one of its network adapters. If a multihomed server is a master browser on both network adapters, the PDC willcollect only the hosts discovered by the network adapter that it is connectedto, and all other servers and domain names discovered on the other networkadapter will be lost to the rest of the domain. If a multihomed server is amaster browser on one network adapter and a backup browser or a non-browser byelection or the UnboundBindings setting on the other network adapter, there isno way to guarantee that the PDC will connect to the master browser's networkadapter. If the master browser has two network adapters, the odds of connectingto the correct interface are fifty percent. If the wrong network adapter isselected, all servers and domain names collected by this master browser will notbe available to the rest of the domain. Therefore, for the PDC to centrally collect all server and domain names, allmaster browsers must not be multihomed. Backup And Potential Browser Issues----------------------------------- Because browser roles are determined by election, no server that can be a masterbrowser can be multihomed. When a client requests a browse list, it issues aGetBackupListRequest, and the response contains a list of computer names. Theclient then establishes a session to one of the computer names in the responseframe. If the network adapter chosen is not running the browser service, theclient will not receive a browse list. Therefore, no backup browsers can bemultihomed. If the network adapter selected is a browser, the list received maycontain servers collected by a master browser on another segment, therebyremoving the deterministic nature of the browser infrastructure. Suggestions for Workaround-------------------------- WARNING: Using Registry Editor incorrectly can cause serious problems that mayrequire you to reinstall your operating system. Microsoft cannot guarantee thatproblems resulting from the incorrect use of Registry Editor can be solved. UseRegistry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys AndValues" Help topic in Registry Editor (Regedit.exe) or the "Add and DeleteInformation in the Registry" and "Edit Registry Data" Help topics inRegedt32.exe. Note that you should back up the registry before you edit it. The PDC must be singlehomed for browsing to operate correctly. All domaincontrollers in a domain are by default browser servers. Therefore, theworkarounds below can help ensure that the browser servers are singlehomed andenable the browsing service to operate correctly. To prevent multihomed Windows NT servers from becoming browser servers: 1. Click Start, point to Settings, click Control Panel, and then double- click Services. 2. Click Computer Browser, click Properties, and then click Manual. 3. Click OK, click Close, and then restart the computer. Or, use Registry Editor (Regedt32.exe) to edit the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ Browser\Parameters\MaintainServerList Change the value of this key to "false" (without quotation marks), quit RegistryEditor, and then restart your computer. To encourage singlehomed computers to become the browser servers: Use Registry Editor (Regedt32.exe) to edit the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ Browser\Parameters\IsDomainMaster Change the value of this key to "yes" (without quotation marks), quit RegistryEditor, and then restart your computer. ======================================================================Keywords : kbenv kbnetwork ntdomain Version : winnt:4.0Platform : winntIssue type : kbinfo=============================================================================Copyright Microsoft Corporation 1999.
06.03.2000, 16:36 Uhr
, 21 mal gelesen