none
CE 5.0 ping: transmit failed, error code 11010.

    Question

  • Static IP assigned. I can ping "google.com". so, the network is ok, the DNS is ok. But I can't ping another PC. I got the message:

    ping: transmit failed, error code 11010.

    I used Microsoft Network Monitor to monitor the network trafic:

    31	14:36:37 2013/1/22	7.6310813		192.168.0.171	192.168.0.170	ICMP	ICMP:Echo Request Message, From 192.168.0.171 To 192.168.0.170	{IPv4:9}
    34	14:36:37 2013/1/22	7.6316752		192.168.0.170	192.168.0.171	ICMP	ICMP:Echo Reply Message, From 192.168.0.170 To 192.168.0.171	{IPv4:9}
    52	14:36:39 2013/1/22	8.9771624		192.168.0.171	192.168.0.170	ICMP	ICMP:Echo Request Message, From 192.168.0.171 To 192.168.0.170	{IPv4:9}
    53	14:36:39 2013/1/22	8.9773987		192.168.0.170	192.168.0.171	ICMP	ICMP:Echo Reply Message, From 192.168.0.170 To 192.168.0.171	{IPv4:9}
    
    192.168.0.170 is the PC. 192.168.0.171 is CE 5.0 device.

    Tuesday, January 22, 2013 7:18 AM

Answers

  • OK. Can you try putting a switch in between the two systems??

    I mean:  System 1 <-> Ethernet Switch <-> System 2.

    • Marked as answer by Percy Xu Wednesday, January 23, 2013 2:01 AM
    Tuesday, January 22, 2013 8:41 AM

All replies

  • Hi Percy,

    This error code 11010 generally means "Error due to lack of resources." You can check this link . Somewhere I read that when there is no reply from the host, this error comes up. Even It had happened to me a few times when I pinged google.com while testing my wifi driver.

    If you want to ping to other PC, you can first look into your IP address and other PC's (which you want to ping) IP addresses are on the same subnet. The IP address details and manually settings you can find in Control Panel.

    Hope this helps

    Tuesday, January 22, 2013 7:26 AM
  • Hi deepak_,

    Thank you for the reply.

    The CE device and the PC are in the same subnet connected with a hub. The ping to the PC always fails with no exception.

    The IP addresses of them are 192.168.0.170 and 192.168.0.171. The mask is 255.255.255.0.

    Tuesday, January 22, 2013 8:00 AM
  • OK. Can you try putting a switch in between the two systems??

    I mean:  System 1 <-> Ethernet Switch <-> System 2.

    • Marked as answer by Percy Xu Wednesday, January 23, 2013 2:01 AM
    Tuesday, January 22, 2013 8:41 AM
  • You mean use a switch instead of the hub?
    Tuesday, January 22, 2013 8:51 AM
  • Its a hub..
    Tuesday, January 22, 2013 9:03 AM
  • I changed to a switch, It works, The CE system can ping other PC now. But other PC cannot ping it.
    Wednesday, January 23, 2013 1:51 AM
  • Oh, that's good Percy...

    Check for subnet masks and ip addresses in both the systems.

    Check for Antivirus and Firewall settings on the other machine....once disable these two and then try...
    • Edited by deepak_ Wednesday, January 23, 2013 5:19 AM
    Wednesday, January 23, 2013 5:03 AM
  • Hi All,

      I am using the WinCe 6.0 device  to connect with the back end server.

    When I trying to ping the server from the device  am getting transmit failed, error code 11010 .

    If the any PC or other Device in same subnet 192.34.78.X to 192.34.78.Y - am able to ping from both the end,

    If the server is other subnet 192.36.78.X  - I cant able to ping and getting error transmit failed, error code 11010".

    It will be great if I get any helping hand to resolve this issue.

    Thanks in advance.

    Friday, March 25, 2016 3:08 AM
  •  I had the same problem. When deactivate the firewall, works fine.

    Rogério Sobreira


    Sobreira

    Thursday, June 16, 2016 11:32 PM
  • I run into the same problem, I believe I found the RC.

    In my case, it only happens when then handheld is roaming from one AP to another AP with the same SSID but diffrent BSSID. The catch is that they have different gateway setting.

    When the roaming happends, if the SSID is the same , the handhelds route table is not updated, the default gateway and routing path stays the same. You can check this in Start>Run [ cmd ] > route print.

    The fix is simple, just rename the APs ensure every AP with different gateway, use a different SSID, ( though this may create management problme... ). So that when the handheld roaming from one to another, it can update route table correctly.


    • Edited by Benten Zha Saturday, June 09, 2018 1:11 AM
    Saturday, June 09, 2018 1:11 AM