A. Checking the Network ConnectionFor the network administrator of a LAN or local network computer, a computer problemcan not access data on the server would have become commonplace in the face.Followingare tips for the novice network administrators, the things you can do when experiencingproblem as aboveAs a network admin, can sometimes lead to feelings of frustration if notcan find the cause or source of the problem on a computer that can not be connectedto the network or can not access data on the server after they were login / log onto the network.Here are tips on what steps to take if experiencing this.Checking steps are: 1. Check the network card or network card is installed, whether it has been recognized by the operating system,for the Windows operating system can be done by checking the control panel and then selectsystems.
2. If not known or there is an error with the network card, try to remove or deleted inthen re-installed using the driver (software program for the network card) fromthe appropriate network card.
3. If the network card is OK and is known by the operating system. For the environmentusing TCP / IP tries to use the ping utility in the operating systemWindows, Linux or UNIX. but before doing ping, can be seen how IP addresses ofcomputer by using a command or command 'winipcfg' operating systemWindows 9.x or 'ipconfig' to windows NT/W2K. Or to the environment based on * nix, canusing the command 'ifconfig'.
Example:
C:> ipconfigWindows 2000 IP ConfigurationEthernet adapter Local Area Connection:
Connection-specific DNS Suffix. :
IP Address. . . . . . . . . . . . : 155.35.119.246
Subnet Mask. . . . . . . . . . . : 255.255.0.0
Default Gateway. . . . . . . . . : 155.35.119.1
From the above example it was found that IP address is 155.35.119.246.
And subnet masknya255.255.0.0, subnet mask serves as the determination of segments in the network or sharelarge network into smaller networks. If the default gateway that works if wewill communicate with other computers outside our network or outside of our network segment.For the segment will be discussed in another article to come.
Then we try to ping the IP address of that computer.
Example:
C:> ping 155.35.119.246
Pinging 155.35.119.246 with 32 bytes of data:
Reply from 155.35.119.246: bytes = 32 time <10ms TTL = 128
Reply from 155.35.119.246: bytes = 32 time <10ms TTL = 128
Reply from 155.35.119.246: bytes = 32 time <10ms TTL = 128
Reply from 155.35.119.246: bytes = 32 time <10ms TTL = 128
Ping statistics for 155.35.119.246:Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0msIf you get results like the above, setting the network card is recognized by the systemoperation. The next step is to try to connect to computers on the same network.
4. To check the connection to other computers in the same network, can also be doneby using the ping utility as above.
For example, say our friend's computerits IP address 155.35.119.138, assuming the same segment of the subnet masknya255.255.0.0
Example:
C:> ping 155.35.119.138Pinging 155.35.119.138 with 32 bytes of data:
Request timed out.Request timed out.Request timed out.
Request timed out.
Ping statistics for 155.35.119.138:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0msNote that the message is different from that obtained earlier in which the message isindicate which package you send to the computer does not respond to ICMP protocolor alias 'timed out' or packets that are sent do not reach the goal for a certain time (TTL -Time To Live).So does that mean we are still problematic computer?The answer is not necessarily, be it a computer with IP address 155.35.119.138 is not active ornot turned on or not connected to the network.So we need to find another computer that would target the connection to the network is nothave problems at all.
For instance, 137 IP addresses active then we try againping to the IP 137 is like the example below:
C:> ping 155.35.119.137
Pinging 155.35.119.137 with 32 bytes of data:
Reply from 155.35.119.137: bytes = 32 time <10ms TTL = 255
Reply from 155.35.119.137: bytes = 32 time <10ms TTL = 255
Reply from 155.35.119.137: bytes = 32 time <10ms TTL = 255
Reply from 155.35.119.137: bytes = 32 time <10ms TTL = 255
Ping statistics for 155.35.119.137:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:Minimum = 0ms, Maximum = 0ms, Average = 0msIf we get a response like the above when using the ping utility to another computerwhich is also connected to the network, it stands to reason that our computers are connectedproperly.
Hopefully SUCCESS...
Description : TIPS AND TRICKS TESTING NETWORK CONNECTION
URL : http://indra-combination.blogspot.com/2012/03/tips-and-tricks-testing-network.html
Permalink : TIPS AND TRICKS TESTING NETWORK CONNECTION
URL : http://indra-combination.blogspot.com/2012/03/tips-and-tricks-testing-network.html
Permalink : TIPS AND TRICKS TESTING NETWORK CONNECTION
