The problems accessing the site

Since I could not access this site yesterday I did some checking and sent this info to Troy
As you can see the trace went well until it got to Denver then timed out.

This explains the sporadic access because when the Internet is really busy it will reroute you through other servers.

After finding this I called my ISP and they told me they were aware of gateway server problems on the Internet but was nothing that they could do since it was not in their system

It is my guess that when Troy switched servers the address for it goes through this defective server.

I did a trace on a site that works and the trace took me through Denver but the server had a different number and it worked so it is not just Denver but one server at Denver,

Their is NO point in messing with your computer
I ask Embarq if they knew where I could call and she said no.
She was in Pennsylvania and she could access DC so it depends on your location as to if you will have a problem.

Now that I know what the problem is how do I fix it other than just wait and hope that someone fixes it.:wall




Tracing route to www.detailcity.org [216.24.138.135]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.2.1
2 35 ms 35 ms 36 ms in-67-237-32-1.dhcp.emb
3 35 ms 35 ms 34 ms 67.235.59.213
4 54 ms 55 ms 54 ms ge-6-21.car2.Chicago2.L
5 54 ms 54 ms 55 ms vlan51.ebr1.Chicago2.Le
6 78 ms 89 ms 89 ms ae-3.ebr2.Denver1.Level
7 78 ms 78 ms 78 ms ge-5-0-0-52.gar1.Denver
]
8 78 ms 78 ms 78 ms VIAWEST-INT.gar1.Denver
9 79 ms 79 ms 79 ms gec-008.crrt02.den05.vi
10 80 ms 80 ms 98 ms pos-02-00-crrt02.den01.
3]
11 80 ms 80 ms 80 ms gec-006.crrt01.den01.vi
12 80 ms 80 ms 80 ms pos-02-00-crrt01.den02.
0]
13 80 ms 81 ms 81 ms vi-010.aggm02.den02.via
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
 
Since I'm on the site this morning I did a trace here is the results. Notice that it did not go through Denver.


Tracing route to detailcity.org [216.246.2.2]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.2.1
2 35 ms 35 ms 35 ms in-67-237-32-1.dhcp.embarqhsd.net [67.237.32.1]
3 35 ms 34 ms 35 ms 67.235.59.213
4 55 ms 54 ms 55 ms ge-6-21.car2.Chicago2.Level3.net [4.71.250.17]
5 54 ms 54 ms 55 ms vlan51.ebr1.Chicago2.Level3.net [4.69.138.158]
6 60 ms 55 ms 54 ms ae-6.ebr1.Chicago1.Level3.net [4.69.140.189]
7 56 ms 55 ms 56 ms ae-13-51.car3.Chicago1.Level3.net [4.68.101.7]
8 56 ms 55 ms 55 ms 263.xe-0-3-0.cr2.ord1.us.scnet.net [4.71.100.38]
9 63 ms 59 ms 64 ms v21.ar2.ord1.us.scnet.net [216.246.95.244]
10 55 ms 55 ms 55 ms 498.tge9-4.ar2.ord1.us.scnet.net [216.246.72.34]
11 75 ms 56 ms 56 ms vps79.servershost.net [216.246.79.183]
12 62 ms 56 ms 56 ms unknown.hostforweb.com [216.246.2.2]
 
When I query DC I get a different IP address (216.246.2.2.)

I tried pinging 216.24.138.135 and it times out. I would try using the ip address I have as the url and see if it gets through.

This sounds like a DNS issue. That is, there is some server has not been updated. The sporatic nature seems to imply that it takes different routes and sometimes it goes through this router. This could explain why it comes and goes and other surfing is not affected.
 
Bunky said:
When I query DC I get a different IP address (216.246.2.2.)

I tried pinging 216.24.138.135 and it times out. I would try using the ip address I have as the url and see if it gets through.

This sounds like a DNS issue. That is, there is some server has not been updated. The sporatic nature seems to imply that it takes different routes and sometimes it goes through this router. This could explain why it comes and goes and other surfing is not affected.
Click to expand...
Yes if you look at the trace that I just did while on DC and it is the same as yours 216.246.2.2
 
