<div class="gmail_quote">On Wed, Jan 6, 2010 at 1:41 PM, James Dinkel <span dir="ltr"><<a href="mailto:jdinkel@gmail.com">jdinkel@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5"><br><br><div class="gmail_quote">On Wed, Jan 6, 2010 at 1:27 PM, Jonathan Lassoff <span dir="ltr"><<a href="mailto:jof@thejof.com" target="_blank">jof@thejof.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Excerpts from James Dinkel's message of Wed Jan 06 11:18:08 -0800 2010:<br>
<div>> Your workstations should have no problem finding the servers across subnets<br>
> using DNS.<br>
<br>
</div>DNS can work for Active Directory I believe, but what if the users want<br>
to use or want their "Network Neighborhood" stuff to work?<br>
Sadly, I don't believe this uses DNS.<br>
<font color="#888888"><br>
</font></blockquote></div><br></div></div>I don't believe that was brought up as an issue.<br><br>Network Neighbor will not use DNS to populate it's list but I believe it will use WINS, so you could set up a WINS server if you wanted users to be able to browse each other in Network Neighborhood. Personally though, I would rather have Network Neighborhood be empty and set up login scripts to map drives to the shares I want the users to have access to.<br>
</blockquote></div><br>Oops, if this is accurate: <a href="http://www.oucs.ox.ac.uk/network/wins/winsinfo/index.xml.ID=Browsing">http://www.oucs.ox.ac.uk/network/wins/winsinfo/index.xml.ID=Browsing</a><br>It looks like you will still not be able to browse computers across subnets even with WINS. But as I said, I personally would prefer to not have that functionality anyway. And since WINS is a deprecated technology, that's further motivation to just stick with DNS.<br>