faq:network_troubleshooting
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
faq:network_troubleshooting [2019/08/26 10:13 (5 years ago)] – [Things to consider when things go wrong] derek | faq:network_troubleshooting [2021/08/03 17:10 (3 years ago)] (current) – kevin | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | See [[https:// | ||
+ | |||
====== Network Troubleshooting ====== | ====== Network Troubleshooting ====== | ||
- | In order for Windward Software products to function correctly in a network environment there needs to be adequate network infrastructure. | + | In order for Windward Software products to function correctly in a network environment, there needs to be adequate network infrastructure. |
===== Best practices ===== | ===== Best practices ===== | ||
* Purchase quality network switches, hardware, use professional cabling and patch panels. | * Purchase quality network switches, hardware, use professional cabling and patch panels. | ||
- | * Buy patch cables instead of building your own. For the cost, it is not worth the dollar savings. | + | * Buy patch cables instead of building your own. For the cost, it is not worth the dollar savings. |
+ | * Ask your IT professional to review information from a network analyzer such as [[http:// | ||
===== Things to consider when things go wrong ===== | ===== Things to consider when things go wrong ===== | ||
* Check the server event log for any message or hints towards what may be failing. | * Check the server event log for any message or hints towards what may be failing. | ||
- | * How old is the hardware? | + | * How old is the hardware? |
- | * Could the server drive be failing? | + | * What is new? Has anyone brought a device or switch in from home or plugged something in? |
+ | * Could the server drive or controller | ||
* Are there any patches available for the server hardware? | * Are there any patches available for the server hardware? | ||
* Could line voltage be an issue? | * Could line voltage be an issue? | ||
- | * Check for pending Windows updates on all workstations / servers involved. | + | * Check for pending Windows updates on all workstations/ |
- | * Last resort mainly due to the expertise level required | + | * Check settings for power saving options and disable. |
+ | * Check for bad or failing ports on switches that are not consistent (Even new ones can fail) | ||
+ | * Ports auto-detecting incorrectly (ie: 10Mb detected on the switch when the server is transmitting at 100Mb) | ||
+ | * Incorrectly crimped cables (Even store-bought cables can fail and mice will eat working ones and they will still operate some of the time) | ||
+ | * Poorly routed cables (Don’t run parallel with power wires as magnetic fields will cause corruption) | ||
+ | * A switching loop or bridge loop in the network. (e.g. multiple connections between two network switches or two ports on the same switch connected to each other). | ||
+ | * Network cards that randomly fail but work most of the time (Poorly crafted operating system drivers can cause this type of issue as well) | ||
+ | * Other environmental considerations (Newly installed welders, air conditioners, | ||
+ | * Is there a duplicate IP address that conflicts with the server or workstation? | ||
+ | * Is there another DHPC server conflicting with yours? | ||
+ | * Are you using Voice over IP phones on the same network as your data? The best networking practice would be to configure a separate VLAN for phone traffic to allow the data network to communicate without competing with packet priority over voice data. | ||
+ | * Is there any third-party software installed such as State or Provincial level tools that could impact VPN or network access? | ||
+ | * Have you swapped internet providers and left old DNS information | ||
+ | * Server restore points being made can cause the database service and System Five to become unresponsive while the restore point is being created and can cause database timeout errors. | ||
+ | * Intrusion Prevention Software (IPS) which can cause network overhead and slow performance doing scans. | ||
+ | |||
+ | ===== Have a Plan B ===== | ||
+ | When a networking event takes place, often IT resources get solely placed into troubleshooting and healing the network. | ||
+ | |||
+ | <note tip> |
faq/network_troubleshooting.1566839599.txt.gz · Last modified: 2019/08/26 10:13 (5 years ago) by derek