Can't connect to the internet

[ouimetteracing]

I am using a wireless connection and cant connect to the internet. I tried
repairing my connection and everything went fine but I still can't connect.
When I check the activity of the connection it is sending at least 341
packets but my computer is only recieving 6. I have full signal strength.
Does anyone have any possible solutions to this problem
thanks

 

[susantha silva]

Hi your information is insufficient to provide any solution. Can you let us
know what is the wireless router you're having and also about your
operating system so we may able to support you more.

Regards,
Susantha

 

[ouimetteracing via WindowsKB.com]

I have a Sony Vaio laptop K-23 series with a D-Link Wireless 108 G Router and
Windows XP Home edition. I also have a Compaq Presario laptop that will
connect to the internet just fine. The Sony used to work fine but after I
tried to delete a virus t didnt work anymore
Thanks

 

[Chuck]

I have a Sony Vaio laptop K-23 series with a D-Link Wireless 108 G Router and
Windows XP Home edition. I also have a Compaq Presario laptop that will
connect to the internet just fine. The Sony used to work fine but after I
tried to delete a virus t didnt work anymore
Thanks

Any time a problem like yours starts after you remove malware, chances are you
have 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

 

[ouimetteracing via WindowsKB.com]

Thanks for your info but unfortunatly it still didn't work. I tried it but I
still get the same response. I am still looking for more info but thanks
anyways

 

[ouimetteracing via WindowsKB.com]

Thanks for your info but unfortunatly it still didn't work. I tried it but I
still get the same response. I am still looking for more info but thanks
anyways

Oh yah Chuck when I tried the 5th step you had me click have disk then type \
windows\inf" in the box, and click OK my computer said the specified location
does not contain information about your hardware so if you can find another
file or somthing then I will try that again.

 

[Chuck]

Oh yah Chuck when I tried the 5th step you had me click have disk then type \
windows\inf" in the box, and click OK my computer said the specified location
does not contain information about your hardware so if you can find another
file or somthing then I will try that again.

OK, that was the best possibility, but there are others too.

Let's try and diagnose the problem. From both computers:
# From a command window:
1. Ping www.yahoo.com.
2. Ping 66.94.230.33.
3. Report success / exact text of error messages.
# From your browser:
1. Browse www.yahoo.com.
2. Browse 66.94.230.33.
3. Report success / exact text of error messages.

This will help us see, objectively, what to check next.

 

[ouimetteracing via WindowsKB.com]

[quoted text clipped - 3 lines]

does not contain information about your hardware so if you can find another
file or somthing then I will try that again.

OK, that was the best possibility, but there are others too.

Let's try and diagnose the problem. From both computers:
# From a command window:
1. Ping www.yahoo.com.
2. Ping 66.94.230.33.
3. Report success / exact text of error messages.
# From your browser:
1. Browse www.yahoo.com.
2. Browse 66.94.230.33.
3. Report success / exact text of error messages.

This will help us see, objectively, what to check next.

OK when I ping www.yahoo.com in the command prompt it says ping request could
not find host www.yahoo.com Please check the name an try again. When I ping
66.94.230.33 it says:
Pinging 66.94.230.33 with 32 bytes of data:

Reply from 66.94.230.33: bytes=32 time=108ms TTL=51
Reply from 66.94.230.33: bytes=32 time=90ms TTL=51
Reply from 66.94.230.33: bytes=32 time=84ms TTL=51
Reply from 66.94.230.33: bytes=32 time=85ms TTL=51

Ping statistics fro 66.94.230.33:
Packets: Sent = 4, Received = 4, Lost = 0 <0% loss>,
Approximate round trip times in milli-seconds:
Minimum = 84ms, Maximum = 108ms, Average = 91ms

When I Browse www.yahoo.com it comes up with the normal The Page cannot be
displayed.
When I Browse 66.94.230.33 it comes up with the same thing.

 

[Chuck]

Thanks for your info but unfortunatly it still didn't work. I tried it but I
still get the same response. I am still looking for more info but thanks

[quoted text clipped - 3 lines]

does not contain information about your hardware so if you can find another
file or somthing then I will try that again.

OK, that was the best possibility, but there are others too.

