ping command prompt returns strange symbols

[andy2004]

for some reason when i ping other machines on the network im getting this in the command prompt ?? is there any way to fix it via the registry ? i dont wanna reinstall just because of this :crazy: anyone know what to do ?

[OPaul]

Does it also do that for computers outside your network?

[dreamthief]

I think instead of using IP addresses, it took the computer name instead. For those computer with non english, XP version might return weird characters due to different charset.

[John Veteran]

I think your TCP/IP stack is corrupt :/ I had the same problem a while ago, but I forget how I fixed it :pinch:

[skrekkur]

I have the excacly same problem, happened after sp2 had been in for a while, but I've also had this problem before, but don?t know how I fixed it, perhaps just reinstall of windows, also the dns doesn?t seem to work on this particular computer, and im not sure about the gateway, but its practicly unusable that way, gonna try to reinstall, given up trying to find the problem no:/:/

btw I get Excacly the same symbols when pinging localhost 4 times

update: I can ping ip's outside my network, and it returns excacly the same symbols, but the dns system just doesn?t seem to work on the computer in question(and yes other that use the router work fine)

hope someone finds a solution of this other than reinstall

Edited September 1, 2004 by skrekkur

[skrekkur]

I have a feeling (although can?t test this right now) that this might be a bug in windows firewall, do you have it on? because I might have

[PiMPiN]

Trust me on this one, the TCP/IP stack is corrupted. The only thing that works to fix this besides a complete reinstall is a system restore. I used to see this all the time in MSN Dial support, and even had it myself on a few occasions. The system restore always worked for me, but I remember a few customers who needed a reinstall of the OS.

[skrekkur]

I have found and fixed the problem!

first I tried reinstall and go back too sp2, but it came up again, reinstalled again and installed sp1, it came up again. I downloaded Spybot : search and destroy version 1.3 (note: Adaware DOESN'T WORK)

I ran it and removed an entry called webhancer, which seems to alter winsock and that results in this dreadful problem that has literally kept me awake for 2 days.

http://www.spyany.com/program/article_spy_rm_webHancer.html here is a stand-alone remover and more info about this dreadful thing, but I won?t guarantee that it does any good, because spybot took care of this for me, and now im running sp2 and holding my old settings and am a very happy panda and proud to have found out what this is.

:DD

hope this will help you guys in the future and Pimpin, now just tell people to install the newest version of spybot to fix this, I might add that so far Spybot has been 'Safer' than Adaware in the sense that I have yet to encounter something that will damage my settings in it, but Adaware has proposed some bad things, so one has to be really awake when using that.

[PiMPiN]

it's great that you fixed it, but when you say "reinstalled", what exactly was reinstalled, the entire OS or a specific program? Spybot is great, but in the cases I've seen with this, it had nothing to do with spyware, just XP deciding to act up because a (legit) program wants to use the network stack and XP is greedy and won't give it up. When I had the problem myself is was on a single, non-networked machine with no internet that was just set-up, I was installing a firewall (McAfee I believe) and that has it's own protocol and XP didn't like it. Needless to say I ended up with a corrupt stack and needed to restore to fix it :/