Vista - Connection to internet

I have been having the problem of losing my connection to the internet for
the past year. I am using Vista Ultimate. About one every day or two, my
computer stops reading and writing to the Intetrnet. The hardware connection
is not lost and appears to be properly connected. It does not depend upon
what type of connection I am using: Lynksys router, wifi link in a cafe,
wired link to a router. Sometimes the connection will start working again,
but this can take an undertermined amount of time (say 1 to 10 hours). I have
tried disconnecting and reconnecting to the router or wife connction, but
this does not help. The only way I have found to correct this probelm is to
restart the computer. This always works. My internet server is msn.com.

You need to 'gather some data' to help find what is happening.
Open a command prompt, and type:
IPCONFIG
Do you have an IP at all when this happens? Which one? a Default Gateway?

type:
NETSTAT /ANO
What is 'Listening' and to what address?

type:
TRACERT www.microsoft.com
did it fail along the way?

type :
ping <default gateway address here>

Have you looked at Device Manager (devmgmt.msc) Do you see any 'bangs'
(exclamation points) ?

--
Was this helpful? Then click the "Yes" Ratings button. Voting helps the web
interface.
http://www.microsoft.com/wn3/locales....htm#RateAPost

Mark L. Ferguson

..
"pteicholz" <pteicholz@xxxxxx> wrote in message
news:925B50B2-0BD6-42CF-92ED-C09D83633B51@xxxxxx

Mark,
Thanks for the suggestions. I tried these commands while I did have a
connection, and some of them generate considerable output. I was wondering if
there is a way to capture (save) this information so that I can past the
results into a message to show you the results. If there is, it might be
helpful.
Paul

"Mark L. Ferguson" wrote:

a cmd window has a 'system' icon in the top left corner, and that has an
edit/mark, and edit/copy feature. Don't worry about the volume, the trolls
here fill this newsgroup up daily.
--
Was this helpful? Then click the "Yes" Ratings button. Voting helps the web
interface.
http://www.microsoft.com/wn3/locales....htm#RateAPost

Mark L. Ferguson

..
"pteicholz" <pteicholz@xxxxxx> wrote in message
news:E836A822-9C86-4742-AD90-58AA46A0C8D0@xxxxxx

Mark,
Here are the responses to the commands you requested while I am connected to
the Internet.
Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Paul Teicholz>ipconfig

Windows IP Configuration


Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : gateway.2wire.net
Link-local IPv6 Address . . . . . : fe80::7d35:4fb2:d0b8:7fe8%8
IPv4 Address. . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : myhome.westell.com

Tunnel adapter Local Area Connection*:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e66:24ae:3e07:3f57:fe9b
Link-local IPv6 Address . . . . . : fe80::24ae:3e07:3f57:fe9b%10
Default Gateway . . . . . . . . . : ::

Tunnel adapter Local Area Connection* 10:

Connection-specific DNS Suffix . : gateway.2wire.net
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.100%17
Default Gateway . . . . . . . . . :

Tunnel adapter Local Area Connection* 8:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 12:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 13:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

C:\Users\Paul Teicholz>netstat /ano

Active Connections

