Vista Internet not working, Ping by DNS is working

My college aged daughter's laptop formerly worked fine but now has odd
networking issues which prevent the system from browsing the internet. The
system correctly obtains a DHCP address and is able to ping by name, websites
on the web (www.yahoo.com, www.cnet.com), can correctly run AIM and Microsoft
Sidebar but still can not connect the IE7.0 Browser to the internet.

I have read a ton of links here within the Network and Sharing group but I
haven't seen anything quite like this before. Even though the I know better,
I still went through the exercise of testing for DNS issues as well as the
often suggested MTU test but there weren't any issues. I have completely
shut off the Microsoft Firewall to no avail. The system came with a free
trial of Norton Internet Security but after it expired, I loaded a
Symantec/Norton Antivirus (NAV 10.1) and did a complete virus scan which
produced nothing. I also did a full spyware scan which also didn't locate any
serious malware.

Below are the system specifics, I would GREATLY appreciate your suggestions.

New Laptop: HP Pavilion dv6500 Notebook (Just bought in Aug)
Windows Vista Home Premium
Both a LAN (wired) and Wireless Port are connected to a "newer" Linksys
SRX200 Wireless Router


c:\Windows>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Audra-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : socal.rr.com

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : socal.rr.com
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network
Connection

Physical Address. . . . . . . . . : 00-1B-77-CE-45-XX
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::3cc2:114b:794b:c371%9(Preferred)

