DNS, NETBIOS, DHCP and WINS

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: JohnDeeze (JohnDeeze_at_discussions.microsoft.com)
Date: 12/12/04 

Date: Sat, 11 Dec 2004 18:37:02 -0800

I am new to networking, although i am helping administer a network and would
like someone to explain the following to me:

I believe the following to be an accurate picture of Windows networks.

NETBIOS - Is the Name of the PC e.g. (PC1)

DNS resolves the IP address of the PC against a pc's name, therefore if i
ping PC1 it will return reply from PC1 and give me its IP address.

Reverse DNS resolves the IP address of a PC to the NETBIOS/DNS name,
therefore if i ping 10.1.1.1 it will return the name of the PC e.g. PC1.

WINS resolves the name of the PC for older pc's like Win NT and Windows 98
as DNS was not in play or DNS has since taken over WINS duites

DHCP assigns an available IP address to a PC which logs onto the network,
provided the pc has "obtain an IP address automatially" in its network TCP/IP
options.

Question 1 - Why not just do away with WINS as 98/NT have DNS options in
their network TCP/IP properties. Why did we need WINS?

Question 2 - On an NT/98 PC do i need to insert a DNS server address in
TCP/IP properties box if i have those PC's WINS server properties in netowrk
TP/IP pointing to the WINS server?

Quesrion 3 - Why is there an option saying use NETBIOS over TCP/IP in
network card properties?

Question 4 - Why do we require reverse DNS?

Question 5 - If the name of the PC sits on the DNS server do we still use
NETBIOS

Any help assistance greatly appreciated

Relevant Pages

  • Re: Help with initial small org AD setup convention when using DMZ network
    ... Consider using Dynamic DNS internally (aka Active Directory Integrated ... > firewall which then connects the public IP dmz network to a private IP ... > domain name for such subnets based on the nearest airport code, ... > servers to serve acme.com names for external users. ...
    (microsoft.public.win2000.active_directory)
  • Re: About DNS naming convention for Active Directory
    ... Here's what I did so far, I set up a private network consists of the ... I did an in-place upgrade of the NT4 PDC to Active Directory 2003, ... I had no DNS service at all. ... Joined the 2003 Server as a member server and that went well too. ...
    (microsoft.public.windows.server.dns)
  • Re: IE cant connect to any sites
    ... On the General tab in the Temporary Internet Files Folder, ... Click on "LAN Settings" and make sure everything is blank, ... Network settings ... IP address automatically", click on the DNS tab, disable DNS here, click ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: Error Message
    ... On the General tab in the Temporary Internet Files Folder, ... Click on "LAN Settings" and make sure everything is blank, ... Network settings ... IP address automatically", click on the DNS tab, disable DNS here, click ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: How do my server 2003 (DNS) know the Internet?
    ... The Multihomed function is not for Internet access. ... has an ip of 156.40.10.10 for that network. ... It is due to a number of reasons, mainly DNS registration of both NICs, whereas you do not want that. ... It's highly recommended to single home all DCs and use a non-DC for the multihoming purposes. ...
    (microsoft.public.windows.server.dns)