Ping your Loopback127.0.0.1Use the Loopback IP address of 127.0.0.1 with the Ping command to troubleshoot local machine network connectivity. From the command prompt type in ping 127.0.0.1 and it acts as an electronic sonar which will return a number of "packets lost" if you have a problem on your computer. What is the path though? What are you actually testing? And what are the possible problem areas? Start with basic troubleshooting: Check your Network Connections:
Mark sure the connection you are trying to use is Enabled. As you can see above....I always disable the connection I am NOT using. Start | Run | type in: cmd | type in: ping 127.0.0.1Everything else here only deals with all packets being lost. 1) Protocol StackBelow: Right click on the connection and select Properties. Scroll down, make sure TCP/IP is installed, if it is not, this is a problem. Resolve this via Control Panel | Add/Remove Programs | Add/Remove Windows Components.
In Device Manager a Red X will show over a disabled component. (it is hard to see). An exclamation point or a question mark denotes a problem. Select Configure: on the General tab, refer to Device Status and refer to this Microsoft Support page for more information on error codes.
2) Network Card DriversThe Loopback test also employs the driver. From the Properties of the device select Configure, and the Driver tab. If you have discovered a possible driver problem using Device Manager you may resolve that here.
3) The Network Card ItselfIf your TCP/IP protocol is installed and the software or drivers for your network card show no signs of problems, the last thing on THIS list is the card itself. If possible test connectivity with another card, preferably an external card first. Can you borrow a USB device from a friend?If all your software checks have not turned up a problem you are left with a hardware issue. Continue Using Ping in my Network
|
