Does "Request timed out" ALWAYS mean a hardware error? What else could cause this return?
Request timed out could also be a routing error. Meaning the originating machine thinks there is a route to the host (i.e. not a "No route to host" error) but that route is invalid, or incorrect. Boiled down, a time out error means that the target of the ping did not answer, but the sender machine thinks that it knows how to reach the target.
I suppose it might also mean that the host could be down. If you ping an IP that is valid on your subnet, but not actually assigned to any active machine, it will return a time out error. Same thing happens if you ping an Internet address that is down.
Thank God! I thought I was absolutely out of it. I have installed a working NIC (pinged fine in another box before AND after this test) and this problem still exists. Thanks again, 800XL. My other thread holds the root of this problem.
Jin Vitas~Do you have any thoughts/suggestions? All/any help is appreciated by one that is gyrating about with no end in sight.
I must now bow to the Masters....and ask for real assistance.
The easiest way to explain it is.. source system cannot find destination system due to cable, hardware issues on network.. or incorrect subnet or the destination system is down... and when it tries to find it..and cannot the packet explodes... the TTL, the hops.. runs out then the packet explodes.. in generic terms..
New Security Features Planned for Firefox 4
Another Laptop Theft Exposes 21K Patients' Data
Oracle Hits to Road to Pitch Data Center Plans
Microsoft Preps Array of Windows Patches
Microsoft Nears IE9 Beta With Final Preview
Simplified Analytics Improve CRM, BI Tools
Android Passes RIM as Top Mobile OS in 2Q
VMware Updates Hyperic System Management
File Monitoring Key to Enterprise Security
LinkedIn Snaps Up SaaS Player mSpoke