2

Hello.
I'm not the most computer literate, but I'll try to explain as best as I can.

I am using my laptop with Windows Vista Home Basic and a linksys router. My connection says it is connected, but when I open both browsers (Firefox and Internet Explorer 7) nothing happens except a message explaining it cannot connect to the server. Msn Messenger works perfectly fine, it seems to just be the internet from what I know. If there is anything else you need to know, let me know. Please help me, this is driving me insane. :'(
Thank you.

2
Contributors
4
Replies
5
Views
8 Years
Discussion Span
Last Post by Shay09
0

There is this problem with wireless connectivity on Vitsa laptops. There has been no hard and fast solutions for the same but 5 different methods worked for 5 different people ( though none for me :|) Just search for " Vista wireless connectivity problem " on Google and the answers should appear.

0

There is this problem with wireless connectivity on Vitsa laptops. There has been no hard and fast solutions for the same but 5 different methods worked for 5 different people ( though none for me :|) Just search for " Vista wireless connectivity problem " on Google and the answers should appear.

Alright, I give it a try. Thanks.

0

Okay, so I have done a few things. First, I visited the microsoft link someone provided and followed to the instructions on modifying something in the registry, that did not work. So I found another post similar to mine on another site and ran a few tests. Here is the original information for the ipconfig/all on cmd:


Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Shainas_Laptop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : launchmodem.com

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : launchmodem.com
Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN
Physical Address. . . . . . . . . : 00-14-A5-DE-91-66
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::e110:b546:b480:c0a2%9(Preferred)
IPv4 Address. . . . . . . . . . . : ***.***.*.***
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, August 14, 2009 1:02:23 AM
Lease Expires . . . . . . . . . . : Sunday, August 16, 2009 3:08:55 PM
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet
NIC
Physical Address. . . . . . . . . : 00-16-D4-A1-9C-6B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{7EB02A15-56DD-435C-87B6-87575E95D
C4A}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.launchmodem.com
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::105b:3b9e:b76f:11dd%10(Preferred)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

**Note:I've taken out the Ip Address because my father is paranoid about it, but if it is needed I will post it.**

The next thing I did was this:
TCP/IP stack repair options for use with Windows Vista.

Start, All Programs\Accessories and right click on Command Prompt, select "Run as Administrator" to open a command prompt.

In the command prompt window that opens, type type the following commands:

Reset WINSOCK entries to installation defaults: netsh winsock reset catalog

Reset IPv4 TCP/IP stack to installation defaults. netsh int ipv4 reset reset.log

Reset IPv6 TCP/IP stack to installation defaults. netsh int ipv6 reset reset.log

Reboot the machine.

I rebooted the computer and tried the internet, still nothing. I ran some tests with these instructions on the command prompt:
IPCONFIG /ALL

PING <computer_IP_address>

PING <default_gateway_address>

PING <dns_servers>

PING 206.190.60.37

PING yahoo.com


Here are my results:

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Shainas_Laptop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : launchmodem.com

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : launchmodem.com
Description . . . . . . . . . . . : Broadcom 802.11b/g WLAN
Physical Address. . . . . . . . . : 00-14-A5-DE-91-66
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::e110:b546:b480:c0a2%9(Preferred)
IPv4 Address. . . . . . . . . . . : ***.***.*.***(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Saturday, August 15, 2009 3:50:14 PM
Lease Expires . . . . . . . . . . : Sunday, August 16, 2009 3:50:13 PM
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet
NIC
Physical Address. . . . . . . . . : 00-16-D4-A1-9C-6B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{7EB02A15-56DD-435C-87B6-87575E95D
C4A}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : launchmodem.com
Description . . . . . . . . . . . : isatap.launchmodem.com
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::105b:3b9e:b76f:11dd%10(Preferred)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Windows\system32>ping ***.***.*.***

Pinging ***.***.*.*** with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.

Ping statistics for ***.***.*.***:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Windows\system32>ping 192.168.2.1

Pinging 192.168.2.1 with 32 bytes of data:
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

C:\Windows\system32>ping 192.168.1.254

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=3ms TTL=63
Reply from 192.168.1.254: bytes=32 time=4ms TTL=63
Reply from 192.168.1.254: bytes=32 time=2ms TTL=63
Reply from 192.168.1.254: bytes=32 time=2ms TTL=63

Ping statistics for 192.168.1.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 4ms, Average = 2ms

C:\Windows\system32>ping 206.190.60.37

Pinging 206.190.60.37 with 32 bytes of data:
Reply from 206.190.60.37: bytes=32 time=45ms TTL=50
Reply from 206.190.60.37: bytes=32 time=44ms TTL=50
Reply from 206.190.60.37: bytes=32 time=44ms TTL=50
Reply from 206.190.60.37: bytes=32 time=44ms TTL=50

Ping statistics for 206.190.60.37:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 45ms, Average = 44ms

C:\Windows\system32>ping yahoo.com

Pinging yahoo.com [209.131.36.159] with 32 bytes of data:
Reply from 209.131.36.159: bytes=32 time=91ms TTL=48
Reply from 209.131.36.159: bytes=32 time=89ms TTL=48
Reply from 209.131.36.159: bytes=32 time=90ms TTL=48
Reply from 209.131.36.159: bytes=32 time=90ms TTL=48

Ping statistics for 209.131.36.159:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 89ms, Maximum = 91ms, Average = 90ms

C:\Windows\system32>

Now what am I suppose to make of this information???!! I don't understand the numbers, but where the IP was pinged, I can see it failed. Why is that?

0

I figured it out. Apparently there was still components of Norton on my computer, I used the Norton Remove Tool from the Symantec website, restarted and voila. Thanks for the support guys.

This question has already been answered. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.