Let's try and diagnose the problem. From both computers:
# From a command window:
1. Ping www.yahoo.com.
2. Ping 66.94.230.33.
3. Report success / exact text of error messages.
# From your browser:
1. Browse www.yahoo.com.
2. Browse 66.94.230.33.
3. Report success / exact text of error messages.

This will help us see, objectively, what to check next.

OK when I ping www.yahoo.com in the command prompt it says ping request could
not find host www.yahoo.com Please check the name an try again. When I ping
66.94.230.33 it says:
Pinging 66.94.230.33 with 32 bytes of data:

Reply from 66.94.230.33: bytes=32 time=108ms TTL=51
Reply from 66.94.230.33: bytes=32 time=90ms TTL=51
Reply from 66.94.230.33: bytes=32 time=84ms TTL=51
Reply from 66.94.230.33: bytes=32 time=85ms TTL=51

Ping statistics fro 66.94.230.33:
Packets: Sent = 4, Received = 4, Lost = 0 <0% loss>,
Approximate round trip times in milli-seconds:
Minimum = 84ms, Maximum = 108ms, Average = 91ms

When I Browse www.yahoo.com it comes up with the normal The Page cannot be
displayed.
When I Browse 66.94.230.33 it comes up with the same thing.

And THAT sounds like a DNS issue. Let's take a look at "ipconfig /all".
<http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html>
http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html

 

[Chuck]

Thanks for your info but unfortunatly it still didn't work. I tried it but I
still get the same response. I am still looking for more info but thanks

[quoted text clipped - 3 lines]

does not contain information about your hardware so if you can find another
file or somthing then I will try that again.

OK, that was the best possibility, but there are others too.

Let's try and diagnose the problem. From both computers:
# From a command window:
1. Ping www.yahoo.com.
2. Ping 66.94.230.33.
3. Report success / exact text of error messages.
# From your browser:
1. Browse www.yahoo.com.
2. Browse 66.94.230.33.
3. Report success / exact text of error messages.

This will help us see, objectively, what to check next.

OK when I ping www.yahoo.com in the command prompt it says ping request could
not find host www.yahoo.com Please check the name an try again. When I ping
66.94.230.33 it says:
Pinging 66.94.230.33 with 32 bytes of data:

Reply from 66.94.230.33: bytes=32 time=108ms TTL=51
Reply from 66.94.230.33: bytes=32 time=90ms TTL=51
Reply from 66.94.230.33: bytes=32 time=84ms TTL=51
Reply from 66.94.230.33: bytes=32 time=85ms TTL=51

Ping statistics fro 66.94.230.33:
Packets: Sent = 4, Received = 4, Lost = 0 <0% loss>,
Approximate round trip times in milli-seconds:
Minimum = 84ms, Maximum = 108ms, Average = 91ms

When I Browse www.yahoo.com it comes up with the normal The Page cannot be
displayed.
When I Browse 66.94.230.33 it comes up with the same thing.

And THAT sounds like a DNS issue. Let's take a look at "ipconfig /all", from
both computers.
<http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html>
http://nitecruzr.blogspot.com/2005/05/reading-ipconfig-and-diagnosing.html

 

[ouimetteracing via WindowsKB.com]

This is what came up:
Windows IP Configuration Host Name . . . . . . . . . . . . :
Brianscomputer Primary Dns Suffix . . . . . . . : Brianscomp
Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . .
.. . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix
Search List. . . . . . : BrianscompEthernet adapter Wireless Network
Connection: Connection-specific DNS Suffix . : Description . .
.. . . . . . . . . : LAN-Express AS IEEE 802.11g miniPCI Adapter
Physical Address. . . . . . . . . : 00-0E-9B-24-6E-B2 Dhcp Enabled. . .
.. . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.102 Subnet Mask . . . . .
.. . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.
168.0.1 DHCP Server . . . . . . . . . . . : 192.168.0.1 DNS
Servers . . . . . . . . . . . : 192.168.0.1 Lease Obtained. . . . . . .
.. . . : Saturday, December 17, 2005 11:47:48 AM Lease Expires . . . . .
.. . . . . : Saturday, December 24, 2005 11:47:48 AMEthernet adapter Local
Area Connection: Media State . . . . . . . . . . . : Media
disconnected Description . . . . . . . . . . . : Realtek RTL8139/810x
Family Fast Ethernet NIC Physical Address. . . . . . . . . : 08-00-46-
E8-68-6B

