Site under development - Call 0427 728 669 for enquiries about what I can do for your communication and technology systems.
CTRL + Scroll wheel makes the text bigger / smaller
OPERATOR: Gordon Danson
LOCATION: Toowoomba / 57 Gulligal Street Kingsthorpe 4400 - (And surrounding districts, .. prepared to travel as required)
PARAGRAPH-ONE - Please note numbers / pages v1, v2, v3, v4.html have not been created yet!
PARAGRAPH-TWO - Like I said, .. up the top of this page, "Site is under development" - If you need to contact me, .. use any of the following 0427728669 - - email@example.com
PARAGRAPH-THREE - The original site http://breakfix.info/default.html is still *HERE*
TODAY = Sunday 7th OCT 2018 - links to text pages only (v3.html, v4.html, v5.html - The original pages need to be found an uploaded, or create new x.html pages.
#1: - v5.html
#2: - v4.html
#3: - v3.html
BASIC PROCEDURE; - Requires having a solid understanding of specific technologies.
OTHER NOTEs - This is a "general guide" to trouble-shooting and NOT a linear checklist.
ANOTHER BREIF NOTE - Setting up networking can become messy, so document what you do, .. (BEFORE and AFTER making ANY configuration).
DISCLAIMER - I take no responsibility for configuration / changes that cause you to lose Internet connectivity.
Use any or all of the following as required.
WHATs HERE? (Tests to perform, and what to look for and check, BEFORE making any changes).
FIRST NOTE - Keep it simple, (If your working in a large complex environment, YOU already know what your doing, .. hence you will not be reading THIS!)
With the first note in mind, .. some of the simplest checks will tell you very quickly, .. what exactly is working, and what is not working.
TOOLs / TECHNIQUEs / METHODs TO PROCEED - (Depending on the environment / senario)
1) EXAMPLE-1, Large environment with a small data centre (relatively speaking) compared to a home test lab.
SENARIO - End user rings up reporting they cannot access there server, .. (And where do you start the trouble-shooting in this situation?) - Simples, You Ask which server they are trying to access/logon, .. and logon yourself. This simple check tells you some very important information, .. primarily weather or not the server is running, .. and that you can actually logon to it confirming connectivity.
SOURCE? (One of many) - Zen and the Art of Network Support (Chapter 20) describes how "ubertechs" fix networks, by following a plan.
Effective trouble shooting requires that you follow consistent procedures that are based on industry standards and reliable methods.
Trouble shooting is all about reducing guesswork and eliminating the obvious.
Knowing what tools are available and how to use them and formulate a troubleshooting plan, by knowing where to look for different sorts of problems. Understand and identify primary troubleshooting tools available.
Interpretation of the problem / error message usuallly needs some form of clarification to determine what action needs to be taken.
Questions directed at the person reporting the problem need to be direct, and diplomatic (depending on the situation).
Due to network connectivity being the primary thing to break / fix, start with ping
2) PING (ip address)
Where the ip address is the destination location, such as the local server, or if domestic computer with modem / ISP connection, ping something on the internet like google.com.au (188.8.131.52).
SOME ASSUMPTION MADE HERE - Your network connectivity was working, and for some reason it has stopped.
If your network has NEVER worked, good chance you need to configure the IP address and DNS entries, BOTH can be set to "Automatically-Receive" for most situations with a domestic modem / router, .. (the DHCP server will be built into the modem / router, and for the most part will not require configuration in a domestic setting).
Ping can tell you about the connection speed in milliseconds when everything is working properly.
When things are not all working, ping can tell you when IPv4 configuration is not correct. Ping can also tell you if the networking drivers are installed or NOT installed, .. I will not state this directly, .. rather the absense of information maybe presented, or even a "media disconnected" error message maybe displayed depending on the senario.
3) ISOLATE THE PROBLEM - (Working with the blackbox procedure)
Couple of methods here, essentially both very similair.
The blackbox method can be described as systematically swapping out components of the system, for known-good / working components, (one at a time, so that you indentify which component is faulty in this way).
As the sub-heading suggests, .. remove components that are making a diagnosis ambiguous.
Sometimes this method will be the only way to confirm exactly what the problem is.
Sometimes this method can be very time consuming, but it usually returns a result.
4) DIAGNOSTIC SOFTWARE - (Utilities specific to some sub system)
Install and test what the problem might be, there are many of these out there.
May create a page about this soon, .. (maybe not), .. as you can see there is backlog of pages here to create content for.
5) SEARCH - (Using the Internet to find a solution to your problem)
Construction of GOOD search strings can find you any thing and everything, .. (Getting the answer question depends on a well constucted search string)
EXAMPLE-1; Some of the basics of finding stuff? http://members.upc.nl/a.horlings/doc-google.html
EXAMPLE-2; VIDEO https://archive.org/details/Fravia_Reversing_our_searching_habits_Power_searching_without_google
- 1) Logon to the server
- 2) ping (ip address)
- 3) Isolate the problem
- 4) DIAGNOSTIC SOFTWARE
- 5) SEARCH
#4: - v4.html