A solid, dependable network is the cornerstone of a trouble-free system.
If the network is "down" or there are intermittent network problems,
the software will not work at its peak level of performance. The following
is a guide to help diagnose and correct network problems.
Network Components
Here is a brief description of the three main components in a standard
network.
Network Interface Card
This is the device in the computer that allows it to communicate with other
computers. It can be found on the back of most computers and is just a
jack similar to a phone jack, but it is twice as wide, and has one or
two green lights.
Network Cable
The cables are usually gray or light blue and the cable ends look similar
to a phone line (clear plastic) but they are twice as wide (eight pins
instead of four pins). The cable connects each computer in the system
to the Network Hub or, in some cases with two terminal systems, directly
connects the two terminals.
Network Hub or Switch
The Network Hub or Switch is a small metal box with 4 to 16 jacks and a
corresponding number and light for each jack. There should be a Network
Cable leading from each of the computers connected to the Hub. There is
also a jack labeled "Uplink' or "Crossover', used for connecting
a second Hub or Switch. This should NEVER be used unless there is more
than one Hub or Switch being used (usually only sixteen terminal systems
or above).
Possible Causes of Network Problems
There are four main problems that can cause a network to function improperly:
Connection problems
Problems with cables or cable ends.
Hub or Switch failure
Hardware failure on the Hub or Switch.
Network Interface Card failure
Hardware failure on Network Card in a PC.
Windows Configuration or Driver problems
Network configurations in Windows or a corrupt or incorrect driver for
the Network Interface Card.
Determining Extent of Problem
The first step in diagnosing network problems is to ascertain how extensive
the network problem is: how many terminals are logged into the network,
if any. To determine which terminals are logged into the network, exit
to Windows and double-click "Network Neighborhood'. This will open
a window with a list of computers identified by each computer's network
name. Double-Click each computer name to verify that Windows can access
the computers listed. If the computer is logged on, a Folder labeled "C'
will be displayed. If the computer is not logged into the network, the
computer name will not be displayed or Windows will display a message
"Windows cannot find \\ComputerName\. Please check share name and
try again'. Click on the "Back' button at the top of the window and
double-click on the next computer name until all computers have been tested.
Repeat this on each terminal and determine which computers are logged
on the network and which computers are not logged on. If there is only
one terminal that is not logged on to the network, follow the steps for
Single Terminal Network Failure. If there are no terminals logged on to
the network, follow the steps for Multiple Terminal Network Failure.
Single Terminal Network Failure
The following is a step-by-step list of possible solutions for a network
problem that is isolated to a single terminal. After completing each step,
retest the network by double-clicking "Network Neighborhood' or search
for the other terminals by name by clicking "Start', "Find'
"Computers', type in the network name of one of the other terminals
and click "Find now'. If the computer name appears in the box below,
double-click the computer name to verify that it can access the computer's
"C' folder. This will determine whether or not the terminal has logged
on to the network.
Check network cable
Verify that the cable is plugged in firmly to the back of the computer,
and plugged in firmly to the hub. Also verify that the corresponding green
light on the hub is lit, and then retest the network.
Reboot the computer
Click on "Start', "Shutdown', check "Restart' and click
on "OK', and then retest the network.
Log off computer and log back on
Click on "Start', "Log off <Username>', "Yes', "OK',
and then retest the network.
Verify that Windows did not install a second network card.
Click "Start', "Settings', "Control Panel' and double click
"Network'. In the white box towards the top on the screen, there
should only be one item with a green icon in the list, not including a
Windows Dialup Adapter. The name of the Ethernet card i.e. "Realtek
10 / 100 Ethernet Adapter' will be displayed next to the green icon. If
there is a second adapter with a green icon (other than "Dialup Adapter',
the Windows dialup adapter should not cause any problems) then highlight
the second adapter and click "Remove'. Reboot the terminal and retest
the network.
Multiple Terminal Network Failure
The following is a step-by-step list of possible solutions for a network
problem that involves all terminals on the network, rather than a single
terminal. If the entire network is down, then the Network Neighborhood
on each terminal will only display itself. After completing each step
on the list, retest the network by double-clicking "Network Neighborhood'
or search for the other terminals by name by clicking "Start', "Find'
"Computers', type in the network name of one of the other terminals
and click "Find now'. If the computer name appears in the box below,
double-click the computer name to verify that it can access the computer's
"C' folder. This will determine whether or not the terminals have
logged on to the network.
1.Check the Hub or Switch
Most total network failures occur because there is no power to the hub.
Verify that the power cable to the hub is connected and the green power
light is lit. Also, verify that all network cables are connected and have
a green light lit, one for each connection. Retest the network.
2.Reset the Hub or Switch
Disconnect the power cable from the hub, wait ten seconds and then reconnect
the power cable.
3.Reboot all Terminals
Click on "Start', "Shutdown', check "Restart' and click
on "OK'. Repeat this on all terminals and then retest the network.
The Last Resort- Changing Servers
As a last resort, after attempting the previously mentioned steps to correct
network problems, you can configure Maitre'D to run on the Emergency server.
The Emergency server maintains the financial information stored on the
server, allowing to quickly switch over to the Emergency server if the
primary server is down.
Networking computer
Industry Standard Category-5 Network Cable
Straight-Thru Pin-out
Pin1
WHITE\ ORANGE
Pin2
ORANGE
Pin3
WHITE\ GREEN
Pin4
BLUE
Pin5
WHITE\ BLUE
Pin6
GREEN
Pin7
WHITE\ BROWN
Pin8
BROWN
Network Crossover Cable
Connect 2 PC's directly without hub / concentrator
