Re: Child Domain NetBIOS Issue



Network Neighborhood is completely independent of DNS. It is driven by
the computer browser service, an NT legacy app which uses Netbios names and
relies on broadcasts.

Because broadcasts don't cross routers, WINS is required to browse a
routed network. If all of your machines (including the servers) are
registering with the same WINS server, this should be working. You should
see the sub-domain's Netbios name and the workstations in that subnet in the
browse list from NN.

There is a description of the browser service in KB188001 and a
troubleshooter in KB188305 .


PJ wrote:
Hi,

Having a problem with a child domain and being able to browse or
connect to resources in it via NetBIOS names from the parent domain
(i.e. \\SERVERNAME or browsing through Network Neighbourhood - the
child domain's NetBIOS name isn't there).

The child domain is on a different subnet, WINS is running on a
server in the parent domain which is used by both parent and child
domain clients/servers.

DNS seems to be functioning correctly as resources can be located in
the child domain if the FQDN is used.

Any ideas??


.



Relevant Pages

  • Re: Cant connect to computers
    ... I can see then in network neighborhood, just once i click them to access them ... NetBIOS computer names. ... Do the laptops EVER show up? ... might not have permissions blah, ...
    (microsoft.public.windows.server.networking)
  • Re: Network Neighborhood
    ... > As far as I know, without WINS server, there will still be master browsers ... the default setting is "Use NetBIOS setting ... > provide NetBIOS setting, enable NetBIOS over TCP/IP". ... > So there will be no problem using network neighborhood to browse client's ...
    (microsoft.public.windows.server.migration)
  • NETBIOS name already exists
    ... After re-formatting and re-installing Windows Server 2003 to correct an ... I am unable to use the same Netbios name. ... dcpromo, ... though my child domain controller was the same. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Cant connect to computers
    ... Now when in Network Neighborhood they still get access ... Warning Serious problems might occur if you modify the registry incorrectly ... NetBIOS computer names. ... Do the laptops EVER show up? ...
    (microsoft.public.windows.server.networking)
  • Re: Cisco 4500m router. Trouble routing between inferfaces
    ... Windows network neighborhood info is carried via NETBIOS over TCP/IP. ... Thus network neighbourhood will not function in a routed environment. ... try configuring IP helper-address command to helper to ...
    (comp.dcom.sys.cisco)