BUNKY I get the same thing when I ping 216.24.138.135 it times out but if I ping 216.246.2.2 it works.
I just removed everything from my computer and then clicked on use current page.
Since I;m being routed around the server in Denver.
I hope this works. Sounds like we have found the problem.
God know how long it will Me before the Denver server updates.
 
Last night, October 31, I had access at 7 PM.
Came back about 10:30 and did not have access.
Sometimes I will be able to access the site via dial-up, (I'm on dial-up right now), but sometimes it won't work either. Last night it would not.
Today, November 1, I can't access through Mediacom, but I can get on via dial-up.
Like several others, I have absolutely no problems with any site other than DC.
It may be fixing itself, but not too quickly. :)

As an aside. How many times have you ever had something "fix itself"?
 
CharlesW said:
Last night, October 31, I had access at 7 PM.
Came back about 10:30 and did not have access.
Sometimes I will be able to access the site via dial-up, (I'm on dial-up right now), but sometimes it won't work either. Last night it would not.
Today, November 1, I can't access through Mediacom, but I can get on via dial-up.
Like several others, I have absolutely no problems with any site other than DC.
It may be fixing itself, but not too quickly. :)

As an aside. How many times have you ever had something "fix itself"?
Click to expand...
Charles the next time you can not access this site do a route trace and see if it is looking for 216.24.138.135 and if it is going through VIA WEST at Denver.
I bet it is.:wall
The IP for the new dc server is 216.246.2.2 it
 
black bart said:
Charles the next time you can not access this site do a route trace and see if it is looking for 216.24.138.135 and if it is going through VIA WEST at Denver.
I bet it is.:wall
The IP for the new dc server is 216.246.2.2 it
Click to expand...
Bart:
I appreciate your efforts and what you are trying to do, but.....
1. I have no idea what you are talking about. :confused:
2. I have no idea how to do a route trace and really don't have any interest in learning how to do one. :notme:
3. If I did find what you are referring to, I would have no idea what to do about it. :huh:
Again, I have no interest in learning what to do about it. :notme:
4. My internet surfing is for pleasure. :bigups
5. If it becomes work or even a challenge, then I will find something else to do with my spare time. :stick
6. I would hate to lose contact with the people at DC, but if it happens, it happens. :cry:
It was nice being able to get access this evening, but I really don't expect it to last permanently.
Time will tell. :)
 
CharlesW said:
Bart:
I appreciate your efforts and what you are trying to do, but.....
1. I have no idea what you are talking about. :confused:
2. I have no idea how to do a route trace and really don't have any interest in learning how to do one. :notme:
3. If I did find what you are referring to, I would have no idea what to do about it. :huh:
Again, I have no interest in learning what to do about it. :notme:
4. My internet surfing is for pleasure. :bigups
5. If it becomes work or even a challenge, then I will find something else to do with my spare time. :stick
6. I would hate to lose contact with the people at DC, but if it happens, it happens. :cry:
It was nice being able to get access this evening, but I really don't expect it to last permanently.
Time will tell. :)
Click to expand...

Charles I feel your pain :wall ... if pleasure turns to pain it is not usually worth it :mad:

I also tend to wonder how many other members and even lurkers and not getting through and do not have the persistence you and Black Bart have had as to get here. :confused:

I know Troy will do whatever it takes to fix this even it means moving to another server ;)
 
Poorboy said:
Charles I feel your pain :wall ... if pleasure turns to pain it is not usually worth it :mad:

I also tend to wonder how many other members and even lurkers and not getting through and do not have the persistence you and Black Bart have had as to get here. :confused:

I know Troy will do whatever it takes to fix this even it means moving to another server ;)
Click to expand...
Like you, I fully expect Troy to get on top of the problem.
In my first post in this thread, I commented that the "frustration we are feeling is probably a very small amount compared to what Troy is going through."
I still feel that way and I guess if he can stick it out, I should be able to. :)
 
Switching servers again has crossed my mind and I just might do that. The customer service with the new server is lacking.

If I knew for sure it would fix the problem I would do it in a heart beat.
 
blk45 said:
You guys should use Open DNS. Their servers are much better than your IPs and they are free.

