Tag Archives: Ping

Troubleshoot a Slow Computer Network – Only One Computer on the Network is Slow

Only One Computer on the Network is Slow

Client Computer Network Mask Wrongly Configured
Your network is a class C network, (net-mask 255.255.255.0), and your client computer has its IP address configuration on a class B network, (255.255.0.0). Change the network mask of the client to match the network configuration.

Poor network cards
Bad network cards or bad drivers are very often the reason for poor transfer rates. Test the transfer rate with a different network card.
An outdated computer can also slow down your network transfer.

Bad Network Configuration
DNS Configuration
can be the cause a of slow network connections.
Wrong DNS address in the IP configuration can slow your network dramatically. Your DNS client will try to connect to an inexistent or not working DNS server then give up and try your secondary DNS server. This translates in slowdowns and sometimes even DNS resolution errors.
Fix: Ping the DNS address or, even better, use nslookup and connect to both of your DNS servers to check if they work.

The TCP/IP protocol stack corrupted.

Sometimes no matter what you do you can’t fix the network and this is because the TCP/IP becomes corrupted. The only thing that fixes it is a reset. On older Operating Systems, such as Windows 98 and Windows NT, the fix was to uninstall and reinstall the whole TCP/IP suite of protocols.
Fix: issue the following command to reset it: netsh int ip reset c:\resetlog.txt.

More Than One Default Route
Advanced Lan SettingsA very common mistake is to assign more than on default route to the same computer. Do not confuse load balancing with multiple Default Gateways. You are configuring two network cards, and both of them have a default gateway. This configuration will not work. Usually, a Windows computer will warn you that this is not a good idea, but some users will choose to ignore the warning.
This is a typical problem for laptop users, they connect into the Lan environment and leave the wireless connection on. This will create a lot of problems for corporate users and even for home users.
In order for this type of configuration to work, special routing rules and IP configuration is needed. it is easier to turn the wireless of or have an adapter manager that will automatically do that for you based on your rules.
Advanced Tcp/IP Settings
On a Windows XP there is a way to assign priorities to network cards using a graphic interface. from the Network Connections applet in the Control Panel, click on the Advanced menu and choose Advanced Settings.
On the Advanced Settings window arrange the network cards according to the correct priority.
Another way to achieve this is to change the gateway’s metric for each of the network adapters on the computer. To do this, open the TCP/IP properties on each of the network addapters with a default gateway configured, and click on the Advanced button. On the Advanced TCP/IP Settings window, uncheck the Automatic Metric for the Default Gateway, and enter a value according to your network topology. The lower the metric, the higher the preference for a default route.

This article is part of a five posts series regarding Network Troubleshooting.

Browser Auto-config and Wpad deployment

Using a Proxy Server in your Company’s Network is one of the best decisions you have made.
But this decision can bring you some administration overhead if you don’t have an automatic way to provision the browser settings.
Fortunately, for Microsoft Operating Systems there is a way to accomplish this.
The procedure involves a configuration file that tells browsers how to connect to Internet.
This file is published via the existing Infrastructure using DNS, DHCP and a WEB Server.

Create the configuration file

Create the wpad.dat file inserting the following text:
function FindProxyForURL(url, host) {
return "PROXY 192.168.100.10:3128; DIRECT";
}

IIS

Create a new website and link it to a folder of your choice, (for instance c:\wpad). Place the wpad.dat file inside the folder.
Create a mime type for the .dat  file type with the mime type  “application/x-ns-proxy-autoconfig”.
Restart IIS. If you already have an IIS just place the file in the root directory.

Apache:

Create the wpad.dat file on the www directory depending on your distribution (on a Debian is /var/www/).
For instance:
#nano /var/www/wpad.dat
would open the nano editor. If nano is not install use vi or mcedit or any other text editor.
Edit httpd.conf:
#nano /etc/apache/httpd.conf
and insert the following line:  
AddType application/x-ns-proxy-autoconfig .dat

Make sure apache daemon is starting at boot time, (update-rc.d  apache2 defaults)
Restart apache #/etc/init.d/apache2 restart.

DHCP – Configuration for Proxy Auto discovery

(on a Microsoft DHCP server)

  1. Click Start, point to All Programs, point to Administrative Tools, and then click DHCP.
  2. In the console tree, right-click the applicable DHCP server, click Set Predefined Options, and then click Add.
  3. In Name, type WPAD.
  4. In Code, type 252.
  5. In Data type, select String, and then click OK.
  6. In String, type http://internalserver/wpad.dat where:
    • internalserver is the domain name of the Server that hosts the wpad.dat file. (Alternatively you can use fully qualified domain name, (eg. http://internalserver.domain.local:3129/wpad.dat)
    • Port is the port number on which automatic discovery information is published. You can specify any port number. I put 3129.
  7. Right-click Server options, and then click Configure options.
  8. Confirm that Option 252 is selected.

If you configure this on a Unix DHCP server you might need to add an extra blank character at the end of the DNS Configuration
Create an alias (CNAME) with the name wpad pointing at the webserver that hosts your wpad.dat file. For instance the alias is wpad and the fully qualified domain name is internalserver.domain.local

Troubleshooting

WPAD alias DNS entry not responding
After creating your alias when you ping wpad you get host not found this could be related to a security improvement on Microsoft’s DNS servers.
To fix this you need to edit the following registry value: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters\GlobalQueryBlockList
Edit this on all of your Microsoft DNS servers and remove wpad from the list of values. See the image below:

Registry Fix for Implementation of WPAD

Note that this configuration requires you or your user to configure your browser to “Automatically Detect Settings”.
For Internet Explorer this can be automatically configured for all the users in an Active Directory domain via a Group Policy.
The same policy will be used by Google Chrome, which uses the Windows Internet Connection configuration.
Other browsers such as Opera, and Mozilla will have to be manually configured. Alternatively, for an automatic configuration they can be tweaked via registry hacks or configured via third party software.
The disadvantage with manual configuration is of course the cost of deployment and the fact that this can be changed by the user. If you want to enforce the use of the proxy you have to restrict the gateway access and allow only the proxy machine to access it. Another way would be to configure your proxy to be your router and set up a transparent proxy.