Proto Local Address Foreign Address State PID
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 3116
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 964
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 3116
TCP 0.0.0.0:10016 0.0.0.0:0 LISTENING 2248
TCP 0.0.0.0:22043 0.0.0.0:0 LISTENING 3116
TCP 0.0.0.0:31038 0.0.0.0:0 LISTENING 2192
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING 624
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING 1160
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING 1416
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING 1208
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING 680
TCP 0.0.0.0:49212 0.0.0.0:0 LISTENING 668
TCP 127.0.0.1:10016 127.0.0.1:59031 TIME_WAIT 0
TCP 127.0.0.1:10016 127.0.0.1:59033 TIME_WAIT 0
TCP 127.0.0.1:27015 0.0.0.0:0 LISTENING 1540
TCP 127.0.0.1:49172 0.0.0.0:0 LISTENING 2320
TCP 192.168.1.100:139 0.0.0.0:0 LISTENING 4
TCP 192.168.1.100:6331 0.0.0.0:0 LISTENING 4
TCP 192.168.1.100:49176 71.138.49.86:32053 ESTABLISHED 3116
TCP 192.168.1.100:49178 207.46.109.45:1863 ESTABLISHED 3108
TCP 192.168.1.100:59034 65.55.131.125:80 TIME_WAIT 0
TCP 192.168.1.100:59036 65.54.170.18:80 ESTABLISHED 4860
TCP 192.168.1.100:59037 64.4.57.119:80 TIME_WAIT 0
TCP [::]:135 [::]:0 LISTENING 964
TCP [::]:445 [::]:0 LISTENING 4
TCP [::]:2869 [::]:0 LISTENING 4
TCP [::]:5357 [::]:0 LISTENING 4
TCP [::]:6331 [::]:0 LISTENING 4
TCP [::]:31038 [::]:0 LISTENING 2192
TCP [::]:49152 [::]:0 LISTENING 624
TCP [::]:49153 [::]:0 LISTENING 1160
TCP [::]:49154 [::]:0 LISTENING 1416
TCP [::]:49155 [::]:0 LISTENING 1208
TCP [::]:49156 [::]:0 LISTENING 680
TCP [::]:49212 [::]:0 LISTENING 668
UDP 0.0.0.0:123 *:* 1416
UDP 0.0.0.0:500 *:* 1208
UDP 0.0.0.0:3702 *:* 1416
UDP 0.0.0.0:3702 *:* 1416
UDP 0.0.0.0:4500 *:* 1208
UDP 0.0.0.0:5355 *:* 1612
UDP 0.0.0.0:22043 *:* 3116
UDP 0.0.0.0:49168 *:* 1416
UDP 0.0.0.0:49239 *:* 1208
UDP 127.0.0.1:1900 *:* 1416
UDP 127.0.0.1:49189 *:* 3116
UDP 127.0.0.1:49192 *:* 3108
UDP 127.0.0.1:49240 *:* 1208
UDP 127.0.0.1:49252 *:* 3988
UDP 127.0.0.1:49265 *:* 1188
UDP 127.0.0.1:49272 *:* 1208
UDP 127.0.0.1:49306 *:* 1416
UDP 127.0.0.1:49403 *:* 4860
UDP 127.0.0.1:49780 *:* 2328
UDP 127.0.0.1:49999 *:* 3232
UDP 192.168.1.100:9 *:* 3108
UDP 192.168.1.100:137 *:* 4
UDP 192.168.1.100:138 *:* 4
UDP 192.168.1.100:1900 *:* 1416
UDP 192.168.1.100:49305 *:* 1416
UDP 192.168.1.100:50152 *:* 3232
UDP 192.168.1.100:50153 *:* 3232
UDP [::]:123 *:* 1416
UDP [::]:500 *:* 1208
UDP [::]:3702 *:* 1416
UDP [::]:3702 *:* 1416
UDP [::]:5355 *:* 1612
UDP [::]:49169 *:* 1416
UDP [::1]:1900 *:* 1416
UDP [::1]:49303 *:* 1416
UDP [fe80::24ae:3e07:3f57:fe9b%10]:1900 *:*
1416
UDP [fe80::24ae:3e07:3f57:fe9b%10]:49304 *:*
1416
UDP [fe80::7d35:4fb2:d0b8:7fe8%8]:1900 *:*
1416
UDP [fe80::7d35:4fb2:d0b8:7fe8%8]:49302 *:*
1416

C:\Users\Paul Teicholz>tracert

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout]
[-R] [-S srcaddr] [-4] [-6] target_name

Options:
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list (IPv4-only).
-w timeout Wait timeout milliseconds for each reply.
-R Trace round-trip path (IPv6-only).
-S srcaddr Source address to use (IPv6-only).
-4 Force using IPv4.
-6 Force using IPv6.

C:\Users\Paul Teicholz>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=255
Reply from 192.168.1.254: bytes=32 time=1ms TTL=255
Reply from 192.168.1.254: bytes=32 time=2ms TTL=255
Reply from 192.168.1.254: bytes=32 time=3ms TTL=255

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

C:\Users\Paul Teicholz>

The device manager shows no "bangs"

"Mark L. Ferguson" wrote:

