|
 |
 |
 |
|
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
Article ID: 814155 - Last Review: September 29, 2011 - Revision: 4.0 How to use Ping.exe to check your Microsoft Broadband Network AdapterThis article describes how to use the Microsoft Windows Ping.exe utility to determine if your network adapter is working. To use ping effectively, you need the following information:
- The IP address of the network adapter that you are
checking.
- The IP address of your default gateway. This may be your
base station, modem, or router, depending on how your network is
configured.
To find this information:
- Click Start, click Run,
type cmd, and then click OK.
- At the command prompt, type
ipconfig, and then press ENTER.
- Note the following information:
- The IP address of the network adapter that you want to
check.
- The IP address of your default gateway.
Use Ping.exe to Check Your HardwareTo do this:
- At the command prompt, type ping loopback
/localhost 127.0.0.1, and then press ENTER. The result should be
similar to the following:
Reply from 127.0.0.1: bytes=127 time<1ms TTL=128
Reply from
127.0.0.1: bytes=127 time<1ms TTL=128
Reply from 127.0.0.1: bytes=127
time<1ms TTL=128
Reply from 127.0.0.1: bytes=127 time<1ms TTL=128
Ping statistics for 127.0.0.1: Packets: Sent = 4, Received = 4, Lost = 0
(0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms,
Maximum = 0ms, Average = 0ms If this does not work, there may be a problem with TCP/IP on your
computer. You may have to reinstall TCP/IP, and you cannot complete the
following steps until you can successfully complete this step. - At the command prompt, type ping
network_adapter_IP_address, and then
press ENTER. For example, if your network adapter's IP address is 192.168.2.9,
type ping 192.168.2.9, and then press ENTER. The result
should be similar to the following:
Reply from 192.168.2.9: bytes=32 time<1ms TTL=128
Reply from
192.168.2.9: bytes=32 time<1ms TTL=128
Reply from 192.168.2.9: bytes=32
time<1ms TTL=128
Reply from 192.168.2.9: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.2.9: Packets: Sent = 4, Received = 4, Lost = 0
(0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms,
Maximum = 0ms, Average = 0ms If this does not work, there may be a problem with your network
adapter. - At the command prompt, type ping
gateway_IP_address, and then press
ENTER. For example, if the IP address of your base station is 192.168.2.1, type
ping 192.168.2.1, and then press ENTER. The result
should be similar to the following:
Reply from 192.168.2.1: bytes=32 time=5ms TTL=64
Reply from 192.168.2.1: bytes=32 time=4ms TTL=64
Reply from
192.168.2.1: bytes=32 time=4ms TTL=64
Reply from 192.168.2.1: bytes=32
time=4ms TTL=64
Ping statistics for 192.168.2.1: Packets: Sent = 4,
Received = 4, Lost = 0 (0% loss), Approximate round trip times in
milli-seconds: Minimum = 4ms, Maximum = 5ms, Average = 4ms If this does not work, there may be a problem with your base
station, modem, router, or network cable.
For additional information about how to troubleshoot TCP/IP in Microsoft Windows, click the following article numbers to view the articles in the Microsoft Knowledge Base:
314067Â
(http://kbalertz.com/Feedback.aspx?kbNumber=314067/
)
How to troubleshoot TCP/IP connectivity with Windows XP
169790Â
(http://kbalertz.com/Feedback.aspx?kbNumber=169790/
)
How to troubleshoot basic TCP/IP problems
APPLIES TO- Microsoft Broadband Networking 10/100 Ethernet PCI Adapter
| kbnetwork kbhowto KB814155 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
|
|
 |
|
 |
|
|
|
| |