No NAM from home.
Joined: Feb 2005
Posts: 4,054
Likes: 0
From: As far away from Florida as I can get.
No NAM from home.
I am unable to connect to NAM from 63.109.58.x ip range. I know there was a similar issue before. Can we get it fixed. LMK if you need more info.
Can't get in from home either. Unable to connect all day yesterday and this morning. Thought it might be a Comcast DNS server issue. I'm in the Baltimore area. Am posting from work, where there is not a problem.
Trending Topics
Last time this has happened it was the fault of a router at the company that hosts NAM, The Planet. Apparently this router was dropping page requests from people who's IP addresses fell within a certain range. I am affected at home as well, and have to post from work.
I know NAM went down for everyone Sunday morning. (see this thread). It also went down for me at home Saturday & another day from work last week for at least an hour
I'll get my IP address/range tonight . . . but I also had no connection Sat. or Sunday through Time Warner -- I actually got a lot done around the house
. . . so that's what it's like to have a life!
Edit -- actually i didn't -- I used the free time to install my MiniDoMore trailer hitch, and to buy supplies for my next couple MINI projects
. . . so that's what it's like to have a life!Edit -- actually i didn't -- I used the free time to install my MiniDoMore trailer hitch, and to buy supplies for my next couple MINI projects
It seems to be a routing issue and not DNS. A DNS issue will allow you to get through using the IP address. Routing problems are essentially trying to connect us to a dead end.
Start>Run Type in cmd hit enter
In the new window type tracert 69.93.166.248 hit enter
Post results
Last edited by gnatster; May 22, 2007 at 06:48 AM.
That is the response I got from the delightful comas* chat session help. Will have to wait till I get home tonight to run it, then start another chat session with comcas*.
Ain't technology grand!
Ain't technology grand!
Its definitely a routing issue. I can switch my dns servers to known working one's (ie Verizon's) and still no connection.
Comcast uses Level 3 pipes for their traffic but some other Level 3 clients seem to work per tracert results....
Per my results, packets are making to the rack, but not the box...
Tracing route to northamericanmotoring.com [xxx.xxx.xxx.xxx]
over a maximum of 30 hops:
1 * * * Request timed out.
2 8 ms 16 ms 7 ms ge-1-22-ur01.howardcounty.md.bad.comcast.net [68.87.131.81]
3 8 ms 7 ms 7 ms te-9-3-ar01.howardcounty.md.bad.comcast.net [68.87.129.37]
4 9 ms 7 ms 8 ms po-10-ar02.whitemarsh.md.bad.comcast.net [68.87.129.34]
5 9 ms 9 ms 7 ms po-90-ar01.whitemarsh.md.bad.comcast.net [68.86.252.217]
6 11 ms 10 ms 11 ms 68.87.129.137
7 13 ms 12 ms 13 ms 68.86.90.93
8 13 ms 12 ms 13 ms ge-5-1-125.ipcolo1.Washington1.Level3.net [63.210.62.157]
9 17 ms 17 ms 17 ms ae-32-54.ebr2.Washington1.Level3.net [4.68.121.126]
10 22 ms 18 ms 17 ms ae-1-100.ebr1.Washington1.Level3.net [4.69.132.29]
11 27 ms 35 ms 36 ms ae-2.ebr1.Atlanta2.Level3.net [4.69.132.85]
12 59 ms 55 ms 53 ms ae-7.ebr2.Dallas1.Level3.net [4.69.134.21]
13 46 ms * * ae-24-54.car4.Dallas1.Level3.net [4.68.122.112]
14 49 ms 50 ms 49 ms THE-PLANET.car4.Dallas1.Level3.net [4.71.122.2]
15 46 ms 55 ms 46 ms te7-2.dsr01.dllstx3.theplanet.com [70.87.253.10]
16 48 ms 49 ms 47 ms 7e.fd.5746.static.theplanet.com [70.87.253.126]
17 52 ms 49 ms 48 ms po2.car19.dllstx2.theplanet.com [12.96.160.36]
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.
Comcast uses Level 3 pipes for their traffic but some other Level 3 clients seem to work per tracert results....
Per my results, packets are making to the rack, but not the box...
Tracing route to northamericanmotoring.com [xxx.xxx.xxx.xxx]
over a maximum of 30 hops:
1 * * * Request timed out.
2 8 ms 16 ms 7 ms ge-1-22-ur01.howardcounty.md.bad.comcast.net [68.87.131.81]
3 8 ms 7 ms 7 ms te-9-3-ar01.howardcounty.md.bad.comcast.net [68.87.129.37]
4 9 ms 7 ms 8 ms po-10-ar02.whitemarsh.md.bad.comcast.net [68.87.129.34]
5 9 ms 9 ms 7 ms po-90-ar01.whitemarsh.md.bad.comcast.net [68.86.252.217]
6 11 ms 10 ms 11 ms 68.87.129.137
7 13 ms 12 ms 13 ms 68.86.90.93
8 13 ms 12 ms 13 ms ge-5-1-125.ipcolo1.Washington1.Level3.net [63.210.62.157]
9 17 ms 17 ms 17 ms ae-32-54.ebr2.Washington1.Level3.net [4.68.121.126]
10 22 ms 18 ms 17 ms ae-1-100.ebr1.Washington1.Level3.net [4.69.132.29]
11 27 ms 35 ms 36 ms ae-2.ebr1.Atlanta2.Level3.net [4.69.132.85]
12 59 ms 55 ms 53 ms ae-7.ebr2.Dallas1.Level3.net [4.69.134.21]
13 46 ms * * ae-24-54.car4.Dallas1.Level3.net [4.68.122.112]
14 49 ms 50 ms 49 ms THE-PLANET.car4.Dallas1.Level3.net [4.71.122.2]
15 46 ms 55 ms 46 ms te7-2.dsr01.dllstx3.theplanet.com [70.87.253.10]
16 48 ms 49 ms 47 ms 7e.fd.5746.static.theplanet.com [70.87.253.126]
17 52 ms 49 ms 48 ms po2.car19.dllstx2.theplanet.com [12.96.160.36]
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.
Thanks!
Thread
Thread Starter
Forum
Replies
Last Post
PelicanParts.com
Interior/Exterior Products
7
Jun 7, 2025 05:56 AM
PelicanParts.com
Accessory Products
0
Oct 1, 2015 01:23 PM
Mini Mania
Drivetrain Products
0
Sep 28, 2015 09:13 AM
Mini Mania
Vendor Announcements
0
Sep 25, 2015 12:32 PM




