Odd tcp/ip problem - XP

[Patrick Keenan]

Hello,
I'm having an odd network problem on one XP machine, and I'm wondering if
anyone has any ideas about it. It's an XP Home machine, with three user
accounts (four including the Admin). There is a firewall installed, which
I have disabled for test purposes.

Account #1 works fine, can get to the router and web, and ping and tracert
work properly.

Accounts #2 and #3 and Admin don't work properly. Account #3 I created
today for testing. There's no web access and neither ping or tracert
really work properly.
==
Ping sort of works - it finds the router at 192.168.0.1 but instead of
returning this:

Pinging 192.168.0.1 with 32 bytes of data:

it comes back with this:

Pinging <garbage characters> with 32 bytes of data:

The garbage characters are actually a superscript o and a y with umlaut.
==
Tracert produces the same garbage characters and doesn't complete, producing
something like this:

Tracing route to 192.168.0.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms no resources

and doesn't say "trace complete" as tracert does on account #1.
==
I'm pretty sure that the garbage characters are giving me a clue, but I
don't know what it is.
Anyone have any idea what's going on here?

Thanks,
Patrick Keenan

 

[Patrick Keenan]

Hello,
I'm having an odd network problem on one XP machine, and I'm wondering if
anyone has any ideas about it. It's an XP Home machine, with three user
accounts (four including the Admin). There is a firewall installed,
which I have disabled for test purposes.

Account #1 works fine, can get to the router and web, and ping and tracert
work properly.

Accounts #2 and #3 and Admin don't work properly. Account #3 I created
today for testing. There's no web access and neither ping or tracert
really work properly.
==
Ping sort of works - it finds the router at 192.168.0.1 but instead of
returning this:

Pinging 192.168.0.1 with 32 bytes of data:

it comes back with this:

Pinging <garbage characters> with 32 bytes of data:

The garbage characters are actually a superscript o and a y with umlaut.
==
Tracert produces the same garbage characters and doesn't complete,
producing something like this:

Tracing route to 192.168.0.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms no resources

and doesn't say "trace complete" as tracert does on account #1.
==
I'm pretty sure that the garbage characters are giving me a clue, but I
don't know what it is.
Anyone have any idea what's going on here?

Thanks,
Patrick Keenan

Also - releasing and renewing IP addresses works fine in all accounts and
the "repair" function also seems to work. Resetting tcp/ip via netsh
doesn't have any effect - only account #1 gets internet access.

-pk

 

[Patrick Keenan]

Also - releasing and renewing IP addresses works fine in all accounts and
the "repair" function also seems to work. Resetting tcp/ip via netsh
doesn't have any effect - only account #1 gets internet access.

-pk

And thanks to the miracle of Usenet, this is fixed. Another thread in this
group described the exact same problem, and the fix:
netsh winsock reset catalog
and a reboot.

thanks!
-pk