<div class="gmail_quote">On Wed, Jan 6, 2010 at 2:40 PM, Simon Hobson <span dir="ltr"><<a href="mailto:dhcp1@thehobsons.co.uk">dhcp1@thehobsons.co.uk</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 class="im">
<br>
James Dinkel wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Oops, if this is accurate: <a href="http://www.oucs.ox.ac.uk/network/wins/winsinfo/index.xml.ID=Browsing" target="_blank">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>
</blockquote>
<br></div>
Odd. At my last job I had exactly the setup Jonathan mentions, and it "just worked" - you opened your browser and there were the workgroups for the other sites. OK it was slow as we only had 64k links, but it worked exactly the same as for just the local site.<br>
<br>
Now I've not been involved in that side of networking for a few years, so I'm not too familiar with AD etc. However, as I understand it, in an AD setup, as machines connect to the network, they will populate the DNS and other machines can find them via that - ie they don't rely on broadcasts to find other machines. But I could be wrong there.<div class="im">
</div></blockquote></div><br>Did you have a domain at your last job? If so, then that would explain why it "just worked." With a domain controller, it should just work even with just DNS.<br>