OpenDNS > Home Network > Solutions

Change your DNS servers to:
208.67.222.222
208.67.220.220

FYI, you don't have to open an account to use them.
Click to expand...

I had been considering something like this but not aware of this. My work DNS servers seem to be faster than my local ISP (roadrunner). I have been able to VPN to my work id and surf faster (through roadrunner) than natively than rr.
 
This morning I'm able to access this site so I pinged it and did a trace and just like the last time it did not go to Denver.
When it goes to Denver it is 216-24-138-135 and I bet that is the IP for the old DC server that has been shut down
Edit Just did a check on Troys site Dc.com it is 216-252-126-190

Results from today

Pinging detailcity.org [216.246.2.2] with 32 bytes of data:
Reply from 216.246.2.2: bytes=32 time=101ms TTL=53
Reply from 216.246.2.2: bytes=32 time=95ms TTL=53
Reply from 216.246.2.2: bytes=32 time=55ms TTL=53
Reply from 216.246.2.2: bytes=32 time=85ms TTL=53
Ping statistics for 216.246.2.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 101ms, Average = 84ms



Tracing route to detailcity.org [216.246.2.2]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.2.1
2 34 ms 35 ms 36 ms in-67-237-32-1.dhcp.embarqhsd.net [67.237.32.1]
3 36 ms 35 ms 34 ms 67.235.59.209
4 54 ms 54 ms 54 ms ge-6-21.car2.Chicago2.Level3.net [4.71.250.17]
5 55 ms 54 ms 55 ms vlan51.ebr1.Chicago2.Level3.net [4.69.138.158]
6 55 ms 55 ms 68 ms ae-6.ebr1.Chicago1.Level3.net [4.69.140.189]
7 55 ms 55 ms 55 ms ae-13-53.car3.Chicago1.Level3.net [4.68.101.71]
8 54 ms 55 ms 54 ms 263.xe-0-3-0.cr2.ord1.us.scnet.net [4.71.100.38]
9 55 ms 56 ms 55 ms v21.ar2.ord1.us.scnet.net [216.246.95.244]
10 55 ms 55 ms 74 ms 498.tge9-4.ar2.ord1.us.scnet.net [216.246.72.34]
11 57 ms 56 ms 57 ms vps79.servershost.net [216.246.79.183]
12 61 ms 63 ms 63 ms unknown.hostforweb.com [216.246.2.2]
Trace complete.
 
It almost sounds like they have to restart the router in denver so that it can pick up DC's new address ... But there is no telling when they rest it ... if ever :cry:
 
jaybs02 said:
It almost sounds like they have to restart the router in denver so that it can pick up DC's new address ... But there is no telling when they rest it ... if ever :cry:
Click to expand...
The people that handle this is called ICANN ( Internet corporation of names and numbers ) I contacted them over a week ago and told them what was going on but have not heard from them.

I talked to tech support at EMBARQ and they say they can't do anything.
They keep assuring me that it is not my computer or their system that it is in the internet system.
Tech support is in Pennsylvania and they can access the site OK from their.
 
I still can NOT access the DC.org from home in the morning. I try to log in any where from 5;30-7 am. Sometimes I can get to the home page but once i click anything on the home page, I get can not connect to server, which I beleive I was just on 5 secounds ago. Its find on my folks computer which i am on right now.
 
RANDAL said:
I still can NOT access the DC.org from home in the morning. I try to log in any where from 5;30-7 am. Sometimes I can get to the home page but once i click anything on the home page, I get can not connect to server, which I beleive I was just on 5 secounds ago. Its find on my folks computer which i am on right now.
Click to expand...

sorry to hear Randal , but with a little optimism let's think this will be resolved soon :rockon
 
Bunky said:
I had been considering something like this but not aware of this. My work DNS servers seem to be faster than my local ISP (roadrunner). I have been able to VPN to my work id and surf faster (through roadrunner) than natively than rr.
Click to expand...

Give it a shot. It's very easy and free. If you don't see an improvement, you can change it back in just a few seconds. It has shown an improvement on every one I have tried.
 
You must log in or register to reply here.
Back
Top