Anyone else having problems with their .Mac account? Can't get my mail...can't even go to "www.mac.com".

I'm not in front of my Mac right now, but I can get to www.mac.com

QUOTE (Part Pricer @ Jan 30 2006, 01:25 PM)

I'm not in front of my Mac right now, but I can get to www.mac.com

do a traceroute to www.mac.com and see where the bottleneck is ...

Andy

QUOTE (SirAndy @ Jan 30 2006, 05:38 PM)

do a traceroute to www.mac.com and see where the bottleneck is ...

traceroute?

On Mac OS X, if you would rather not open a terminal and use the command line, a GUI front-end for traceroute (and several other utilities) called Network Utility can be found in the Utilities folder within the Applications folder. Run it, click the “Traceroute” tab, and enter an address to run a trace to.

QUOTE (dkos @ Jan 30 2006, 01:56 PM)

QUOTE (SirAndy @ Jan 30 2006, 05:38 PM) do a traceroute to www.mac.com and see where the bottleneck is ... traceroute?

oh, that's right, you got one of those "oh so user-friendly" Mac's ...


dunno if there's a traceroute utility for the mac, old ones didn't have it, maybe OSX does ...

a traceroute utility lets you view the route between your computer and any other computer. it tells you all the routers (hops) and how fast they responded.
those response times tell you if and where there is a "bottleneck" between you and the machine you're trying to reach.

here's a sample traceroute to www.google.com from my computer at work:

=============================================
Tracing route to www.l.google.com [66.102.7.99]
over a maximum of 30 hops:

1 16 ms 29 ms 35 ms 172.16.119.65
2 58 ms 54 ms 50 ms r1.ca.rwc.bsr.nextweb.net [209.172.111.229]
3 32 ms 30 ms 31 ms r1.ca.pao.bsr.nextweb.net [64.186.170.165]
4 65 ms 29 ms 21 ms r1.ca.paix.cr2.nextweb.net [209.172.123.1]
5 35 ms 46 ms 48 ms r1-ca-paix-cr1-gig2-0.nextweb.net [64.186.160.145]
6 24 ms 31 ms 21 ms ge-9-0-301.hsa3.SanJose1.Level3.net [4.79.59.9]
7 38 ms 18 ms 15 ms so-7-2-0.bbr1.SanJose1.Level3.net [4.68.125.145]
8 10 ms 12 ms 13 ms ae-12-53.car2.SanJose1.Level3.net [4.68.123.80]
9 13 ms 10 ms 20 ms unknown.Level3.net [209.247.202.218]
10 15 ms 13 ms 13 ms 66.249.94.31
11 16 ms 10 ms 13 ms 216.239.49.150
12 22 ms 14 ms 10 ms 66.102.7.99
=============================================

Andy

ok...ran traceroute...it's stll running...looks like this
26***
27***
28***
29***
30***
.......

so what's that mean?

i think thats where your problem is....

b

Run a traceroute to 914world.com and give us the results

QUOTE (dkos @ Jan 30 2006, 02:16 PM)

ok...ran traceroute...it's stll running...looks like this 26*** 27*** 28*** 29*** 30*** ....... so what's that mean?

show us the last couple of entries before you get the "*" ...

"*" means timeout, meaning the router/computer did not respond at all, which could very well be your problem.
a burnt up router inbetween you and mac.com is all you need to be cut off ...

Andy

QUOTE (Part Pricer @ Jan 30 2006, 06:20 PM)

Run a traceroute to 914world.com and give us the results

are you serious?

ok, here you go:

