|
ru.networks
- RU.NETWORKS ------------------------------------------------------------------
From : Victor Yuzhanin 2:5079/32.89 19 Feb 2001 18:45:50
To : Eugene Azarkin
Subject : Computer Browser ?
--------------------------------------------------------------------------------
Eugene Azarkin wrote to All :
EA> Есть две сети
EA> 192.168.0.xxx -> PDC (NT4) <- 192.168.1.xxx
EA> Hа сеpвеpе есть WINS и DHCP сеpвеpа.
EA> Все pаботает, но в сетевом окpyжении клиенты (win95) видят токо
EA> свой сегмент. ( а надо бы оба) в сетевом окpyжении сеpвеpа видны оба
EA> сегмента. ЧТО еще можно сделать ?
Пpисоединяюсь к вопpосy.
Пpобовал я делать вот по этой доке, не полyчается. Может быть y тебя выйдет.
== cut ==
PSS ID Number: Q244983
Article last modified on 10-21-2000
WINDOWS:2000; winnt:4.0
-------------------------------------------------------------------------------
The information in this article applies to:
- Microsoft Windows NT Server version 4.0
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
-------------------------------------------------------------------------------
SYMPTOMS
========
When you use a multihomed primary domain controller (PDC), you may experience
browsing problems and NetBIOS name resolution errors.
CAUSE
=====
This issue can occur because each browser service bound to each interface
operates independently. The PDC maintains a separate cumulative list on each
interface, but the lists are not merged. A master browser that exchanges lists
with the PDC on one interface does not obtain a list of servers discovered by a
master browser that is exchanging lists with the PDC on the other interface.
Because the browser service does not merge the browse list for separate
networks, the PDC should not be multihomed.
RESOLUTION
==========
To resolve this issue, unbind the WINS Client (TCP/IP) protocol from the second
adapter.
NOTE: After unbinding the additional adapters, verify that the WINS database
and any LMHosts files do not refer to the Internet Protocol (IP) address of the
unbound adapters. WINS may need to be purged to register the old entries for
the second network interface card (NIC) out of the WINS database.
Windows NT 4.0
--------------
1. Click Start, point to Settings, click Control Panel, and then double-click
Network.
2. Click Bindings.
3. In the Show Bindings For box, click All Protocols.
4. Double-click the WINS Client (TCP/IP) protocol branch to expand the list of
adapters bound to the protocol.
5. To disable the network binding between the WINS Client (TCP/IP) protocol and
the second network adapter, click the second network adapter, and click
Disable.
6. Click OK, and then click Close.
7. Click Yes to restart your computer.
Windows 2000
------------
1. Right-click My Network Places, and then click Properties.
2. Right-click the external network adapter's Local Area Connection icon, and
then click Properties.
NOTE: VPN, RRAS, and RAS can also create a second network adapter to create the
browsing issue.
3. Click Internet Protocl (TCP/IP), and then click Properties.
4. Click Advanced.
5. Click the WINS tab.
6. Click "Disable NetBIOS over TCP/IP".
7. Click OK, click OK, and then click OK.
MORE INFORMATION
================
When browsing does not work on a multihomed computer, the transport that did
not
work can be identified in Event Viewer by locating text similar to this: 'The
browser was unable to retrieve a list of servers from the browser master
primary
domain controller name on the network \device name\transport name' or 'The
browser service has failed to retrieve the backup list too many times on
transport of transport name'. The transport for NetBIOS over TCP/IP appears as
'NetBT_network card driver name', such as 'NetBT_E100B1'. The transport for
other protocols appears as:
NetBEUI protocol appears as: Nbf_network card name.
IPX/SPX protocol appears as: NwlnkIpx (the network card name does not
appear).
NetBIOS over NwLink appears as: NwLnkNB (the network card name does not
appear).
Microsoft Windows NT version 4.0 introduced the 'UnboundBindings' setting, and
this can be used to prevent the PDC from directly gathering a browse list on
more than one interface. However, this setting does not force the master
browsers in the domain to use only the bound interface card. If WINS is used to
provide the IP address for the master browser to find the PDC, there is no way
of guaranteeing that the correct interface is chosen. This limitation cannot be
overcome with Windows NT 4.0. To guarantee that it can merge a single,
domain-wide list, the PDC must not be a multihomed computer.
The following procedure describes how to edit the registry to enable the
UnboundBindings parameter, which will prevent the PDC from directly gathering a
browse list on more than one interface. In versions of Windows NT Server
earlier than version 4.0, it was not possible to browse across subnets that
were connected by a PDC server configured with TCP/IP routing and WINS. In NT
4.0, the parameter UnboundBindings can be added to the registry of the
multihomed domain master browser to disable the binding between the second NIC
and the browser service. On a multihomed PDC running WINS, all WINS entries
should have the IP address of the one network adapter that has the browser
service enabled.
1. Use Registry Editor to locate the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters
2. Add a REG_MULTI_SZ value named UnboundBindings with a value of NetBT_network
adapter name to this key, where network adapter name is the name of the
network adapter on which to disable the binding to the browser service.
NOTE: You can determine the names of your network cards by typing NET CONFIG
RDR at the command prompt. The network cards are indicated by NetBT_NIC type,
where NIC type is the type of network interface card on your computer. You
can also find the names of your network adapters in the following registry
key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
Each network adapter has multiple entries in the registry. A network card
entry that ends in a number contains the settings for a specific instance of
the card. Select the instance of the card where you want to disable the
bindings to the browser service.
For example, for a computer with two Intel EtherExpress Pro 100B network
adapters, there are three registry keys, 'E100B' and 'E100B1' and 'E100B2',
in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services. The first entry,
'E100B', contains the driver and binding information for all the Intel
EtherExpress Pro 100B cards. The entry 'E100B1' contains the settings for the
first instance of the card. The settings for the second instance of the card
is listed in the registry as 'E100B2'. To disable the bindings to the browser
on the second network card, type "NetBT_E100B2" (without the quotation marks)
in the String text box.
If there are more than two network adapters on the multihomed PDC computer,
type on a separate line of the String field the name of each network adapter
to disable the browser bindings.
3. Restart the computer to enable the new settings.
4. After the computer restarts, look in the Event Log to make sure the new
settings are working properly:
a. Start Event Viewer.
b. Inspect the System event log for one occurrence of the following event
that corresponds to the adapter on which the binding to the browser
service is enabled:
Source: Browser
Event: 8015 (The browser has forced an election on network device because a
Windows NT Server (or domain master) browser is started.)
== end ==
Виктоp
---
* Origin: (2:5079/32.89)
Вернуться к списку тем, сортированных по: возрастание даты уменьшение даты тема автор
|
Computer Browser ? 