What does this tell you?

 

[Chuck]

This is what came up:
Windows IP Configuration Host Name . . . . . . . . . . . . :
Brianscomputer Primary Dns Suffix . . . . . . . : Brianscomp
Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . .
. . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix
Search List. . . . . . : BrianscompEthernet adapter Wireless Network
Connection: Connection-specific DNS Suffix . : Description . .
. . . . . . . . . : LAN-Express AS IEEE 802.11g miniPCI Adapter
Physical Address. . . . . . . . . : 00-0E-9B-24-6E-B2 Dhcp Enabled. . .
. . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.102 Subnet Mask . . . . .
. . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.
168.0.1 DHCP Server . . . . . . . . . . . : 192.168.0.1 DNS
Servers . . . . . . . . . . . : 192.168.0.1 Lease Obtained. . . . . . .
. . . : Saturday, December 17, 2005 11:47:48 AM Lease Expires . . . . .
. . . . . : Saturday, December 24, 2005 11:47:48 AMEthernet adapter Local
Area Connection: Media State . . . . . . . . . . . : Media
disconnected Description . . . . . . . . . . . : Realtek RTL8139/810x
Family Fast Ethernet NIC Physical Address. . . . . . . . . : 08-00-46-
E8-68-6B

What does this tell you?

Not a lot. It would be more useful if I could compare it to the same, from the
other computer. And please label each as "Presario" or Vaio", so I know which
I'm looking at.
<http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html>
http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html

 

[ouimetteracing via WindowsKB.com]

VAIO

Windows IP Configuration
Host Name . . . . . . . . . . . . : Brianscomputer Primary Dns
Suffix . . . . . . . : Brianscomp Node Type . . . . . . . . . . . . :
Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy
Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . :
BrianscompEthernet adapter Wireless Network Connection: Connection-
specific DNS Suffix . : Description . . . . . . . . . . . : LAN-
Express AS IEEE 802.11g miniPCI Adapter Physical Address. . . . . . . .
.. : 00-0E-9B-24-6E-B2 Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . .
.. : 192.168.0.102 Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1 DHCP Server . . . . . .
.. . . . . : 192.168.0.1 DNS Servers . . . . . . . . . . . : 192.168.0.
1 Lease Obtained. . . . . . . . . . : Saturday, December 17, 2005 11:
47:48 AM Lease Expires . . . . . . . . . . : Saturday, December 24,
2005 11:47:48 AMEthernet adapter Local Area Connection: Media State . .
.. . . . . . . . . : Media disconnected Description . . . . . . . . . .
.. : Realtek RTL8139/810x Family Fast Ethernet NIC Physical Address. . .
.. . . . . . : 08-00-46-E8-68-6B

Presario

Windows IP Configuration



Host Name . . . . . . . . . . . . : PC226661211056

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Local Area Connection:



Media State . . . . . . . . . . . : Media disconnected

Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
Ethernet NIC

Physical Address. . . . . . . . . : 00-C0-9F-C6-68-8C



Ethernet adapter Wireless Network Connection 2:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN

Physical Address. . . . . . . . . : 00-14-A5-18-EC-67

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.101

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1

Lease Obtained. . . . . . . . . . : Saturday, December 17, 2005 2:47:
17 PM

Lease Expires . . . . . . . . . . : Saturday, December 24, 2005 2:47:
17 PM

Sorry about that

 

[Chuck]

Sorry about that

NP, seen worse.

