Hardware Error Ping Wireless
to another device in the network, rarely you may receive one strange error Hardware error instead of proper replies from the destination device. In most cases ping hardware error is followed with disabled Network Adapters. Some users report they see hardware error when they ping from a computer just after wake the system from sleep mode. You may also receive hardware error when you ping with unplugged Ethernet cable on a computer. So let us check the common reasons for getting hardware error while you ping a different IP address from a computer and also find the fix. To get the better view of the Ping Hardware error, look at the image below. Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Documents and Settings\vi83>ping 4.2.2.2 Pinging 4.2.2.2 with 32 bytes of data: Hardware error. Hardware error. Hardware error. Hardware error. Ping statistics for 4.2.2.2: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Documents and Settings\vi83>ping 4.2.2.2 Reasons for Getting Ping Hardware Error The possible reasons for getting hardware error when you ping to an IP address are: Bad Ethernet cable Disconnected Ethernet cable Disabled Network Adapter How to Resolve Ping Hardware Error Message By following the steps below we can troubleshoot and resolve ping hardware error. Unplug and reconnect Ethernet cable. Check if the Adapter is enabled. To check and enable Ethernet adapter on your computer follow the steps mentioned in the link below. How To Enable Disabled Ethernet Adapter On Your Computer Restart your computer Replace the Ethernet cable. Replace the NIC and check for the issue. Other ICMP Error Messages and Solutions 1. Ping error message Destination net unreachable 2. ping; transmit failed, error code 10045 solution of the error 3. ICMP error Destination Host Unreachable Home Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: ICMP Error Messages at 10:51 PM Posted by Alex George 2 comments: Alan Lodge said... Confusingly, you can also get "hardware error
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: Ping is giving hardware error Windows Vista IT Pro > Windows Vista Networking Question 0 Sign in to vote I have 2 Lans and two switches and routers i have the 2 machines with primary and backup Lans primary are connected to primary switch and backup is cnnected to secondary switch . those machines IP adresses are 170.25.1.1--> primary Lan 170.25.2.1 --->secondary LAN 170.25.1.2--> primary Lan 170.25.2.2--->secondary LAN subnet mask is 255.255.255.0 for two lans http://www.corenetworkz.com/2009/05/ping-gives-hardware-error.html is same. Default gateway 170.25.11.140 for primary lan machine Default gateway 170.25.12.140 for secondary lan machine if i disable the primary lan of (170.25.1.1) this machine manually by right clicking the network icon and disable it. after this it is pinging to 170.25.1.2 and 170.25.2.2 these machines but if i pull the LAN physically after this if i ping the second machine with is iP 170.25.2.2 it is https://social.technet.microsoft.com/Forums/windows/en-US/bcbb6066-ea8d-4c9f-9515-e54259fc8acf/ping-is-giving-hardware-error?forum=itprovistanetworking working fine but if i ping 170.25.1.2 this address it is giving hardware error. Eventhough i pull the LAN it has to ping my secondary machine primary lan 170.25.1.2 for this where to change ? and how to configure my routers to ping other machines if i remove the LAN Please give me the solution am in urgency. appreciate any suggesstions. Thanks KK Sunday, October 14, 2007 9:25 AM Reply | Quote All replies 0 Sign in to vote It looks as if the issue you faced is: After you disabled the primary network adapter (170.25.1.1) on the machine (we call it computerA), it unable to ping the IP address 170.25.1.2 which is assigned to the other machine (we call it computerB). Additionally, I see that the IP address of default gateway for the secondary network adapter on computerA is 170.25.12.140 but not the IP address where is the same subnet as secondary network adapter (170.25.2.0). It may cause computerA fail to communicate with secondary LAN if its primary network adapter is disabled. To confirm it, would you share me the Route Table on computerA? You may dis
'General Discussion' started by moerl, Mar 23, 2006. moerl Network Guru Member I'm on quite an adventure here.. just check out the second half or so of this thread and the related one here. Whereas at first the problem seemed to http://www.linksysinfo.org/index.php?threads/hardware-error-when-pinging-router.13688/ be with the router, I am now, after flashing to Thibor 14, convinced that it is my system. I just don't know how this happened or why it's occurring.. but when I unplug my ethernet cable to test the wireless link and then ping the router using command prompt, I just get this: Seconds after plugging the ethernet back in and repeating the same exact command, everything works fine! I get a reply and all. The strange thing about all this hardware error is here... All of these are for the wireless connection. Windows is telling me everything is fine, essentially! But why on earh does my wireless connection not work? I just don't get it. I've changed the channel on which the router broadcasts the wireless signal to "2". Do wireless NICs automatically switch to the correct channel when they find a connection? This shouldn't even matter though, because as you can see, I HAVE a standing connection. moerl, Mar 23, 2006 hardware error ping #1 Toxic Administrator Staff Member try reconnecting the wireless connection without the LAN cable in place Toxic, Mar 23, 2006 #2 moerl Network Guru Member Toxic said: try reconnecting the wireless connection without the LAN cable in placeClick to expand... Just tried that. I just never get past ACQUIRING NETWORK ADDRESS. Well, unless acquiring a network address is supposed to take hours... moerl, Mar 23, 2006 #3 Toxic Administrator Staff Member ok try uninstalling and the reinstall the wireless drivers. dont use the lan cable at all. this will add false DHCP info to you computer as it is trying to access the net via the lan adapter all the time. make sure first of all the WRT has no encryption or mac filtering in place to start with. Toxic, Mar 24, 2006 #4 moerl Network Guru Member I tried a million things. Finally I loaded a fresh disk drive image onto the system, with just about nothing installed. It was so fresh I didn't even have display drivers, audio drivers or anything installed. That way I wanted to make sure I'm dumping all sorts of factors out of the problem equation.. like registry tweaks, conflicting software installations, driver corruption.. And guess what, it worked! Wireless works again, but I still cannot connect to my own router. I use WPA encryption on my router, with Thibor 14 as I said, and the router is working flawlessly. I prefe