« Lieberman and the election
Firefox Red Carrot/Gray Bar Fixes »
Aug 09 2006

Fixing the “pinging °ÿ with 32 bytes of data” error in Windows XP

Posted by: biggandy, in Computer

CMDJust had this problem come up and took a while to google it out.
A Windows XP machine can sometimes have its WINSOCK catalog become corrupted and it appears like a network connection is disabled. Well, this is not always the case. If you perform a

PING -a -n 1 127.0.0.1

Ping the loopback connection at the COMMAND prompt you will see this as the hostname reply:

pinging °ÿ with 32 bytes of data

That °ÿ is the telltale sign that the WINSOCK catalog is corrupted. Simply enter this command at a command prompt:

netsh winsock reset catalog

and reboot the machine. The problem will be cleared up.

This entry was posted on Wednesday, August 9th, 2006 at 1:55 pm and is filed under Computer. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
del.icio.us:Fixing the  digg:Fixing the  spurl:Fixing the  newsvine:Fixing the  furl:Fixing the  reddit:Fixing the  fark:Fixing the  Y!:Fixing the 1,548

9 Responses to “Fixing the “pinging °ÿ with 32 bytes of data” error in Windows XP”

  1. Andrea says:
    March 6th, 2007 at 10:23 pm

    Thank you for having high google ratings and the answer to my problem! Now back to fixing the trojan that started this fiasco…

  2. Lamsidjan says:
    April 30th, 2007 at 3:01 am

    Thx a lot.

  3. Augusto says:
    May 16th, 2007 at 11:54 am

    It´s a great trick… Thanks for the answer.

  4. Francois says:
    November 6th, 2007 at 4:57 am

    excellent thank you very much for this solution

  5. Kris says:
    November 21st, 2007 at 4:59 pm

    Thank you so much. I was ready to pull my hair out!!!

  6. Nick says:
    December 4th, 2007 at 6:06 pm

    Thanks you So Much! This problem was driving me crazy. I had tried so many things to fix it. I finally googled the pinging error and your page was the second result. Great information and it worked perfectly!

  7. mohan kumar says:
    January 14th, 2008 at 5:43 am

    Thanks you so much…
    thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…thanks…

  8. ian says:
    January 24th, 2008 at 5:47 am

    this worked for Server 2k3 SP2 on the first shot after me trying several dns configuration changes and reboots with no avail. thank you so much for posting.

  9. Chris McElroy says:
    March 27th, 2008 at 3:16 am

    This problem was driving me nuts and this worked first time. Thank you so much.

    Now I want to know why this fixed it.

Leave a Reply

You must be logged in to post a comment.