Differences

This shows you the differences between two versions of the page.

--- faq:network_troubleshooting [2020/03/30 11:29 (4 years ago)] – kevin
+++ faq:network_troubleshooting [2021/08/03 17:10 (3 years ago)] (current) – kevin
@@ Line 1: / Line 1: @@
+See [[https://support.windwardsoftware.com/a/solutions/articles/66000481186]]
 ====== Network Troubleshooting ======
 In order for Windward Software products to function correctly in a network environment, there needs to be adequate network infrastructure.  By network infrastructure, we mean a professionally cabled network with reliable network cards and switches.  A properly configured server, DNS and TCP/IP protocol for our applications and other network services will be required.  If things are not working as they should, this document may give you some ideas on what to check and consider.
@@ Line 14: / Line 16: @@
   * Are there any patches available for the server hardware?  Firmware such as RAID card, network card, BIOS?
   * Could line voltage be an issue?  Any large motors, compressors or welding devices nearby?  You may want to consider some power conditioning.
-  * Check for pending Windows updates on all workstations/servers involved.  Strange things can occur when updates have not been applied a server degrades into a "reboot pending" state.
+  * Check for pending Windows updates on all workstations/servers involved.  Strange things can occur when updates have not been applied and a server degrades into a "reboot pending" state.
-  * Check settings for power saving options and disable.  We have seeing OS updates reset power-saving settings.
+  * Check settings for power saving options and disable.  We have seen OS updates reset power-saving settings.
   * 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, or other power-hungry devices in the same building (even outside the company) can cause power brownouts which can cause pieces of equipment to fail during startup of the power-hungry device)  Install a UPS and if it is beeping every few minutes, you may have a power issue.
@@ Line 26: / Line 29: @@
   * 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 hardcoded on workstations?  This can be overlooked and can cause 30-second timeout delays while DNS fails over to a working DNS server.
+  * Have you swapped internet providers and left old DNS information hardcoded on workstations?  This can be overlooked and can cause 30-second timeout delays while DNS fails over to a working DNS server.  Due to the round-robin and caching nature of DNS, System Five will work sometimes and have a long delay at other times.
+  * 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.  Although great to restore the server to a known point in time, do not configure restore points to be created automatically during production hours of the business.
+  * 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.  This is a great primary action but consider and start moving a Plan B in the event that healing the network does not work.  This can decrease downtime experienced and will often show areas that can be improved for Business Continuity Planning.
+<note tip>Example:  Restoring from backup to a slower server may not seem like a great plan at the beginning.  When it can take days to get parts for a failed network component, operating on a slower second option will eliminate downtime if it is available.</note>