|
| |||||||||
| Tags: lan, wan, wan failures, wan port, wan troubleshooting |
![]() |
| | Thread Tools | Search this Thread |
|
#1
| |||
| |||
| How to quickly rule out from the WAN failures
Hi all, For frequent dropped LAN failure, I believe that most network administrators can readily adapt the solution, but if the phenomenon of the Internet frequently dropped in place in wide-area network, then the phenomenon is more trouble to solve, in order to effectively improve the wide-area network frequently dropped Trouble efficiency, I want the common troubleshooting steps and solutions for WAN failures. Please help. Thanks in advance. |
|
#2
| ||||
| ||||
| How to quickly rule out from the WAN failures
If the WAN through Routing Device to a network connection, then the discovery of the phenomenon of wide-area network frequently dropped, you can quickly log into the local router admin interface and in which the implementation of the Ping command to the other devices connected router WAN port address to send Test Data packets, to take a look at the other WAN port can be Ping. Check and reply |
|
#3
| ||||
| ||||
| How to quickly rule out from the WAN failures
If the WAN is routed through the three-tier Exchange equipment for network connections, then we might as two lines in the wide area network are connected to a workstation, and in turn to each workstation and the IP address of set-up costs to the three-tier routing Exchange Machines connected by wide area network interface address, and then log into the workstation, open the operation of the system dialog box, and enter the string in which the command "Ping xxx.xxx.xxx.xxx-t" (where xxx.xxx.xxx.xxx is the other WAN port of the IP address), click "OK" button, the results from the subsequent pop-up interface to see the other side of the WAN ports can be Ping. All the best.
__________________ 90% of everything is crap...except for crap, because crap is 100% crap |
|
#4
| ||||
| ||||
| Re: How to quickly rule out from the WAN failures
If the Ping command Test operation is successful, it shows the WAN line no packet loss, which can prove that the physical line service providers is a good line, resulting in failure of the Internet frequently dropped the most likely cause is that the workstation system itself, which requires us to to further rule out the workstation if there is a problem. If the Ping command to test the above-mentioned operation is unsuccessful, that is the WAN line has undergone an obvious phenomenon of data packet loss, which prove that most of the Internet often dropped from the fault-line service providers caused by the physical line, when we line service providers must be invited to send a special technical staff to solve the physical line fault. Check and reply
__________________ Truly, if there is evil in this world, it lies within the heart of mankind. -Edward D. Morrison Old soldiers never die- they just fade away. |
|
#5
| ||||
| ||||
| How to quickly rule out from the WAN failures
The exclusion of the WAN circuit factors, network failures are mostly from the line at both ends of the system caused by the workstation at this time we need to narrow the scope of troubleshooting, find out whether it is a problem with the local workstation, or other workstations, the system is down. At this point, let us at both ends of the line corresponding to each of the LAN network to find a workstation, and then open the Run dialog box on each workstation, and the implementation of strings in which the command "Ping aaa.aaa.aaa.aaa-t" (of which aaa.aaa.aaa.aaa local LAN gateway address), and then the results from the pop-up interface to determine the client workstation to the local LAN gateway connectivity is normal. Check and reply. |
|
#6
| ||||
| ||||
| How to quickly rule out from the WAN failures
Frequently dropped in the WAN failure occurs, we should stop and carefully analyze the phenomenon of network failure, then the integrated use of equipment substitution, one by one investigation method, network cable plug method and other methods, gradually narrow the scope of troubleshooting and accurately find the the specific location of the failure, determine the correct network problems caused by the reasons for, and finally select the appropriate measures to solve the fault phenomena. At present, along with the crazy network virus outbreak, wide area network fault line may encounter the phenomenon largely caused by a network virus, so we recommend a good wide-area network systems should be equipped with anti-virus system, while the introduction of network traffic monitoring functions and IDS intrusion detection functions in order to effectively prevent various types of networks from viruses, improve the wide area network system Safe Prevention capabilities, to ensure that the WAN line away from the frequent dropped calls or other symptoms. All the best. |
![]() |
|
| Thread Tools | Search this Thread |
| |
Similar Threads for: "How to quickly rule out from the WAN failures" | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Help - add policy rule | microms | Operating Systems | 1 | 10-12-2011 11:44 PM |
| AT&T Starts No Tethering rule | Ilampirai | Portable Devices | 5 | 07-06-2011 11:07 AM |
| 3 Hit rule in Vampire war | rafael n | Video Games | 4 | 10-03-2011 05:58 AM |
| Does stress testing rule out bad RAM/CPU | Kohlmann | Motherboard Processor & RAM | 6 | 16-05-2010 07:48 AM |
| rule out ODBC connection? | ed | Active Directory | 2 | 27-01-2010 07:03 PM |