| Mental Patient on Thu, 14 Mar 2002 19:56:00 -0500 |
|
On Thu, 2002-03-14 at 18:38, W. Chris Shank wrote: > isn't wins only used for SMB routing across subnets? these machines would all > be on the same network. > > No. Wins is a centralized service where win32 clients go to find out who has what name. On large networks this is very important. Without wins, you will have a significant amount of broadcast traffic as every box 'announces' itself to every other box. Wins make that not happen. You can also use wins to facilitate smb connectivity across subnets. > > >internal DNS box? I've been perusing how-to's, bit i'm a little dense and > > >need something in simple language. > > > > Have you considered using a hosts file? > yes. but this network is likely to grow over time and i may not be the one > who manages it (for a church), so i wanted to have it as Plug n Play as > possible, in case someone decides to buy a new machine and 'just plug it in' hosts files are most certainly not the way to go. They scale badly. An ideal solution would be to setup a name server with some sort of dynamic dns. This would probably be a non-trivial task, but it would require next to no maintenance until you ran out of DHCP leases. You could probably use something along the lines of this: http://www.thismetalsky.org/files/dhcp_dns/ If all you're worried about are windows file shares, you will not need a name server. You should be fine with just a WINS server. If for some reason you'll need names to resolve for non-smb purposes, then dynamic dns is the way to go. -- Mental (Mental@NeverLight.com) Is it weird in here, or is it just me? --Steven Wright GPG public key: http://www.neverlight.com/Mental.asc Attachment:
signature.asc
|
|