traceroute to www.914world.com (66.250.97.205), 30 hops max, 40 byte packets
1 w097.z208037115.nyc-ny.dsl.cnc.net (208.37.115.97) 7.581 ms 2.496 ms 66.815 ms
2 67.108.98.77.ptr.us.xo.net (67.108.98.77) 10.999 ms 6.605 ms 6.504 ms
3 ge5-0-0.mar1.philadelphia-pa.us.xo.net (207.88.87.49) 4.571 ms 52.857 ms 11.385 ms
4 p5-1-0-1.rar1.washington-dc.us.xo.net (65.106.3.149) 24.692 ms 87.885 ms 123.889 ms
5 p1-0-0.rar1.sanjose-ca.us.xo.net (65.106.0.38) 96.325 ms 91.732 ms 94.855 ms
6 p4-0-0.mar1.roseville-ca.us.xo.net (65.106.5.150) 91.049 ms 91.177 ms 91.394 ms
7 ge0-0.clr1.roseville-ca.us.xo.net (207.88.80.50) 96.477 ms 97.806 ms 93.311 ms
8 66.237.52.110.ptr.us.xo.net (66.237.52.110) 94.395 ms 91.33 ms 128.788 ms

OK. So we know that traceroute is working properly to 914world.com

Do you get *** for all entries when trying mac.com?

QUOTE (SirAndy @ Jan 30 2006, 06:22 PM)

show us the last couple of entries before you get the "*" ...

traceroute to www.mac.com (17.250.248.32), 30 hops max, 40 byte packets
1 w097.z208037115.nyc-ny.dsl.cnc.net (208.37.115.97) 2.976 ms 23.175 ms 2.551 ms
2 67.108.98.77.ptr.us.xo.net (67.108.98.77) 38.82 ms 9.234 ms 11.665 ms
3 ge5-0-0.mar2.philadelphia-pa.us.xo.net (207.88.87.53) 35.398 ms 4.844 ms 4.641 ms
4 p5-1-0-1.rar2.washington-dc.us.xo.net (65.106.3.153) 12.372 ms 20.724 ms 10.577 ms
5 p1-0.ir1.ashburn-va.us.xo.net (65.106.3.138) 13.722 ms 9.48 ms 9.503 ms
6 206.111.0.22.ptr.us.xo.net (206.111.0.22) 17.437 ms 9.611 ms 17.705 ms
7 so1-1-0-2488m.ar1.sjc2.gblx.net (67.17.64.65) 121.315 ms 83.55 ms 83.73 ms
8 internap-ken-schmid-san-jose-3.ge-0-1-0.106.ar1.sjc2.gblx.net (64.212.108.130) 85.617 ms 90.656 ms 86.296 ms
9 bor

sorry wrong section:

7 so1-1-0-2488m.ar1.sjc2.gblx.net (67.17.64.65) 121.315 ms 83.55 ms 83.73 ms
8 internap-ken-schmid-san-jose-3.ge-0-1-0.106.ar1.sjc2.gblx.net (64.212.108.130) 85.617 ms 90.656 ms 86.296 ms
9 border1.pc0-0-bbnet1.sje.pnap.net (66.151.144.4) 242.596 ms 196.449 ms 101.229 ms
10 * * *

It looks like a router crapped out. Log a call with your ISP.

QUOTE (dkos @ Jan 30 2006, 02:33 PM)

9 border1.pc0-0-bbnet1.sje.pnap.net (66.151.144.4) 242.596 ms 196.449 ms 101.229 ms

border1.pc0-0-bbnet1.sje.pnap.net (66.151.144.4) is the last router to respond, after that is silence.

call your ISP and let them know the results of your traceroute. they'll be able to help ...
Andy

PS: found two addresses for pnap.net, the company that runs the last router that responded ...

Operations Center, InterNAP
noc@internap.com
250 Williams St
Suite E-100
Atlanta, GA 30303
US
Phone: (206) 256-9500
Fax: (206) 748-0320

Operations Center, InterNAP Network
noc@INTERNAP.COM
601 UNION ST STE 1000
SEATTLE, WA 98101-4064
US
Phone: 206.256.9500
Fax: 206.256.9580

thanks for the help...just got home and it works fine here.

Don't know who the ISP is at work.