In-depth problems with cisco 2950 vswitch access failure

Cisco 2950 vswitches cannot access the Internet in depth. As long as you have mastered the cisco 2950 vswitch configuration skills, you can handle the cisco 2950 vswitch network loopback problems reasonably. This can quickly solve switch faults.

In-depth analysis of why the cisco 2950 switch cannot access the Internet

Is there a problem with the cisco 2950 switch faulty workstation itself? When thinking about the cisco 2950 switch, the author immediately opens the running dialog box of the system, runs the "ping 127.0.0.1" string command in it, and then returns a command similar to "Reply from 127.0.0.1: bytes = 32 time <1 ms TTL = 128 "indicates that the local loop address" 127.0.0.1 "can be pinged normally, this also means that the TCP/IP communication protocol of the faulty workstation is working normally.

In order to verify whether the NIC device of the local workstation of the cisco 2950 switch is working properly, the Ping command is used to test the connectivity of the NIC device address of the local workstation. The Ping command is successfully executed, this also indicates that the NIC device of the cisco 2950 switch faulty workstation is working normally.

Next, I tested the connectivity of the LAN gateway address in the cisco 2950 switch fault workstation. The test result is "Request timed out ", this indicates that there are some problems with the network connectivity between the local workstation and the LAN gateway device. Is it true that there is an accident with the LAN router or gateway device?

 

In-depth analysis of why the cisco 2950 switch cannot access the Internet

However, I think this is not possible because I have tested the connectivity of the LAN gateway address on my workstation before the arrival of the cisco 2950 switch's faulty workstation, it is found that it can be pinged normally. Then, carefully check the taskbar icon on the desktop of the cisco 2950 switch faulty workstation system, the local connection icon is displayed as "m connected ".

Is it possible that this cisco 2950 switch's faulty workstation is infected with a network virus, or that this workstation has installed and enabled a professional firewall program, which temporarily disables the Internet connection by the firewall program? To eliminate these possible factors, I immediately took out my laptop that I carried with me. The computer has been tested to be able to access the Internet normally.

Unplug the network cable connecting to the cisco 2950 switch fault workstation and re-insert it into the laptop. Then, open the system running dialog box of the laptop and run the string command "ping 10.176.6.1" in it ", the target gateway address cannot be pinged normally.

Later, I double-click the "local connection" icon in the tray area of my laptop system. From the local connection Status dialog box that appears later, I found that my laptop can only send data packets to external devices, the packet information cannot be received from the outside, which indicates that the failure of the cisco 2950 switch that cannot access the network has nothing to do with the failure of the cisco 2950 switch workstation system.

As a last resort, I took my laptop to a department next to the cisco 2950 switch fault workstation and inserted some network cables into my laptop, then run the "ping 10.176.6.1" string command and find that the test result is normal. Then, the author immediately performs a network access test. The result shows that the network access operation is also normal.

It is reasonable to say that all the Internet points connected after a laptop computer belong to the same working subnet. Why do some Internet points work normally while others cannot? Where exactly is the problem? Return to the cisco 2950 Switch Failure workstation. I can see that when the network cable is inserted into the interface of the corresponding Nic device, the status information displayed on the local connection icon at the system tray area is still "m connected", but the network connection is still unsuccessful when accessing the Internet!