Excellent work. You can ping your router, and the router seems to be
offline. Open the router configuration app (http://192.168.1.254 ) You will
see an area to examine the WAN (internet) configuration, and look for its IP
address ( possibly open http://192.168.0.1 ) See if you can ping it, too.
All this while you are having trouble connecting. If it pings, you can look
to your browser config or MSN.com for your problem.
You didn't use tracert correctly. It needs an address:

tracert msn.com

I suspect your error happens when tracert says one of your 'hops' is failing
(not the first one)
This would be an MSN error.

--
Was this helpful? Then click the "Yes" Ratings button. Voting helps the web
interface.
http://www.microsoft.com/wn3/locales....htm#RateAPost

Mark L. Ferguson

..
"pteicholz" <pteicholz@xxxxxx> wrote in message
news:61240979-A427-4BFA-888A-99C939EF4E5F@xxxxxx

Here is tracert msn.com while I am connected:
Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Paul Teicholz>tracert msn.com

Tracing route to msn.com [207.68.172.246]
over a maximum of 30 hops:

1 2 ms 1 ms * home [192.168.1.254]
2 20 ms 18 ms 17 ms ppp-71-139-47-254.dsl.snfc21.pacbell.net
[71.139
..47.254]
3 15 ms 16 ms 14 ms dist1-vlan62.snfcca.sbcglobal.net
[206.13.3.129]

4 16 ms 16 ms 14 ms bb1-10g2-0.snfcca.sbcglobal.net
[216.102.176.224
]
5 16 ms 17 ms 18 ms ex2-p2-0.eqsjca.sbcglobal.net
[151.164.191.202]

6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * *

Paul

"Mark L. Ferguson" wrote:

As I expected from MSN ( :/ ) It's "Not Your Fault ! : ) )
All kidding aside, msn is having an epiphany at the moment. Passport is
down, their site is a wreak, and their staff is having 'takeover-itis'
I suggest simply having patience with their changeover, or find a new ISP.
Your system is fine, it's your connection that is at fault.

--
Was this helpful? Then click the "Yes" Ratings button. Voting helps the web
interface.
http://www.microsoft.com/wn3/locales....htm#RateAPost

Mark L. Ferguson

..
"pteicholz" <pteicholz@xxxxxx> wrote in message
news:9887E72E-E21C-4226-BCB9-EB4389F4B78F@xxxxxx

Mark,
You could be right, but there is some evidence that it might not be their
fault:
1. The problem has been going on for a long time (before they started their
offer for Yahoo.
2. I can always fix the problem by restarting the computer.
Is there some possibility that the process of checking the phishing filter
for a web site somehow causes problems?
Here is the results of a tracert msn.com without use of the phishing filter:
Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Paul Teicholz>tracert msn.com

Tracing route to msn.com [207.68.172.246]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms home [192.168.1.254]
2 15 ms 19 ms * ppp-71-139-47-254.dsl.snfc21.pacbell.net
[71.139
..47.254]
3 19 ms 17 ms 17 ms dist1-vlan62.snfcca.sbcglobal.net
[206.13.3.129]

4 17 ms 15 ms 15 ms bb1-10g2-0.snfcca.sbcglobal.net
[216.102.176.224
]
5 21 ms 18 ms 16 ms ex2-p3-0.eqsjca.sbcglobal.net [70.245.63.232]
6 * * * Request timed out.
7 * *
etc.
And here are the results with the filter on:
Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Paul Teicholz>tracert msn.com

Tracing route to msn.com [207.68.172.246]
over a maximum of 30 hops:

1 4 ms 7 ms 7 ms home [192.168.1.254]
2 15 ms 21 ms 16 ms ppp-71-139-47-254.dsl.snfc21.pacbell.net
[71.139
..47.254]
3 15 ms 19 ms 17 ms dist1-vlan62.snfcca.sbcglobal.net
[206.13.3.129]

4 15 ms 17 ms 18 ms bb1-10g2-0.snfcca.sbcglobal.net
[216.102.176.224
]
5 16 ms 16 ms 17 ms ex2-p3-0.eqsjca.sbcglobal.net [70.245.63.232]
6 * *
etc.
I don't see any difference, do you?
Paul



"Mark L. Ferguson" wrote:

Well, as a coincidence, Live was down today, which is used by the msn site.
I don't think the phishing filter would effect the traceRT utility. It seems
to be working fine.
You seem to be using a path on the internet that is failing for you. I can't
really tell you what that might be causing that.

--
Was this helpful? Then click the "Yes" Ratings button. Voting helps the web
interface.
http://www.microsoft.com/wn3/locales....htm#RateAPost

Mark L. Ferguson

..
"pteicholz" <pteicholz@xxxxxx> wrote in message
news:4871E49B-B22E-470A-AF5B-FB2BB3877E57@xxxxxx