Re: DNS conditional forwarding

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

"aconti" <aconti.3tp8zd@xxxxxxxxxxxxx> wrote in message
news:aconti.3tp8zd@xxxxxxxxxxxxxxxx

ok so if I just configure all the clients to use the same Wins Server
through the DHCP server options then both networks on both sides will be
able to browse eachother. I tought that Wins was an old system and it is
not being used however I was wrong then !

WINS has its functions and features that differ from DNS. WINS is not an old
'system' but rather a service. In the terms of being 'old,' it's been around
since the 90's, and it even has its own RFC by the IEEE defining WINS as a
NetBIOS name server (NBNS), which also defines *nix NBNS servers.

WINS is a dynamic NetBIOS name database. DNS is a dynamic hierarchal
hostname database. The hierarchy starts with the TLD, then the domain name,
then a host name, etc. NetBIOS is not hierarchal, but a flat namespace
developed back in the 80's to identify machines before the importance and
popularity of hostname support (DNS). The differences are WINS allows to
support legacy and current applications that require NetBIOS name resolution
(SQL, Exchange-Outlook communication for certain functions, Browser serice,
and many others). If WINS is in use, the Microsoft Browser Service will pull
data from it to assemble a browse list. When you click on Network
Neighborhood on any machine, it queries the Master Browser to get the list.
Therefore, if all machines in an infrastructure ares using WINS, and they
all successfully register their NetBIOS name and NetBIOS services into the
WINS database, the Browser service will pull that data, and then you will
see them in Network Neighborhood.

Unfortunately, the Browser Service does not use DNS.

I hope that helps to explain why WINS is needed in the scenario you've
described.

Ace



.

Relevant Pages

  • Re: Computer \computername cannot be managed because it is not running Windows NT
    ... the other computer/client which 'wants' to manage it via Server ... 'NetBIOS over TCP/IP' is disabled. ... little to nothing to improve network security. ... disabling 'NetBIOS over TCP/IP' and therefore loosing 'My Network ...
    (microsoft.public.windowsxp.security_admin)
  • Re: The specified network name is nolonger available
    ... the "The specified network name is nolonger ... > works, NetBIOS is working. ... > you can substitute server with computer if that helps your understanding. ... Edit your LMHOSTS file. ...
    (microsoft.public.win2000.networking)
  • Re: Cannot browse the network after migration
    ... the cause is the multiply NICs are all enable NetBT. ... >>> browse the network. ... >>> 189101 Understanding NetBIOS Resource Record Flags ... >>> NetBIOS setting from the DHCP server. ...
    (microsoft.public.windows.server.migration)
  • FIXED: Not all computers see server...
    ... The NETBIOS over TCP/IP cured the problem and retained my firewall ... > domain mixed-mode network with DHCP and DNS, ... This was due to needed to connect with older machines ... After installing the server software and making the new server ...
    (microsoft.public.windows.server.networking)
  • Re: Server not appearing in Network Places
    ... This is what the issue was, somehow netbios over tcp/ip was set to disabled. ... See the link below on how to troubleshoot the browser service including how ... it and use the command net config server to see if it is configured to be ... Network Places. ...
    (microsoft.public.cert.exam.mcse)