Differences

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

--- faq:network_troubleshooting [2021/03/05 11:15 (3 years ago)] – kevin
+++ faq:network_troubleshooting [2021/03/05 13:01 (3 years ago)] – 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)
@@ Line 30: / Line 32: @@
 ===== Have a Plan B =====
-When a local network 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.  Restoring from backup to a different server may not seem like a great plan now.  But when it can take days to get parts for a failed server resource, operating on a slower second option will seem like a good option to have.
+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>