Since the PacketShaper unit usually sits between the LAN and the WAN, when you experience a problem with the WAN link, it can be difficult to determine whether the problem is with PacketShaper, the router, or with something else on the network.
With PacketShaper, the problem could be with the hardware, software, policies, partitions, topology, etc.
You can take certain steps to isolate the problems:
1. Power down the PacketShaper unit. Does the problem go away?
When you turn the unit off, it works as a piece of wire -- the inside interface will be connected directly to the outside interface. If the problem goes away by turning off the unit, the problem is with PacketShaper.
2. Turn shaping off. Does the problem go away?
When shaping is off, PacketShaper works like a bridge. It will monitor the traffic flowing through it but it will not apply any policies and partitions. If the problem goes away with shaping off, then it is related to a policy, partition, or the link rate setting. It can also be problem with the topology.
3. The problem does not go away with shaping on or off until the unit is turned off.
It could be a hardware problem, problem with the network cards, 10 baseT/100baseT, Half Duplex, Full Duplex settings, bad cables, and so forth. Try some of the following:
* Try auto-negotiate.
* Use different cables.
* In the command line, use the net nic command to see whether RxErrors and TxErrors are incrementing fast.
* There may be an incompatibility problem with one of the devices connected to the inside or outside interface. You can put a hub in between PacketShaper and the other device to rule out any problem due to incompatibility. Topology is also a common problem.