>Hi,
>  I'm fixing a friends computer and I've come across a very strange
>networking problem that I haven't experienced before. I've only managed to
>find on emention of it online, but there was no solution.
>
>Here is the problem, I would VERY much be appreciative if someone could
>supply a solution as I've tried just about everything. I'm surprised there is
>not a KnowledgeBase article on this.
>
>I'm trying to add the computer to a network. I've added many before and have
>always been able to resolve problems. But this one is plain strange. The
>computer will not network by TCP/IP. I've managed to get it working by
>installing IPX protocol, but this doesn't help when it comes to sharing the
>internet connection. After trying several things, I noticed somehting very
>strange with the PING from command prompt. Strange characters and symbols are
>coming up when I ping anything, such as:-
>
>ping 192.168.1.1
>
>Pinging (Spade symbol) with 32 bytes of data:
>
>Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
>Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
>Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
>Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
>
>Ping statistics for 0ù?:
>Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>Approximate round trip times in milli-seconds:
>Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
>The computer only had service pack one. So I created a CD to upgrade it to
>SP2 which went on fine. When i tried ping again there were different weird
>characters and as soon as i hit return the PC speaker beeps. NOTE PC speaker,
>not the sound card:-
>
>Pinging °ÿ with 32 bytes of data:
>
>Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
>Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
>Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
>Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
>
>Ping statistics for            :
>Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>Approximate round trip times in milli-seconds:
>Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
>I've tried resetting tcpip following the knowledge base article. But that
>made no difference. I even tried copying over ping.exe and the tcpip system
>files from system32 on a working macine to this one, but that made no
>difference as well. I'm totally stumped. I don't want to do a clean install
>as I've spend so much time on this, and the manufacturor did not provide an
>xp cd. I'm a computer programmer, so don't be afraid to post any advanced
>techniques.
>
>The post I found on this from another forum is at:-
>http://www.techiegroups.com/showthread.php?t=15609
>
>Please help.

"Chuck" wrote:

> On Mon, 9 Oct 2006 15:23:01 -0700, CosmicPerl
> <CosmicP***@discussions.microsoft.com> wrote:
>
> >Hi,
> >  I'm fixing a friends computer and I've come across a very strange
> >networking problem that I haven't experienced before. I've only managed to
> >find on emention of it online, but there was no solution.
> >
> >Here is the problem, I would VERY much be appreciative if someone could
> >supply a solution as I've tried just about everything. I'm surprised there is
> >not a KnowledgeBase article on this.
> >
> >I'm trying to add the computer to a network. I've added many before and have
> >always been able to resolve problems. But this one is plain strange. The
> >computer will not network by TCP/IP. I've managed to get it working by
> >installing IPX protocol, but this doesn't help when it comes to sharing the
> >internet connection. After trying several things, I noticed somehting very
> >strange with the PING from command prompt. Strange characters and symbols are
> >coming up when I ping anything, such as:-
> >
> >ping 192.168.1.1
> >
> >Pinging (Spade symbol) with 32 bytes of data:
> >
> >Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
> >Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
> >Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
> >Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
> >
> >Ping statistics for 0ù?:
> >Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> >Approximate round trip times in milli-seconds:
> >Minimum = 0ms, Maximum = 0ms, Average = 0ms
> >
> >The computer only had service pack one. So I created a CD to upgrade it to
> >SP2 which went on fine. When i tried ping again there were different weird
> >characters and as soon as i hit return the PC speaker beeps. NOTE PC speaker,
> >not the sound card:-
> >
> >Pinging °ÿ with 32 bytes of data:
> >
> >Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
> >Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
> >Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
> >Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
> >
> >Ping statistics for            :
> >Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> >Approximate round trip times in milli-seconds:
> >Minimum = 0ms, Maximum = 0ms, Average = 0ms
> >
> >I've tried resetting tcpip following the knowledge base article. But that
> >made no difference. I even tried copying over ping.exe and the tcpip system
> >files from system32 on a working macine to this one, but that made no
> >difference as well. I'm totally stumped. I don't want to do a clean install
> >as I've spend so much time on this, and the manufacturor did not provide an
> >xp cd. I'm a computer programmer, so don't be afraid to post any advanced
> >techniques.
> >
> >The post I found on this from another forum is at:-
> >http://www.techiegroups.com/showthread.php?t=15609
> >
> >Please help.
>
> This is an example of LSP / Winsock corruption.
> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
> http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
>
> Get rid of IPX/SPX first please.  You'll have more possible problems, if you
> don't.
> <http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
> http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html
>
> --
> Cheers,
> Chuck, MS-MVP [Windows - Networking]
> http://nitecruzr.blogspot.com/
> Paranoia is not a problem, when it's a normal response from experience.
> My        email         is          AT         DOT
>    actual       address    pchuck       mvps        org.
>

