Winsock Error, Ping °_ Options

[NickTheGreek]

If you encounter this :

"Pinging °_" instead of the usual host then you have WINSOCK issues ...

Pinging oy with 32 bytes of data" (PC's built-in spkr beep once)
Discuss Pinging oy with 32 bytes of data" (PC's built-in spkr beep once) in the Networking forum on Dev Hardware.
Pinging oy with 32 bytes of data" (PC's built-in spkr beep once) Networking forum discussing setting up network printers, Wi-Fi, GigaNet, 802.11, Ethernet, T1 and T3 connections, routers and firewalls, NICs, IP addresses, DNS errors, and troubleshooting networking problems.

"Pinging oy with 32 bytes of data" (PC's built-in spkr beep once)
Please help.


Pinging oy with 32 bytes of data"(spkr beep once)

After un-installing CA EZ Armor Antivirus I loss my ethernet connectivity on my 3Com 3c905C-TXM. I cang ping out to the web 198.133.215.xx or 209.123.109.175 for example. My NOD32 did not find any spyware and viruses. It says no threat found.

So I remove all the protocols/service/client and uninstall the card, replaced it with Intel PCI PRO/100+ . Still got the same results.

I know I have a clean system. My ESET, uSoft Antispyware Beta and Spybot S&D were all up to date.

If possible, I do not want to go to "XP in place upgrade recovery" since my machine is warking very good except for the networking part.

The restore points are all gone.

Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

U:\>ping 209.123.109.175

Pinging oy with 32 bytes of data:

Reply from 209.123.109.175: bytes=32 time=66ms TTL=46
Reply from 209.123.109.175: bytes=32 time=66ms TTL=46
Reply from 209.123.109.175: bytes=32 time=66ms TTL=46
Reply from 209.123.109.175: bytes=32 time=66ms TTL=46

Ping statistics for 209.123.109.175:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 66ms, Maximum = 66ms, Average = 66ms

U:\>ping 209.123.109.175

Pinging oy with 32 bytes of data:

(## The "oy" is kind a weird since the "y" has a double dot above it.##)

TIA.
"

Solution :

Execute the following command:

CODE

netsh winsock reset

Then restart your computer. It worked for me.

Source : http://www.devhardware.com/forums/networking-34/pinging-oy-with-32-bytes-of-data-pc-s-built-in-47335.html