Slow Performance when connecting to any network interface

[Guest]

Hello All, I have a problem with laptop running XP pro SP2, once it is taken
outside the corporate network. Once a computer is connceted to a network
interface such as a Switch or a Hub, the performance slows to a grind...
It does not matter where it is connected or to what network. The computer is
fine when the network card is not connected.
I have taken Filemon and Regmon captures as well as Network packet captures,
in addition to Performnce logs of the Processor System and Hard Drive
parameters. So far I have not been able to see what is wrong.

Has anyone ever seen such a case?
Any help would be greately appreciated.
Thank you in advance.
Dmitry.

 

[Guest]

Sounds like a DNS problem. When off the corpnet, it's looking for an
unavailable DNS server. Your may have to modify the TCP/IP properties to
prevent it from looking for your corpnet's DNS server. Ideally, both the
corpnet and the outside network should provide a DNS server automatically,
rather than having it hard-coded in the TCP/IP properties. Check Settings,
Network Connections, Local Area Network, Properties, TCP/IP, Properties.

 

[Chuck]

Hello All, I have a problem with laptop running XP pro SP2, once it is taken
outside the corporate network. Once a computer is connceted to a network
interface such as a Switch or a Hub, the performance slows to a grind...
It does not matter where it is connected or to what network. The computer is
fine when the network card is not connected.
I have taken Filemon and Regmon captures as well as Network packet captures,
in addition to Performnce logs of the Processor System and Hard Drive
parameters. So far I have not been able to see what is wrong.

Has anyone ever seen such a case?
Any help would be greately appreciated.
Thank you in advance.
Dmitry.

Dmitry,

Many computers, carefully configured for one network, may experience problems
when removed form the network. See if this article provides any ideas:
<http://nitecruzr.blogspot.com/2005/05/have-laptop-will-travel.html>

 

[Guest]

Thank you Chuck and Ted for the suggestions. In looking at DNS I discovered
that the hosts file was causing the slowdown. Removing all entries in the
hosts file solved it.
Thanks again, you pointed me to the right answer.

dmitry.

 

[Chuck]

Thank you Chuck and Ted for the suggestions. In looking at DNS I discovered
that the hosts file was causing the slowdown. Removing all entries in the
hosts file solved it.
Thanks again, you pointed me to the right answer.

dmitry.

Dmitry,

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>

 

[Guest]

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.

 

[Chuck]

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.

 

[Guest]

Thank you Chuck for your clarification.

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.

 

[Chuck]

Thank you Chuck for your clarification.

You're welcome, Dmitry. It's fun to put all these thoughts together.