Mark,
I lost my connection today after a few days of uptime. I repeated the
commands that you had suggested to see what differences, if any, there were
as compared to the responses to these commands when the connection was up.
Here are the responses. There were no responses to the pings. There were no
bangs for devices in system info - that I could observe. I was able to
recover the connection by restarting my computer.
Paul
------------------------------------------------------------------------------------
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:3413:30f0:3f57:fe9b
Link-local IPv6 Address . . . . . : fe80::3413:30f0: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 1220
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 904
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 1220
TCP 0.0.0.0:10016 0.0.0.0:0 LISTENING 2128
TCP 0.0.0.0:22043 0.0.0.0:0 LISTENING 1220
TCP 0.0.0.0:31038 0.0.0.0:0 LISTENING 2096
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING 560
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING 1104
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING 1384
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING 1156
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING 616
TCP 0.0.0.0:49160 0.0.0.0:0 LISTENING 604
TCP 127.0.0.1:27015 0.0.0.0:0 LISTENING 4896
TCP 127.0.0.1:27015 127.0.0.1:55065 ESTABLISHED 4896
TCP 127.0.0.1:49184 0.0.0.0:0 LISTENING 4068
TCP 127.0.0.1:49193 0.0.0.0:0 LISTENING 320
TCP 127.0.0.1:49196 0.0.0.0:0 LISTENING 5016
TCP 127.0.0.1:55065 127.0.0.1:27015 ESTABLISHED 1620
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:50080 71.194.95.240:35463 ESTABLISHED 1220
TCP [::]:135 [::]:0 LISTENING 904
TCP [::]:445 [::]:0 LISTENING 4
TCP [::]:2869 [::]:0 LISTENING 4
TCP [::]:5357 [::]:0 LISTENING 4
TCP [::]:6331 [::]:0 LISTENING 4
TCP [::]:31038 [::]:0 LISTENING 2096
TCP [::]:49152 [::]:0 LISTENING 560
TCP [::]:49153 [::]:0 LISTENING 1104
TCP [::]:49154 [::]:0 LISTENING 1384
TCP [::]:49155 [::]:0 LISTENING 1156
TCP [::]:49156 [::]:0 LISTENING 616
TCP [::]:49160 [::]:0 LISTENING 604
UDP 0.0.0.0:123 *:* 1384
UDP 0.0.0.0:500 *:* 1156
UDP 0.0.0.0:3702 *:* 1384
UDP 0.0.0.0:3702 *:* 1384
UDP 0.0.0.0:4500 *:* 1156
UDP 0.0.0.0:5355 *:* 1568
UDP 0.0.0.0:22043 *:* 1220
UDP 0.0.0.0:49164 *:* 1384
UDP 0.0.0.0:49198 *:* 1156
UDP 127.0.0.1:1900 *:* 1384
UDP 127.0.0.1:49199 *:* 1156
UDP 127.0.0.1:49222 *:* 3184
UDP 127.0.0.1:49224 *:* 1220
UDP 127.0.0.1:49227 *:* 3652
UDP 127.0.0.1:49293 *:* 760
UDP 127.0.0.1:49723 *:* 5596
UDP 127.0.0.1:50403 *:* 1384
UDP 127.0.0.1:50420 *:* 1128
UDP 127.0.0.1:50421 *:* 1156
UDP 127.0.0.1:54073 *:* 6424
UDP 192.168.1.100:137 *:* 4
UDP 192.168.1.100:138 *:* 4
UDP 192.168.1.100:1900 *:* 1384
UDP 192.168.1.100:50402 *:* 1384
UDP [::]:123 *:* 1384
UDP [::]:500 *:* 1156
UDP [::]:3702 *:* 1384
UDP [::]:3702 *:* 1384
UDP [::]:5355 *:* 1568
UDP [::]:49165 *:* 1384
UDP [::1]:1900 *:* 1384
UDP [::1]:50400 *:* 1384
UDP [fe80::3413:30f0:3f57:fe9b%10]:1900 *:*
1384
UDP [fe80::3413:30f0:3f57:fe9b%10]:50401 *:*
1384
UDP [fe80::7d35:4fb2:d0b8:7fe8%8]:1900 *:*
1384
UDP [fe80::7d35:4fb2:d0b8:7fe8%8]:50399 *:*
1384
C:\Users\Paul Teicholz>tracert msn.com
Tracing route to msn.com [207.68.172.246]
over a maximum of 30 hops:
1 5 ms 1 ms 2 ms home [192.168.1.254]
2 16 ms 16 ms 15 ms ppp-71-139-15-254.dsl.snfc21.pacbell.net
[71.139
..15.254]
3 16 ms 16 ms 15 ms dist1-vlan50.snfc21.pbi.net [206.171.134.130]
4 14 ms 15 ms 15 ms bb1-10g2-0.snfcca.sbcglobal.net
[216.102.176.224
]
5 17 ms 15 ms 15 ms ex2-p3-0.eqsjca.sbcglobal.net [70.245.63.232]
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 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * *
Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Paul Teicholz>tracert wwww.microsoft.com
Unable to resolve target system name wwww.microsoft.com.
C:\Users\Paul Teicholz>tracert microsoft.com
Tracing route to microsoft.com [207.46.197.32]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms home [192.168.1.254]
2 15 ms 16 ms 17 ms ppp-71-139-15-254.dsl.snfc21.pacbell.net
[71.139
..15.254]
3 15 ms 14 ms 15 ms dist2-vlan62.snfcca.sbcglobal.net
[206.13.3.130]
4 15 ms 14 ms 15 ms bb2-10g2-0.snfcca.sbcglobal.net
[216.102.176.226
]
5 20 ms 18 ms 15 ms ex2-p2-0.eqsjca.sbcglobal.net
[151.164.191.202]
6 18 ms 18 ms 15 ms 151.164.251.26
7 18 ms 48 ms 17 ms ge-7-3-0-57.sjc-64cb-1b.ntwk.msn.net
[207.46.37.
201]
8 18 ms 17 ms 17 ms ge-0-0-0-0.sjc-64cb-1a.ntwk.msn.net
[207.46.37.5
7]
9 35 ms 37 ms 36 ms so-7-2-2-0.tuk-64cb-1a.ntwk.msn.net
[207.46.34.1
62]
10 37 ms 37 ms 35 ms ge-0-1-0-0.cpk-64c-1a.ntwk.msn.net
[207.46.35.6]
11 39 ms 35 ms 37 ms ten3-4.cpk-76c-1b.ntwk.msn.net [207.46.34.118]
12 * * * Request timed out.
13 * * * Request timed out.
14
Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Paul Teicholz>ping 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Paul Teicholz>ping 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Paul Teicholz>
Mark L. Ferguson said:
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/help/help_en-us.htm#RateAPost
Mark L. Ferguson
.
pteicholz said:
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 said:
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/help/help_en-us.htm#RateAPost
Mark L. Ferguson
..
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
:
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/help/help_en-us.htm#RateAPost
Mark L. Ferguson
..
Mark,
Here are the responses to the commands you requested while I am
connected
to
the Internet.