Re: DNS, NETBIOS, DHCP and WINS
From: Steven L Umbach (n9rou_at_n0-spam-for-me-comcast.net)
Date: 12/12/04
- Next message: John Wunderlich: "Re: DNS, NETBIOS, DHCP and WINS"
- Previous message: Amy L.: "IPSECPOL.EXE Questions"
- In reply to: JohnDeeze: "DNS, NETBIOS, DHCP and WINS"
- Next in thread: John Wunderlich: "Re: DNS, NETBIOS, DHCP and WINS"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 12 Dec 2004 05:13:11 GMT
There are two types of computer names in the Windows world - netbios "flat"
names and dns "host" names. Netbios names are single words such as
computer1. Host names are computers that are a member of a domain as in
computer1.mydomain.corp. Now usually the netbios name of a computer in a
Windows domain is the first name in the FQDN.
Before Windows 2000 all the Windows operating systems used the netbios names
to locate computers in the Windows domain. Windows 200o still usually does
in a workgroup. However in an Active Directory domain, all W2K/XP Pro/W2003
domain computers always try to resolve a computer name using host name/dns
name resolution first. If a computer is referred to by it's netbios name,
the W2K domain computer will append the domain name to the computer name and
send it off to the dns server for name resolution. If that fails it will
still try netbios name resolution asking first the wins server [if used]
and then if that fails it will resort to broadcasting. Hosts and lmhosts
files can also be used in the name resolution process.
NT4.0/W9X computers will only use netbios name resolution for a netbios
name. They will however use host name/dns if they receive a FQDN that has a
period in it [as all FQDN do] such as for a website. However in an AD domain
NT4.0/W9X computers still refer to all Windows computers by their netbios
names including domain controllers which is why wins is needed for those
computers. Wins is used to dynamically register netbios names of wins
clients and make them available to wins clients for netbios name resolution
rather that broadcasting. Wins also is used by W2K/XP Pro computers in
network browsing [My Network Places] , so they can benefit from wins also
and it is necessary for browsing the network across subnets including VPN.
To answer your questions.
1. You can not do away with wins for W9X as they still need it to find
computers on the network via netbios name resolution, including domain
controllers. If you look in the wins database you will see many different
records to help wins clients not only resolve netbios computer names but
locate records for domain controllers and master browsers. While W2K/XP
Pro/W2003 computers can locate domain controllers via dns, W9X computers are
not capable of reading the _srv records that are used to locate them.
2. You should also configure W9X computers with a dns server so they can
resolve FQDN such as websites.
3. Netbios over tcp/ip is necessary for netbios name resolution. If you do
not want to use it for some reason you can disable it. Usually this is done
on W2K/XP Pro/W2003 computers that have no need to use netbios name
resolution and are using strictly dns and port 445 for file and print
sharing.
4. Reverse dns is used to resolve IP addresses to domain names. This can be
for convenience or security in some cases to help determine more information
about an IP address possibly in case a user is trying to bypass a domain
name/url restriction by using IP address instead of name.
5. Again netbios name resolution is needed for W9X/NT4.0 computers anytime
they are referring to a computer by their netbios name rather than FQDN.
Steve
"JohnDeeze" <JohnDeeze@discussions.microsoft.com> wrote in message
news:6EAE852B-A8C4-45A9-AD48-E740B3CC1435@microsoft.com...
>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
- Next message: John Wunderlich: "Re: DNS, NETBIOS, DHCP and WINS"
- Previous message: Amy L.: "IPSECPOL.EXE Questions"
- In reply to: JohnDeeze: "DNS, NETBIOS, DHCP and WINS"
- Next in thread: John Wunderlich: "Re: DNS, NETBIOS, DHCP and WINS"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
