In article , cwshultz@mvps.org
says...
> Leythos,
>
> Are we talking about WIN2000 or WIN2003?
>
> Essentially, it does not matter as you will need NetBIOS name resolutions
> either way. The forest trusts that you created ( probably using NETDOM from
> the Support Tools ) are based on DNS resolution. If you want those "other"
> Forests to show up then you need NetBIOS name resolutions - as mentioned.
> This could be accomplished via WINS or via LMHOSTS files.
>
> WINS might be a whole lot easier.
Cary,
Since DNS information replicates between the forests, and since I can
map shares using the FQDN, I don't see a need for Wins or a hosts file.
Neither a Wins server or a Host entry will make the other forest show up
in the network neighborhood list. It's not a matter of not being able to
reach the other forest, it's a matter of when I click on "My Network
Places" and then "Entire Network" and then "MS Windows Network", that I
want to see Forest 1, Forest 2, Forest 3, etc...
This is all based on Forest 1 being Windows 2003 Server, Forest
2,3,4,5... being Windows 2000 server. Each office was installed as it's
own Forest before the though of connecting them to each other was put in
place.
>
> HTH,
>
> Cary
>
>
> "Leythos" wrote in message
> news:MPG.1aaa6637faffd2a098a288@news-server.columbus.rr.com...
> > Ok, now that I have all my forests trusted with each other for Admins, I
> > would like to be able to click through My Network and then Entire
> > Network, and see all the other forests listed so that I can uses them as
> > easily as the subdomains in the local forest.
> >
> > I can connect to them using their shares, but I don't have a clue as to
> > where to start looking for making the other forests show up in the
> > entire network list.
> >
> > Thanks.
> >
> > --
> > --
> > spamfree999@rrohio.com
> > (Remove 999 to reply to me)
>
>
>
--
--
spamfree999@rrohio.com
(Remove 999 to reply to me)