>Thanks man. U RULE!!!!!
>
>That sorted it. I guessed in was something between windows and the tcp
>drivers I updated. Very much appreciated.
>
>Lyle
>
>
>"Chuck" wrote:
>
>> On Mon, 9 Oct 2006 15:23:01 -0700, CosmicPerl
>> <CosmicP***@discussions.microsoft.com> wrote:
>>
>> >Hi,
>> >  I'm fixing a friends computer and I've come across a very strange
>> >networking problem that I haven't experienced before. I've only managed to
>> >find on emention of it online, but there was no solution.
>> >
>> >Here is the problem, I would VERY much be appreciative if someone could
>> >supply a solution as I've tried just about everything. I'm surprised there is
>> >not a KnowledgeBase article on this.
>> >
>> >I'm trying to add the computer to a network. I've added many before and have
>> >always been able to resolve problems. But this one is plain strange. The
>> >computer will not network by TCP/IP. I've managed to get it working by
>> >installing IPX protocol, but this doesn't help when it comes to sharing the
>> >internet connection. After trying several things, I noticed somehting very
>> >strange with the PING from command prompt. Strange characters and symbols are
>> >coming up when I ping anything, such as:-
>> >
>> >ping 192.168.1.1
>> >
>> >Pinging (Spade symbol) with 32 bytes of data:
>> >
>> >Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
>> >Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
>> >Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
>> >Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
>> >
>> >Ping statistics for 0ù?:
>> >Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>> >Approximate round trip times in milli-seconds:
>> >Minimum = 0ms, Maximum = 0ms, Average = 0ms
>> >
>> >The computer only had service pack one. So I created a CD to upgrade it to
>> >SP2 which went on fine. When i tried ping again there were different weird
>> >characters and as soon as i hit return the PC speaker beeps. NOTE PC speaker,
>> >not the sound card:-
>> >
>> >Pinging °ÿ with 32 bytes of data:
>> >
>> >Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
>> >Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
>> >Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
>> >Reply from 192.168.1.1: bytes=32 time<1ms TTL=150
>> >
>> >Ping statistics for            :
>> >Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>> >Approximate round trip times in milli-seconds:
>> >Minimum = 0ms, Maximum = 0ms, Average = 0ms
>> >
>> >I've tried resetting tcpip following the knowledge base article. But that
>> >made no difference. I even tried copying over ping.exe and the tcpip system
>> >files from system32 on a working macine to this one, but that made no
>> >difference as well. I'm totally stumped. I don't want to do a clean install
>> >as I've spend so much time on this, and the manufacturor did not provide an
>> >xp cd. I'm a computer programmer, so don't be afraid to post any advanced
>> >techniques.
>> >
>> >The post I found on this from another forum is at:-
>> >http://www.techiegroups.com/showthread.php?t=15609
>> >
>> >Please help.
>>
>> This is an example of LSP / Winsock corruption.
>> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
>> http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
>>
>> Get rid of IPX/SPX first please.  You'll have more possible problems, if you
>> don't.
>> <http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
>> http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html
>>
>> --
>> Cheers,
>> Chuck, MS-MVP [Windows - Networking]
>> http://nitecruzr.blogspot.com/
>> Paranoia is not a problem, when it's a normal response from experience.
>> My        email         is          AT         DOT
>>    actual       address    pchuck       mvps        org.
>>