Re: Re: XP Not Detecting Connection
anonymous_at_discussions.microsoft.com
Date: 06/30/04
- Next message: Frank P: "RE: Auto IP Detect Not Working"
- Previous message: Tegger®: "Re: Auto IP Detect Not Working"
- In reply to: Tegger®: "Re: Re: XP Not Detecting Connection"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 29 Jun 2004 19:58:23 -0700
Yes. It's the same computer, network card, ISP
everything. The only thing that's changed since the last
time it was plugged in was I removed several adware
programs and files, along with virus files and other
suspicious files, and then a massive windows update.
Like I said, I may have gotten a little 'delete-happy'
but I'm really not sure. I've now tried restoring the
system using sysem restore to various points throughout
the process, but to no avail.
There is no 'cable unplugged' message in the task bar,
and the Network Connection displays 'Enabled.'
When I tried to ping 127.0.0.1, I received a reply along
the lines of 'bytes = 32 time.... etc' 4 times But when
I tried to ping the 160.33.26.10, it produced 'Unable to
ping requested address' or something like that 4 times.
And when trying to ping sony.com, it simply said
something like 'I dont recognize that' only once.
Thanks for your help thus far.
>-----Original Message-----
>"Brad Grubb" <uvabrad@hotmail.com> spake unto the masses
in
>news:234d001c45e3c$48dae410$a501280a@phx.gbl:
>
>> No. No new network cards or routers were installed,
it's
>> simply a direct connection to the cable modem.
>
>
>
>So it's the same computer, same network card, same ISP?
>
>Do you get a "cable unplugged" icon in your task bar?
>
>When you go to My Network Places, what does it say for
the network
>connection that plugs into the cable modem?
>
>
>
>>
>> Also, the problem still persists after trying the
first
>> reply's suggestion and also completely removing and
>> reinstalling the winsock and winsock2's manually.
>
>
>
>Go Start>Run and type:
>cmd <enter>
>
>try pinging 127.0.0.1 and then 160.33.26.10 like this:
>ping 127.0.0.1 <enter>
>
>What happens? Any response or does it just say "timed
out" both times? If
>you get no reply to either then your TCP stack may need
to be reinstalled.
>
>If you get a reply to the second IP address that's
something like this:
>Reply from 160.33.26.10: bytes=32 time=101ms TTL=236
>
>then try:
>ping sony.com <enter>
>
>Any response then?
>
>
>--
>TeGGeR®
>
>
>How to find anything on the Internet or in Usenet Groups:
>www.google.com
>www.groups.google.com
>.
>
- Next message: Frank P: "RE: Auto IP Detect Not Working"
- Previous message: Tegger®: "Re: Auto IP Detect Not Working"
- In reply to: Tegger®: "Re: Re: XP Not Detecting Connection"
- Messages sorted by: [ date ] [ thread ]