Category Archives: Network Troubleshoot

A collection of posts to help you troubleshoot a slow network or bad network.

Snagless RJ45 connectors – How To Make Network Cables Snagless

Patch Panel

Snagless RJ45 Connectors – the Odd Request

Snagless RJ45 connectors are that odd request that my department makes from time to time. Why do you need RJ45 connectors anyway, it’s the invariable answer from supervisors, and the typical reminder: “You have all sorts of patchcords, all dimensions…” Well, first of all, we sysadmins never have all the patchcords dimensions available. The IT racks should be something that should be kept as tidy as possible, and one way is to have custom length of the patchcords.

Depending on your infrastructure, you might want or might not want to use handmade patchcords in your racks; however, in many cases this is totally acceptable. You can probably make a Cat 5 patchcord, but you won’t be able to make a Cat 6 one. In other words your hand made patchcords will be able to run at Gigabit speeds, but not at 10 Gigabit speeds, even with the proper connectors and cables. Having said that, most of the equipment in a business server room is connected into a Gigabit switch or at lower speeds, so this would not be a problem.

Custom Patchcords – Always Broken Lokcing Tabs

The major problem with all the handmade Ethernet patchcords and cables is that the locking tab is breaking. I probably don’t have to explain why broken tabs are bad; they will not be secured into the equipment’s jack, resulting in intermittent data loss, or even disconnection.

There are two reasons for the locking tabs breaking so often. Firstly, the little locking tab is very fragile, and we can’t change that, it is fragile to keep the costs down. The other reason is the design, the locking tab sticks out, and it is very easy to get snagged and broken off. All store-bought cables come with a snagless boot; it’s the standard these days. All the cables with broken locking tabs don’t have the boots, because they are terminated in place, by either a datacom tech, or an admin.

These plugs from Panduit are the best snagless RJ45 connectors.

The connectors are meant for patch cords, and they are rated as providing Category 5e performance.

The patented tangle-free plug latch prevents snags, hence breaking.

They are easy release, unlike some snagless boots, and they save time on frequent moves, adds, and changes.

The design facilitates easy insertion and termination of wires

What Is the Solution for Broken RJ45 Connectors

One of the solutions to fix the snagging network cables is to install a "snagless" boot over the cable, before crimping the connector. After crimping, just push the boot over the connector and the boot will protect the little tab.

My preferred way to fix this is to use snagless RJ45 connectors, and a boot. This ensures the plug will not break ever, unless you purposely do it. You can also use just the snagless connectors, they are very good, and I do it very often, but if I have both the snagless connectors and the snagless boots, I will use both for optimization. The snagless plugs are slightly more expensive than the regular ones, but when you draw the line, and consider the troubleshooting needed on the long term, and the fact that sooner or later those RJ45 connectors will break and will need to be replaced, the additional cost is worth paying.

Like I already mentioned before, with the low prices for commercial made patchcords, and the quality ensured by a machine made ethernet cable, there is no need to make your own, it's just not practical.

This cables are made in a commercial facility, they are tested, and they come in a variety of lengths, just choose the one that is right for you. You can even get  to choose the color, so you can color code your patch panel connections, so everything looks tidy, and easy to follow.

How to troubleshoot a slow computer network?

Troubleshoot Network - Ping
Pinging Google

Your network is slow. What do you do to make it faster?
The answer is not simple and the reason for your slow network could be a lot of things. You have to take a step by step approach and isolate the bottleneck. Once you isolate the point of failure it is easier to find the problem.

Many times a packet sniffer will help you find the problem faster. A good free packet sniffer is Wireshark. Another packet sniffer is Microsoft Network Monitor.

Here is a list of Windows-based network tools that can help you troubleshoot almost any problem in a Computer Network:
Ping – a network utility to test if a computer is up and reachable or not. Ping uses the ICMP protocol to send echo requests.
Nmap – a port scanner. You need a port scanner to enumerate open ports and live IP addresses.
Tracert – a utility that traces the path of a network packet enumerating all of the routers that it passes through.
Wireshark – a packet sniffer.
Netstat – a utility that enumerates all the open ports on the local computer.
Ipconfig – a utility to list or modify the properties of a network adapter.
Netsh – a powerful Windows utility to modify various network properties. It is a scripting utility that basically controls every aspect of the Network on a Windows computer.
One of the cool usages of the netsh is to reset the TCP/IP stack to the defaults without the need to uninstall and reinstall the TCP/IP protocol as we needed with the older OSs.
Route – enables the view and manipulation of routing.
Nslookup – a name resolution utility. Very useful to check DNS servers and validity of name records.
Arp – a utility that allows you to get information about MAC address to IP address resolution.
Getmac – Provides the MAC address and lists associated network protocols for all network cards for a local or remote computer.
Getname – displays the computer name.
PathPing – Combines the functions of Traceroute and Ping, very powerful tool.
Net services commands – Performs a broad range of network tasks such as Network mapping, authentication, controls services, etc…

If you are not sure how to use these tools read the Help or from the command line, (all of these are command line tools), issue the command with the help option, for instance: “pathping /?”. This will give you a list of other valid options.  

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

  1. How to troubleshoot a slow computer network?
  2. Troubleshoot a Slow Network – The entire Network is Slow
  3. Troubleshoot a Slow Network – Slow Server
  4. Troubleshoot a Slow Computer Network – Only One Computer on the Network is Slow
  5. Troubleshoot a Slow Computer Network – Your Computer is Slow and Not the Network

Troubleshoot a Slow Computer Network – Your Computer is Slow and Not the Network

Slow Data Transfer is not Always caused by the Network

Slow data transfers are sometimes caused by a slow computer. Determine if the computer is the reason by comparing the transfer speed with a different computer connected on the same switch port. If the speed is the same, the problem is your network. If you get faster data transfers with a different computer then the problem is the computer.

A computer could be slow because of various reasons:

A bad network card. Troubleshoot: Swap the network card and test the data transfers afterwards.
The computer is outdated and it runs software that needs more resources. Troubleshoot: change the computer.
Slow hard-drive. The hard-drive will always be the computer’s bottle neck. It is the slowest part of a desktop computer. Old hard-disks are very often seen in new computers. Hard-disk fragmentation is a frequent reason for slow computers. Troubleshoot: Defragment often your hard-drive and reserve a 25% free space on the drive.
The computer might be infected with a virus or a Trojan. Troubleshoot: scan the computer for viruses. On a Windows machine run the command “netstat -a -b” to see what ports are being used and which program is using them. Use a network sniffer and monitor the network activity on the specific computer.
The transfer is intermittently slow, check what background processes are using the CPU, Memory, and hard-drives. Windows Vista can sometimes be a resources hog by allocating too many resources for background processes such as indexing and running the antispyware. Antivirus or other antimalware can consume a lot of the computers’ resources. Troubleshoot: Change the schedule for maintenance tasks to a time when you are not using the computer. Check what other programs are running in the background and configure accordingly. Some antivirus programs enable scanning the network drives by default.
A slow network printer. A slow network printer can be caused by the power save feature. If you use the printer very often you might consider turning off the power save.
A slow Network Attached Storage device. A slow NAS could be caused by improper SAMBA configuration or a disk power save feature. The power save feature is fairly easy to fix, just disable it if you find that you are using the drive very often. The SAMBA tune up is more difficult and usually it is complicated to have terminal access to the device itself. Many manufacturers do not allow direct access to the OS. SAMBA is a free implementation of Microsoft’s SMB protocol. SAMBA, SMB and CIFS offer file and print sharing services for Windows and Linux/Unix machines

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