Transaction Analyst
Xerox
Total years of experience :1 years, 0 Months
NETWORK PROTOCOL ANALYSER
Platform : Windows 7, Visual Studio 2008
Language : VB.Net
Role : Individual
Duration : January year to April year
Description:
Every network administrator will have the unpleasant occurrence of being paged to solve a technique problem. This can often result in a surge of emotions, panic, urgency, and maybe even a sense of heroism. The key to successfully troubleshooting a problem knows how your network functions under normal conditions. This will allow you to quickly recognize unusual and abnormal operations. One way to know how your network normally functions is to use your sniffer at various points in the network. This will allow you to get a sense of the protocols that are running on your network, the devices on each segment, and the top talkers (computers that are sending and receiving data most frequently). You may even find some things on your network that you didn’t know about, such as an old printer server that no ones uses any more and is flooding the network with broadcasts. Once you have an idea of how your network functions, you can develop a strategy for network troubleshooting. This way you can approach the problem methodically and resolve it with minimum disruption to customers. With the basic concept of troubleshooting, a few minutes spent evaluating the symptoms can save hours of time lost because you are tracking down the wrong problem. A good approach to network troubleshooting involves the following 7 steps:
1. Recognize the symptoms
2. Define the problem
3. Analyze the problem
4. Isolate the problem
5. Identify and test the cause of the problem
6. Solve the problem
7. Verify that the problem has been solve
kerala
kerala