Outline ·
[ Standard ] ·
Linear+
problem connecting to live
|
welwitchia
|
 Sep 12 2007, 10:12 PM
|
|
Any network experts out here that can explain below? I tried to ping www.xbox.com and the results are : QUOTE mark@mark-ubuntu:~$ ping www.xbox.com
PING xbox.com (65.59.234.166) 56(84) bytes of data.
From 219.94.9.182 icmp_seq=1 Time to live exceeded
From 219.94.9.182 icmp_seq=2 Time to live exceeded
From 219.94.9.182 icmp_seq=3 Time to live exceeded Noticed that xbox.com is 65.59.234.166 but my ping times out from 219.94.9.182 instead? So i did a traceroute and here's even more interesting.. Look at the part in red. The packets keeps getting bounced between those 2 IPs. I guess that's where the problem lies. QUOTE mark@mark-ubuntu:~$ tracepath www.xbox.com
1: mark-ubuntu.local (192.168.0.53) 0.094ms pmtu 1500
1: . (192.168.0.1) 0.602ms
2: . (192.168.0.1) asymm 1 0.996ms pmtu 1492
3: 219.93.216.189 (219.93.216.189) asymm 4 58.617ms
4: 210.187.142.1 (210.187.142.1) 32.732ms
5: 210.187.142.5 (210.187.142.5) asymm 4 52.201ms
6: 202.188.0.11 (202.188.0.11) asymm 7 59.928ms
7: 219.94.9.178 (219.94.9.178) asymm 8 334.149ms
8: 219.94.9.182 (219.94.9.182) asymm 9 349.385ms
9: 219.93.174.71 (219.93.174.71) 44.822ms
10: 219.94.9.166 (219.94.9.166) 235.836ms
11: 219.94.9.181 (219.94.9.181) asymm 8 395.750ms
12: ge-6-3-0-59.pao-64cb-1b.ntwk.msn.net (207.46.46.125) asymm 15 353.871ms
13: 219.94.9.181 (219.94.9.181) asymm 8 395.683ms
14: 219.94.9.182 (219.94.9.182) asymm 9 669.244ms
15: 219.94.9.181 (219.94.9.181) asymm 8 462.877ms
16: 219.94.9.182 (219.94.9.182) asymm 9 616.229ms
17: 219.94.9.181 (219.94.9.181) asymm 8 735.632ms
18: 219.94.9.182 (219.94.9.182) asymm 9 841.846ms
19: 219.94.9.181 (219.94.9.181) asymm 8 667.072ms
20: 219.94.9.182 (219.94.9.182) asymm 9 891.573ms
21: 219.94.9.181 (219.94.9.181) asymm 8 927.188ms
22: 219.94.9.182 (219.94.9.182) asymm 9 955.010ms
23: 219.94.9.181 (219.94.9.181) asymm 8 1019.251ms
23: 219.94.9.181 (219.94.9.181) asymm 8 5275.379ms
24: 219.94.9.182 (219.94.9.182) asymm 9 1073.120ms
24: 219.94.9.182 (219.94.9.182) asymm 9 5296.161ms Those with no problems connecting to LIVE, maybe u can do a tracert/traceroute for us just for comparison sake? This post has been edited by welwitchia: Sep 12 2007, 10:33 PM |
|
|
|
|
|
acougan
|
Sep 13 2007, 12:16 AM
|
|
|
i'm using windows. what does tracert do? IP Address: 60.49.107.134 Gateway: 60.49.107.134 cannot login XBL, PSN working fine QUOTE
ping xbox.com
Pinging xbox.com [65.59.234.166] with 32 bytes of data:
Reply from 219.94.9.182: TTL expired in transit.
Reply from 219.94.9.182: TTL expired in transit.
Reply from 219.94.9.182: TTL expired in transit.
Reply from 219.94.9.182: TTL expired in transit.
Ping statistics for 65.59.234.166:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
tracert xbox.com
Tracing route to xbox.com [65.59.234.166]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.123.254
2 17 ms 83 ms 15 ms 219.93.218.177
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
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 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
tracert google.com
Tracing route to google.com [64.233.187.99]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.123.254
2 32 ms 27 ms 27 ms 219.93.218.177
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
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 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
|
|
|
|
|
|
welwitchia
|
Sep 13 2007, 12:46 AM
|
|
|
traceroute "traces" the path u'r packets have to travel to the destination and back. I find it strange that u'rs time out.
|
|
|
|
|
|
shumaky
|
Sep 13 2007, 03:30 AM
|
|
|
QUOTE U:\>ping xbox.com
Pinging xbox.com [65.59.234.166] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 65.59.234.166:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), QUOTE U:\>tracert xbox.com
Tracing route to xbox.com [65.59.234.166]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms bremoffd-129.ipcomms.pacific.net.my [203.114.1.129]
2 <1 ms <1 ms <1 ms klp099.ipcomms.pacific.net.my [203.114.2.1]
3 1 ms 1 ms 1 ms 198.19.0.21
4 11 ms 10 ms 10 ms 198.19.50.37
5 11 ms 11 ms 11 ms 198.19.50.38
6 11 ms 11 ms 11 ms csw-ct3.pacific.net.sg [203.120.91.6]
7 11 ms 11 ms 11 ms scipk004.pacific.net.sg [203.120.91.4]
8 12 ms 11 ms 11 ms 203.208.143.29
9 11 ms 12 ms 12 ms ge-4-0-1-0.sngc3-cr1.ix.singtel.com [203.208.172.157]
10 189 ms 199 ms 189 ms so-1-2-0-0.laxow-cr2.ix.singtel.com [203.208.172.46]
11 214 ms 183 ms 196 ms ge-2-1-2-0.laxow-dr2.ix.singtel.com [203.208.171.58]
12 219 ms 219 ms 225 ms ge-0-1-0-0.plapx-dr2.ix.singtel.com [203.208.149.253]
13 232 ms 221 ms 221 ms 203.208.147.42
14 214 ms 221 ms 213 ms ge-1-3-0-56.pao-64cb-1a.ntwk.msn.net [207.46.46.113]
15 224 ms 231 ms 225 ms so-7-2-1-0.wst-64cb-1a.ntwk.msn.net [207.46.35.149]
16 239 ms 239 ms 232 ms ge-7-0-0-0.wst-64cb-1b.ntwk.msn.net [207.46.34.122]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
U:\> Here is mine at office.. |
|
|
|
|
|
blacktrix
|
Sep 13 2007, 09:15 AM
|
Scott Pilgrim Vs The World!
|
Ha! Found out the problem! If you connect to a 95.xxx.xxx Server, you can get into Live!
I'm in Bangsar, so I don't know about the rest of you all, but 208 and 60 doesn't work for me........
Once I switched to 95...... not a problem!!!!!
|
|
|
|
|
|
alkt
|
Sep 13 2007, 09:28 AM
|
^_^
|
mine seems to lock to 60.xxx.xx  |
|
|
|
|
|
tailgunner
|
Sep 13 2007, 09:47 AM
|
Getting Started
|
mine one ok with ip 60.XX.XX.XX the only problem is my streamyx account always get stuck error 691 have to call them almost every night.  |
|
|
|
|
|
shumaky
|
Sep 14 2007, 10:39 AM
|
|
|
im fecking stuck with 60.X n its not getting me anywhere..
feck this syit
|
|
|
|
|
|
blacktrix
|
Sep 14 2007, 01:44 PM
|
Scott Pilgrim Vs The World!
|
60 sucks...... try disconnecting and reconnecting until you get either 95 or 94....
To me 94 works better......
|
|
|
|
|
|
shumaky
|
Sep 14 2007, 03:04 PM
|
|
|
^ tried for like 20 times.. still stuck at 60.x IP
|
|
|
|
|
|
terencey
|
Sep 14 2007, 07:32 PM
|
Getting Started
|
Guys,
According to my TM client, he said it should be solved already. Anybody can confirm this? I still in office so I dunno yet.
|
|
|
|
|
|
bansai
|
Sep 14 2007, 07:35 PM
|
|
|
connection seems kinda fast here in kota damansara.. my fifa08 demo download is almost done..
|
|
|
|
|
|
welwitchia
|
Sep 14 2007, 07:44 PM
|
|
|
My IP : 60.49.35.103 As of now, I can connect to LIVE.  QUOTE(terencey @ Sep 14 2007, 07:32 PM) Guys, According to my TM client, he said it should be solved already. Anybody can confirm this? I still in office so I dunno yet. |
|
|
|
|
|
gnome
|
Sep 14 2007, 07:58 PM
|
|
|
QUOTE(terencey @ Sep 14 2007, 07:32 PM) Guys, According to my TM client, he said it should be solved already. Anybody can confirm this? I still in office so I dunno yet. Quaker seems can online ady, not sure about others  |
|
|
|
|
|
terencey
|
Sep 14 2007, 08:13 PM
|
Getting Started
|
Cool, I also can online now. Looks like my client had problem solved. Thank god.
Now just wait for confirmation from the rest of the people that got LIVE issue.
This post has been edited by terencey: Sep 14 2007, 08:20 PM
|
|
|
|
|
|
SUSMightySmiter
|
Sep 14 2007, 09:38 PM
|
|
|
i dunno, i kinda one shotted connected to LIVE without having to restart the router....seems fine
|
|
|
|
|
|
alkt
|
Sep 14 2007, 09:39 PM
|
^_^
|
so far so good. i am able to connect. hopefully won't dc later  |
|
|
|
|
|
Merlin MY
|
Sep 14 2007, 09:57 PM
|
New Member
|
i'm A-LIVE!!!! so far it's looking good. hopefully it stays that way.  |
|
|
|
|
Quote
0.0410sec
0.75
5 queries
GZIP Disabled