Thanks for that, ill look into trying to get this working.
Thanks again for your help on this.
Andy C
"Bill Grant" <not.available@online> wrote in message
news:(E-Mail Removed)...
> To drive home what Todd has said, remember that browsing is an NT legacy
> program that uses Netbios names. So while permissions etc depend on your
> AD setup, browsing still works with the Netbios names of the machines and
> domains.
>
> "Todd J Heron" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Is there anyway of being able to see Child 1, Child 2 and parent in
>> network
>> neighborhood?
>>
>> A machine's workgroup or domain membership will effect how the browse
>> list
>> is initially displayed in My Network Places. That being said, you should
>> be
>> able to drill into My Network Places > Entire Network > Microsoft Windows
>> Network and there you may see other domains and workgroups on your
>> network
>> infrastrure. You may or may not be able to drill into these however,
>> depending on how trusts, accounts and permissions are set up on those
>> domains. You may not be able to see any other domains at all if the
>> domain
>> master browsers of each domain (PDCe) do not share the browse list. A
>> common reason why they would not share their browse list is because they
>> are
>> not aware of each other because they are not using the same WINS server
>> set.
>> Or, the WINS servers between the domains are not replicating (pushing and
>> pulling) with each other. You need WINS for cross-domain browsing.
>>
>> --
>> Todd J Heron, MCSE
>> Windows Server 2003/2000/NT
>> ----------------------------------------------------------------------------
>> This posting is provided "as is" with no warranties and confers no rights
>>
>>
>
>
|