Both computers are getting the same name resolution settings - and both use the
router as a DNS relay. Your DNS settings ("Primary Dns Suffix . . . . . . . :
Brianscomp" and "DNS Suffix Search List. . . . . . : Brianscomp") are a bit
gratuituous - they're generally used on a LAN with an actual DNS server, not a
NAT router providing a DNS relay, but I don't see them causing your problem.

Brianscomputer is Node Type . . . . . . . . . . . . : Hybrid, and PC226661211056
is Node Type . . . . . . . . . . . . : Unknown. Node types Hybrid and Unknown
are a bit inefficient, but this only affects the local subnet; name resolution
on the Internet only uses DNS.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

So what's the problem here? My guess is the MTU, but that doesn't explain why a
ping by IP address was successful, even though ping by name, and browse by both
name and ip address were unsuccessful. Repeat the 4 tests a couple times,
please, over a few hours, and see if they vary in result. The neat (NOT) thing
about the MTU issue is that results can vary over just seconds, as packet
switching effects change by millisecond.
<http://nitecruzr.blogspot.com/2005/06/internet-connectivity-problems-caused.html>
http://nitecruzr.blogspot.com/2005/06/internet-connectivity-problems-caused.html

My opinion is that you still have an LSP / Winsock / TCP/IP corruption problem
here. Which of the 6 (now for your convenience, in a numbered list!) fixes did
you try? Please be specific.
<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

A misconfigured personal firewall, that doesn't trust the NAT router, could have
a similar effect, but it should NOT affect browse by IP address.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html

 

[ouimetteracing via WindowsKB.com]

I tried repairing the LSP Winsock Layer again these are what happened.
1. I tried the LSP-Fix and nothing came up

2. I tried the WinsockFix.zip and restarted it and it still did the same
thing

3. Winsock 2 Fix does not apply to Windows XP systems

4. Winsock XP Fix I tried and restarted the comp and it is still doing the
exact same thing

5. A. When i used this it still did the same thing
B. It Successfully reset it but it still did the exact same thing

6. and to reset my tcp/ip what exactly should I type to do what I want to do.

 

[ouimetteracing via WindowsKB.com]

interesting note I tried pinging my own computers ip address and the request
timed out 4 times and the 5th time it said it sent 4 packets and received 0,
While I pinged my other comp and it worked just fine sending 4 and receiving
4.

 

[ouimetteracing via WindowsKB.com]

Still as i ping www.yahoo.com and try to type them in, in the explorer they
still do the same thing.

 

[Chuck]

Still as i ping www.yahoo.com and try to type them in, in the explorer they
still do the same thing.

And still as you ping 66.94.230.33 does it say:
Pinging 66.94.230.33 with 32 bytes of data:

Reply from 66.94.230.33: bytes=32 time=108ms TTL=51
Reply from 66.94.230.33: bytes=32 time=90ms TTL=51
Reply from 66.94.230.33: bytes=32 time=84ms TTL=51
Reply from 66.94.230.33: bytes=32 time=85ms TTL=51

Please be specific here. I'm trying to figure if the one test, out of four, is
consistently successful. Then I gotta figure out why browsing 66.94.230.33
would be unsuccessful, even when pinging would be successful. Knowing if the 4
tests return consistent results is a big help.

 

[ouimetteracing via WindowsKB.com]

Yes it is all the same thing. The ms is a little bit different but all around
the same number. It doesnt work to explore any of them and it still does not
ping www.yahoo.com or explore it.
Thanks again for the help

 

[Chuck]

Yes it is all the same thing. The ms is a little bit different but all around
the same number. It doesnt work to explore any of them and it still does not
ping www.yahoo.com or explore it.
Thanks again for the help

We're dealing with the unknown here, but at least consistent unknown (so you
say). The fact that you can ping by IP address, but not browse that way, is
interesting. Likewise the fact that you can ping by IP address, but not by
name.

If you had just browser symptoms, I'd suspect an MTU problem.
<http://nitecruzr.blogspot.com/2005/06/internet-connectivity-problems-caused.html>
http://nitecruzr.blogspot.com/2005/06/internet-connectivity-problems-caused.html

If you just had name resolution issues (ie inability to browse or ping by name
only), I'd suspect a DNS issue.

The combination makes me think LSP / Winsock, which can have many different
symptoms. But you've tried the known resolutions for that. Maybe you have a
problem (or software) that is in LSP / Winsock, but doesn't respond to any of
the 6 solutions. Let's look at your LSP / Winsock component layer. Maybe we
can spot a clue.
<http://nitecruzr.blogspot.com/2005/12/lsp-winsock-analysis-using-log-from.html>
http://nitecruzr.blogspot.com/2005/12/lsp-winsock-analysis-using-log-from.html