Child Domain NetBIOS Issue

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??

Do you have servers in the child domain? DC for replication? Try push/pull
replication from a server child --> parent domain.

"PJ" <(E-Mail Removed)> wrote in message
news:2DBCDBA3-B118-4548-B959-(E-Mail Removed)...
> 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??

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??