Your network consists of a single Active Directory domain named contoso.com.
You have a server named Server1 that runs a custom network application. Server1 has the following IP
addresses:
192.168.15.10
192.168.15.11
You need to ensure that a client computer resolves server1.contoso.com to only the 192.168.15.11 IP address.
What should you do from the computer?
A.
Edit the hosts file.
B.
Edit the lmhosts file.
C.
Run Ipconfig.exe /flushdns.
D.
Run Netsh interface ipv4 reset.
Explanation:
1072 20116
Differences between the HOSTS and LMHOSTS files in Windows NT
In Windows NT, the HOSTS file is for TCP/IP utilities, and the LMHOSTS file is for LAN Manager NET utilities.
If you cannot PING another computer (using a friendly name), check the HOSTS file. If you cannot NET VIEW
a server using only the TCP/IP protocol, check the LMHOSTS file.
Hosts file
The Hosts file is a common way to resolve a host name to an IP address through a locally stored text file that
contains IP-address-to-host-name mappings. On most UNIX-based computers, this file is /etc/hosts. On
Windows-based computers, this file is the Hosts file in the systemroot\System32\Drivers\Etc folder.
The following describes the attributes of the Hostsfile for Windows:
A single entry consists of an IP (IPv4 or IPv6) address and one or more host names.
The Hosts file is dynamically loaded into the DNS client resolver cache, which Windows Sockets
applications use to resolve a host name to an IP address on both local and remote subnets.
When you create entries in the Hosts file and save it, its contents are automatically loaded into the DNS
client resolver cache.
The Hosts file contains a default entry for the host name localhost.
The Hosts file can be edited with any text editor.
Each host name is limited to 255 characters.
Entries in the Hosts file for Windows-based computers are not case sensitive.
The advantage of using a Hosts file is that users can customize it for themselves. Each user can create
whatever entries they want, including easy-to-remember nicknames for frequently accessed resources.
However, the individual maintenance required for the Hosts file does not scale well to storing large numbers of
FQDN mappings or reflecting changes to IP addressesfor servers and network resources. The solution for the
large-scale storage and maintenance of FQDN mappings is DNS. The solution for the maintenance of FQDN
mappings for changing IP addresses is DNS dynamic update.
NOT LMHOSTS File
The LMHOSTS file is a local text file that maps IP addresses to NetBIOS names of remote servers with which
you want to communicate over the TCP/IP protocol. W indows recognizes names instead of IP addresses for
network requests and a name discovery process is used to correctly route network requests with TCP/IP.
Because the name discovery process is generally notrouted by an IP router, the LMHOSTS file allows
Windows machines to communicate using TCP/IP acrossa subnet.
LMHOSTS contains IP address to “NetBIOS over TCP/IP” name translations.
LMHOSTS is only used by the NBT (NetBIOS over TCP/IP) interface.
LMHOSTS file contains some valuable additions to the LAN Manager and Windows for Workgroups
LMHOSTS file, such as the ability to support routeddomain logon validation.
LMHOSTS contains static information about TCP/IP addresses, but using logon scripts and/or the replicator
service, the “master” file can be distributed transparently across all stations.
By default, the LMHOSTS file should be located in the directory %SYSTEMROOT%\SYSTEM32\DRIVERS
\ETC (usually C:\WINNT\SYSTEM32\DRIVERS\ETC).
Other info
http://support.microsoft.com/kb/105997