Re: Slow Performance when connecting to any network interface
- From: Chuck <none@xxxxxxxxxxx>
- Date: 27 Jul 2005 16:31:02 -0500
On Wed, 27 Jul 2005 13:47:04 -0700, "chalkfarmer"
<chalkfarmer@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>"Chuck" wrote:
>
>> On Wed, 27 Jul 2005 07:01:09 -0700, "chalkfarmer"
>> <chalkfarmer@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>>
>> >> Thanks for letting us know. But what of the contents of the Hosts file? Is the
>> >> computer in question a domain member? If so, the domain should provide the
>> >> Hosts file equivalent. If the computer is not a domain member, though, there
>> >> are other solutions to this problem.
>> >> <http://nitecruzr.blogspot.com/2005/07/local-name-and-address-resolution-on.html>
>>
>> >The hosts file contained the IP addresses and the hostnames of all the
>> >servers in our domain, so in case the DNS server went down the users would
>> >still be able to access the data servers.
>> >The slow performance problem occured on computers that were part of the
>> >domain as well as those that no longer were part of our domain.
>> >
>> >Can you please tell me more about the Domain providing the hosts file
>> >equivalent.
>> >
>> >Thanks again.
>> >Dmitry.
>>
>> Dmitry,
>>
>> There is no actual relationship between domains and name resolution. Both
>> domains and workgroups may, or may not, use server based name resolution. If
>> your network has no server, DNS, or WINS, it will use either Broadcast, or will
>> need a Hosts or LMHosts file.
>> <http://nitecruzr.blogspot.com/2005/07/windows-networking.html>
>>
>> The existence of Hosts predates the Internet, and DNS. When TCP networking was
>> first developed, Hosts was the only method of name to address resolution. As
>> the Internet became popular, trading Hosts entries became impossible, and DNS, a
>> dynamic, hierarchical Hosts equivalent, was developed.
>>
>> Using a Hosts or LMHosts file for resolution has advantages and disadvantages.
>> Advantages:
>> # It's local on the computer, so quickly available.
>> # You can customise it for each computer.
>> Disadvantages:
>> # You have to update it on each computer.
>> # You have to update it whenever a change is made.
>> # When it gets large, any changes to it will slow the system significantly.
>>
>> The latter disadvantage is one which many using a Hosts file based website
>> blocking strategy learn about. When you have a large Hosts file, on a network
>> without DNS, you turn the DNS Client service off.
>> <http://nitecruzr.blogspot.com/2005/07/local-name-and-address-resolution-on.html>
>>
>> Obviously, using Hosts for a DNS backup, and for bad website blocking, is a
>> contradictory activity. Many purists say that using Hosts for security is an
>> incorrect use anyway.
>Thank you Chuck for your clarification.
You're welcome, Dmitry. It's fun to put all these thoughts together.
--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
.
- References:
- Slow Performance when connecting to any network interface
- From: chalkfarmer
- Re: Slow Performance when connecting to any network interface
- From: Chuck
- Re: Slow Performance when connecting to any network interface
- From: chalkfarmer
- Re: Slow Performance when connecting to any network interface
- From: Chuck
- Re: Slow Performance when connecting to any network interface
- From: chalkfarmer
- Re: Slow Performance when connecting to any network interface
- From: Chuck
- Re: Slow Performance when connecting to any network interface
- From: chalkfarmer
- Slow Performance when connecting to any network interface
- Prev by Date: Re: Slow Performance when connecting to any network interface
- Next by Date: Re: Internet conection keeps failing
- Previous by thread: Re: Slow Performance when connecting to any network interface
- Next by thread: Peer to Peer networking VS> Server-Client Networking
- Index(es):
Relevant Pages
|