IPv4 Address. . . . . . . . . . . : 192.168.1.106(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, January 03, 2008 10:46:41 AM
Lease Expires . . . . . . . . . . : Friday, January 04, 2008 10:46:40 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 268442487
DNS Servers . . . . . . . . . . . : 66.75.164.90
66.75.164.89
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : socal.rr.com
Description . . . . . . . . . . . : Realtek RTL8101 Family PCI-E Fast
Ethernet NIC (NDIS 6.0)

Physical Address. . . . . . . . . : 00-1B-24-94-55-XX
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2905:7336:41e0:f454%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.107(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, January 03, 2008 10:46:29 AM
Lease Expires . . . . . . . . . . : Friday, January 04, 2008 10:46:28 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 201333540
DNS Servers . . . . . . . . . . . : 66.75.164.90
66.75.164.89
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 9:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 10:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 6TO4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:
Connection-specific DNS Suffix . : socal.rr.com
Description . . . . . . . . . . . : isatap.socal.rr.com
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.106%12(Preferred)
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.107%12(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 66.75.164.90
66.75.164.89
NetBIOS over Tcpip. . . . . . . . : Disabled

c:\Windows>ping 127.1.0.0
Pinging 127.1.0.0 with 32 bytes of data:

Reply from 127.1.0.0: bytes=32 time<1ms TTL=128
Reply from 127.1.0.0: bytes=32 time<1ms TTL=128
Reply from 127.1.0.0: bytes=32 time<1ms TTL=128
Reply from 127.1.0.0: bytes=32 time<1ms TTL=128

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

c:\Windows>ping 192.168.1.102
Pinging 192.168.1.102 with 32 bytes of data:

Reply from 192.168.1.102: bytes=32 time=88ms TTL=64
Reply from 192.168.1.102: bytes=32 time=1ms TTL=64
Reply from 192.168.1.102: bytes=32 time=1ms TTL=64
Reply from 192.168.1.102: bytes=32 time=1ms TTL=64

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

c:\Windows>ping www.yahoo.com

Pinging www.yahoo-ht3.akadns.net [209.131.36.158] with 32 bytes of data:

Reply from 209.131.36.158: bytes=32 time=31ms TTL=53
Reply from 209.131.36.158: bytes=32 time=28ms TTL=54
Reply from 209.131.36.158: bytes=32 time=42ms TTL=54
Reply from 209.131.36.158: bytes=32 time=40ms TTL=54

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

c:\Windows>ping www.cnet.com
Pinging c18-ssa-xw-lb.cnet.com [216.239.122.220] with 32 bytes of data:

Reply from 216.239.122.220: bytes=32 time=58ms TTL=242
Reply from 216.239.122.220: bytes=32 time=59ms TTL=242
Reply from 216.239.122.220: bytes=32 time=50ms TTL=242
Reply from 216.239.122.220: bytes=32 time=55ms TTL=242

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

--
Craig
PC Slave

Check if the port 80 is blocked by your firewall. Create an exception
otherwise.
I suggest to try other browsers also. IE is ok but you should check for
updates ...

"Craig" <Craig@discussions.microsoft.com> wrote in message
news:5D234890-7C0B-4A43-B4B7-07894B1E2842@microsoft.com...

>
> My college aged daughter's laptop formerly worked fine but now has odd
> networking issues which prevent the system from browsing the internet.
> The
> system correctly obtains a DHCP address and is able to ping by name,
> websites
> on the web (www.yahoo.com, www.cnet.com), can correctly run AIM and
> Microsoft
> Sidebar but still can not connect the IE7.0 Browser to the internet.
>
> I have read a ton of links here within the Network and Sharing group but I
> haven't seen anything quite like this before. Even though the I know
> better,
> I still went through the exercise of testing for DNS issues as well as the
> often suggested MTU test but there weren't any issues. I have completely
> shut off the Microsoft Firewall to no avail. The system came with a free
> trial of Norton Internet Security but after it expired, I loaded a
> Symantec/Norton Antivirus (NAV 10.1) and did a complete virus scan which
> produced nothing. I also did a full spyware scan which also didn't locate
> any
> serious malware.
>
> Below are the system specifics, I would GREATLY appreciate your
> suggestions.
>
> New Laptop: HP Pavilion dv6500 Notebook (Just bought in Aug)
> Windows Vista Home Premium
> Both a LAN (wired) and Wireless Port are connected to a "newer" Linksys
> SRX200 Wireless Router
>
>
> c:\Windows>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : Audra-PC
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Hybrid
>
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : socal.rr.com
>
> Wireless LAN adapter Wireless Network Connection:
>
> Connection-specific DNS Suffix . : socal.rr.com
> Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG
> Network
> Connection
>
> Physical Address. . . . . . . . . : 00-1B-77-CE-45-XX
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
>
> Link-local IPv6 Address . . . . . :
> fe80::3cc2:114b:794b:c371%9(Preferred)
>
> IPv4 Address. . . . . . . . . . . : 192.168.1.106(Preferred)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Lease Obtained. . . . . . . . . . : Thursday, January 03, 2008 10:46:41
> AM
> Lease Expires . . . . . . . . . . : Friday, January 04, 2008 10:46:40 AM
> Default Gateway . . . . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . . . . : 192.168.1.1
> DHCPv6 IAID . . . . . . . . . . . : 268442487
> DNS Servers . . . . . . . . . . . : 66.75.164.90
> 66.75.164.89
> NetBIOS over Tcpip. . . . . . . . : Enabled
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . : socal.rr.com
> Description . . . . . . . . . . . : Realtek RTL8101 Family PCI-E Fast
> Ethernet NIC (NDIS 6.0)
>
> Physical Address. . . . . . . . . : 00-1B-24-94-55-XX
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> Link-local IPv6 Address . . . . . :
> fe80::2905:7336:41e0:f454%8(Preferred)
> IPv4 Address. . . . . . . . . . . : 192.168.1.107(Preferred)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Lease Obtained. . . . . . . . . . : Thursday, January 03, 2008 10:46:29
> AM
> Lease Expires . . . . . . . . . . : Friday, January 04, 2008 10:46:28 AM
> Default Gateway . . . . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . . . . : 192.168.1.1
> DHCPv6 IAID . . . . . . . . . . . : 201333540
> DNS Servers . . . . . . . . . . . : 66.75.164.90
> 66.75.164.89
> NetBIOS over Tcpip. . . . . . . . : Enabled
>
> Tunnel adapter Local Area Connection* 9:
> Media State . . . . . . . . . . . : Media disconnected
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
> Physical Address. . . . . . . . . : 02-00-54-55-4E-01
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
>
> Tunnel adapter Local Area Connection* 10:
> Media State . . . . . . . . . . . : Media disconnected
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : 6TO4 Adapter
> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
>
> Tunnel adapter Local Area Connection* 11:
> Connection-specific DNS Suffix . : socal.rr.com
> Description . . . . . . . . . . . : isatap.socal.rr.com
> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> Link-local IPv6 Address . . . . . :
> fe80::5efe:192.168.1.106%12(Preferred)
> Link-local IPv6 Address . . . . . :
> fe80::5efe:192.168.1.107%12(Preferred)
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . : 66.75.164.90
> 66.75.164.89
> NetBIOS over Tcpip. . . . . . . . : Disabled
>
> c:\Windows>ping 127.1.0.0
> Pinging 127.1.0.0 with 32 bytes of data:
>
> Reply from 127.1.0.0: bytes=32 time<1ms TTL=128
> Reply from 127.1.0.0: bytes=32 time<1ms TTL=128
> Reply from 127.1.0.0: bytes=32 time<1ms TTL=128
> Reply from 127.1.0.0: bytes=32 time<1ms TTL=128
>
> Ping statistics for 127.1.0.0:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
> c:\Windows>ping 192.168.1.102
> Pinging 192.168.1.102 with 32 bytes of data:
>
> Reply from 192.168.1.102: bytes=32 time=88ms TTL=64
> Reply from 192.168.1.102: bytes=32 time=1ms TTL=64
> Reply from 192.168.1.102: bytes=32 time=1ms TTL=64
> Reply from 192.168.1.102: bytes=32 time=1ms TTL=64
>
> Ping statistics for 192.168.1.102:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 1ms, Maximum = 88ms, Average = 22ms
>
> c:\Windows>ping www.yahoo.com
>
> Pinging www.yahoo-ht3.akadns.net [209.131.36.158] with 32 bytes of data:
>
> Reply from 209.131.36.158: bytes=32 time=31ms TTL=53
> Reply from 209.131.36.158: bytes=32 time=28ms TTL=54
> Reply from 209.131.36.158: bytes=32 time=42ms TTL=54
> Reply from 209.131.36.158: bytes=32 time=40ms TTL=54
>
> Ping statistics for 209.131.36.158:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
> Approximate round trip times in milli-seconds:
> Minimum = 28ms, Maximum = 42ms, Average = 35ms
>
> c:\Windows>ping www.cnet.com
> Pinging c18-ssa-xw-lb.cnet.com [216.239.122.220] with 32 bytes of data:
>
> Reply from 216.239.122.220: bytes=32 time=58ms TTL=242
> Reply from 216.239.122.220: bytes=32 time=59ms TTL=242
> Reply from 216.239.122.220: bytes=32 time=50ms TTL=242
> Reply from 216.239.122.220: bytes=32 time=55ms TTL=242
>
> Ping statistics for 216.239.122.220:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 50ms, Maximum = 59ms, Average = 55ms
>
> --
> Craig
> PC Slave

Using a Third-Party Firewall

Windows Vista includes a built-in host-based firewall known as Windows
Firewall. When network discovery or file and printer sharing are enabled,
Windows Firewall automatically allows the corresponding incoming traffic.
However, many users use a different firewall product such as Windows Live
OneCare or PC-cillin. These firewalls by default might block incoming
network discovery and file and printer sharing traffic. If a firewall
product other than Windows Firewall is being used, Windows Vista displays an
information message above the Sharing and Discovery section of the Network
and Sharing Center window. Figure 11 shows an example.

Figure 8: The information message in the Network and Sharing Center window
when the Windows Firewall is not being used
Figure 11: The information message in the Network and Sharing Center window
when Windows Firewall is not being used

If you are using a firewall other than Windows Firewall, you must configure
the firewall to allow incoming network discovery and file and printer
sharing traffic.

For network discovery of other computers running Windows Vista, you must
allow the following incoming Transmission Control Protocol (TCP) and User
Datagram Protocol (UDP) traffic:

*

UDP 3702
*

TCP 5357
*

TCP 5358

For network discovery of computers running Windows XP and for file and
printer sharing for both Windows Vista and Windows XP, you must allow the
following incoming traffic:

*

UDP 137
*

UDP 138
*

TCP 139
*

TCP 445

For network discovery of network devices, you must allow the following
incoming traffic:

*

UDP 1900
*

TCP 2869

For more information about how to configure your third-party firewall to
allow incoming traffic, see the documentation for your third-party firewall.



SOURCE: http://technet.microsoft.com/en-us/l.../bb727037.aspx

Cheers,


"Craig" <Craig@discussions.microsoft.com> wrote in message
news:5D234890-7C0B-4A43-B4B7-07894B1E2842@microsoft.com...

>
> My college aged daughter's laptop formerly worked fine but now has odd
> networking issues which prevent the system from browsing the internet.
> The
> system correctly obtains a DHCP address and is able to ping by name,
> websites
> on the web (www.yahoo.com, www.cnet.com), can correctly run AIM and
> Microsoft
> Sidebar but still can not connect the IE7.0 Browser to the internet.
>
> I have read a ton of links here within the Network and Sharing group but I
> haven't seen anything quite like this before. Even though the I know
> better,
> I still went through the exercise of testing for DNS issues as well as the
> often suggested MTU test but there weren't any issues. I have completely
> shut off the Microsoft Firewall to no avail. The system came with a free
> trial of Norton Internet Security but after it expired, I loaded a
> Symantec/Norton Antivirus (NAV 10.1) and did a complete virus scan which
> produced nothing. I also did a full spyware scan which also didn't locate
> any
> serious malware.
>
> Below are the system specifics, I would GREATLY appreciate your
> suggestions.
>
> New Laptop: HP Pavilion dv6500 Notebook (Just bought in Aug)
> Windows Vista Home Premium
> Both a LAN (wired) and Wireless Port are connected to a "newer" Linksys
> SRX200 Wireless Router
>
>
> c:\Windows>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : Audra-PC
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Hybrid
>
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : socal.rr.com
>
> Wireless LAN adapter Wireless Network Connection:
>
> Connection-specific DNS Suffix . : socal.rr.com
> Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG
> Network
> Connection
>
> Physical Address. . . . . . . . . : 00-1B-77-CE-45-XX
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
>
> Link-local IPv6 Address . . . . . :
> fe80::3cc2:114b:794b:c371%9(Preferred)
>
> IPv4 Address. . . . . . . . . . . : 192.168.1.106(Preferred)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Lease Obtained. . . . . . . . . . : Thursday, January 03, 2008 10:46:41
> AM
> Lease Expires . . . . . . . . . . : Friday, January 04, 2008 10:46:40 AM
> Default Gateway . . . . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . . . . : 192.168.1.1
> DHCPv6 IAID . . . . . . . . . . . : 268442487
> DNS Servers . . . . . . . . . . . : 66.75.164.90
> 66.75.164.89
> NetBIOS over Tcpip. . . . . . . . : Enabled
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . : socal.rr.com
> Description . . . . . . . . . . . : Realtek RTL8101 Family PCI-E Fast
> Ethernet NIC (NDIS 6.0)
>
> Physical Address. . . . . . . . . : 00-1B-24-94-55-XX
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> Link-local IPv6 Address . . . . . :
> fe80::2905:7336:41e0:f454%8(Preferred)
> IPv4 Address. . . . . . . . . . . : 192.168.1.107(Preferred)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Lease Obtained. . . . . . . . . . : Thursday, January 03, 2008 10:46:29
> AM
> Lease Expires . . . . . . . . . . : Friday, January 04, 2008 10:46:28 AM
> Default Gateway . . . . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . . . . : 192.168.1.1
> DHCPv6 IAID . . . . . . . . . . . : 201333540
> DNS Servers . . . . . . . . . . . : 66.75.164.90
> 66.75.164.89
> NetBIOS over Tcpip. . . . . . . . : Enabled
>
> Tunnel adapter Local Area Connection* 9:
> Media State . . . . . . . . . . . : Media disconnected
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
> Physical Address. . . . . . . . . : 02-00-54-55-4E-01
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
>
> Tunnel adapter Local Area Connection* 10:
> Media State . . . . . . . . . . . : Media disconnected
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : 6TO4 Adapter
> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
>
> Tunnel adapter Local Area Connection* 11:
> Connection-specific DNS Suffix . : socal.rr.com
> Description . . . . . . . . . . . : isatap.socal.rr.com
> Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP Enabled. . . . . . . . . . . : No
> Autoconfiguration Enabled . . . . : Yes
> Link-local IPv6 Address . . . . . :
> fe80::5efe:192.168.1.106%12(Preferred)
> Link-local IPv6 Address . . . . . :
> fe80::5efe:192.168.1.107%12(Preferred)
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . : 66.75.164.90
> 66.75.164.89
> NetBIOS over Tcpip. . . . . . . . : Disabled
>
> c:\Windows>ping 127.1.0.0
> Pinging 127.1.0.0 with 32 bytes of data:
>
> Reply from 127.1.0.0: bytes=32 time<1ms TTL=128
> Reply from 127.1.0.0: bytes=32 time<1ms TTL=128
> Reply from 127.1.0.0: bytes=32 time<1ms TTL=128
> Reply from 127.1.0.0: bytes=32 time<1ms TTL=128
>
> Ping statistics for 127.1.0.0:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
> c:\Windows>ping 192.168.1.102
> Pinging 192.168.1.102 with 32 bytes of data:
>
> Reply from 192.168.1.102: bytes=32 time=88ms TTL=64
> Reply from 192.168.1.102: bytes=32 time=1ms TTL=64
> Reply from 192.168.1.102: bytes=32 time=1ms TTL=64
> Reply from 192.168.1.102: bytes=32 time=1ms TTL=64
>
> Ping statistics for 192.168.1.102:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 1ms, Maximum = 88ms, Average = 22ms
>
> c:\Windows>ping www.yahoo.com
>
> Pinging www.yahoo-ht3.akadns.net [209.131.36.158] with 32 bytes of data:
>
> Reply from 209.131.36.158: bytes=32 time=31ms TTL=53
> Reply from 209.131.36.158: bytes=32 time=28ms TTL=54
> Reply from 209.131.36.158: bytes=32 time=42ms TTL=54
> Reply from 209.131.36.158: bytes=32 time=40ms TTL=54
>
> Ping statistics for 209.131.36.158:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
> Approximate round trip times in milli-seconds:
> Minimum = 28ms, Maximum = 42ms, Average = 35ms
>
> c:\Windows>ping www.cnet.com
> Pinging c18-ssa-xw-lb.cnet.com [216.239.122.220] with 32 bytes of data:
>
> Reply from 216.239.122.220: bytes=32 time=58ms TTL=242
> Reply from 216.239.122.220: bytes=32 time=59ms TTL=242
> Reply from 216.239.122.220: bytes=32 time=50ms TTL=242
> Reply from 216.239.122.220: bytes=32 time=55ms TTL=242
>
> Ping statistics for 216.239.122.220:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 50ms, Maximum = 59ms, Average = 55ms
>
> --
> Craig
> PC Slave

I've rechecked and there is no 3rd party Firewall on the system and I have
reconfirmed the Vista/Windows FW has been disabled. (To be thorough, I
created policies to make certain the FW, if enabled, would allow both port 80
and 81). I downloaded on another system and installed Firefox on the troubled
system and it also can not communicate with the internet.

The Network and Sharing Center shows a complete/clean internet connection.
The Icon in the toolbar shows the correct two-screens-w/globe with bits
passing in and out. It's odd that even Vista/Windows Network Diagnostics
claims it did not find any problems with this computer's network connection.
Tools other than the browser seem to communicate (AIM, Sidebar, Windows
Update, etc.).

I'm still dead in the water... Any other suggestions??
--
Craig
PC Slave


"Marius Farcas" wrote:

>
> Using a Third-Party Firewall
>
> Windows Vista includes a built-in host-based firewall known as Windows
> Firewall. When network discovery or file and printer sharing are enabled,
> Windows Firewall automatically allows the corresponding incoming traffic.
> However, many users use a different firewall product such as Windows Live
> OneCare or PC-cillin. These firewalls by default might block incoming
> network discovery and file and printer sharing traffic. If a firewall
> product other than Windows Firewall is being used, Windows Vista displays an
> information message above the Sharing and Discovery section of the Network
> and Sharing Center window. Figure 11 shows an example.
>
> Figure 8: The information message in the Network and Sharing Center window
> when the Windows Firewall is not being used
> Figure 11: The information message in the Network and Sharing Center window
> when Windows Firewall is not being used
>
> If you are using a firewall other than Windows Firewall, you must configure
> the firewall to allow incoming network discovery and file and printer
> sharing traffic.
>
> For network discovery of other computers running Windows Vista, you must
> allow the following incoming Transmission Control Protocol (TCP) and User
> Datagram Protocol (UDP) traffic:
>
> *
>
> UDP 3702
> *
>
> TCP 5357
> *
>
> TCP 5358
>
> For network discovery of computers running Windows XP and for file and
> printer sharing for both Windows Vista and Windows XP, you must allow the
> following incoming traffic:
>
> *
>
> UDP 137
> *
>
> UDP 138
> *
>
> TCP 139
> *
>
> TCP 445
>
> For network discovery of network devices, you must allow the following
> incoming traffic:
>
> *
>
> UDP 1900
> *
>
> TCP 2869
>
> For more information about how to configure your third-party firewall to
> allow incoming traffic, see the documentation for your third-party firewall.
>
>
>
> SOURCE: http://technet.microsoft.com/en-us/l.../bb727037.aspx
>
> Cheers,
>
>
> "Craig" <Craig@discussions.microsoft.com> wrote in message
> news:5D234890-7C0B-4A43-B4B7-07894B1E2842@microsoft.com...

>

Maybe the WAP has a firewall (if you connect wireless) ? IPSec ?
Check Internet Options in IE/Connec/LAN settings because I think is set up
to auto ... In this case I suggest you to use only wire conn. or wireless
conn. because IE don't know on what IP to broadcast (maybe you can setup
this in Options) I see 2 different IP addresses witch I assume are the ISP
ones. You don't have the SOHO device installed ? (Did you setup a subnet ?)

?!?!?


"Craig" <Craig@discussions.microsoft.com> wrote in message
news1DA80AC-6F77-4A24-B292-1F2C98D8B294@microsoft.com...

>
> I've rechecked and there is no 3rd party Firewall on the system and I have
> reconfirmed the Vista/Windows FW has been disabled. (To be thorough, I
> created policies to make certain the FW, if enabled, would allow both port
> 80
> and 81). I downloaded on another system and installed Firefox on the
> troubled
> system and it also can not communicate with the internet.
>
> The Network and Sharing Center shows a complete/clean internet connection.
> The Icon in the toolbar shows the correct two-screens-w/globe with bits
> passing in and out. It's odd that even Vista/Windows Network Diagnostics
> claims it did not find any problems with this computer's network
> connection.
> Tools other than the browser seem to communicate (AIM, Sidebar, Windows
> Update, etc.).
>
> I'm still dead in the water... Any other suggestions??
> --
> Craig
> PC Slave
>
>
> "Marius Farcas" wrote:
>

My laptop broadband that is built in is not working anymore, i need help or
solutions to solve this problem

"Marius Farcas" wrote:

> Maybe the WAP has a firewall (if you connect wireless) ? IPSec ?
> Check Internet Options in IE/Connec/LAN settings because I think is set up
> to auto ... In this case I suggest you to use only wire conn. or wireless
> conn. because IE don't know on what IP to broadcast (maybe you can setup
> this in Options) I see 2 different IP addresses witch I assume are the ISP
> ones. You don't have the SOHO device installed ? (Did you setup a subnet ?)
>
> ?!?!?
>
>
> "Craig" <Craig@discussions.microsoft.com> wrote in message
> news1DA80AC-6F77-4A24-B292-1F2C98D8B294@microsoft.com...