Tough network issue

Anonymous · Post by **Anonymous** » Mon Apr 05, 2004 4:51 pm

Here's one I really need help with. Maybe someone will know what to do with this.

I have a dedicated server at managed.com. It runs fine, 100% uptime so far.

I have one client who cannot access the server. The DNS info IS resolving. He cannot get to my server at the datacenter.

I have a system administrator running the box. He is not blocking the IP with the software firewall and there are no bans setup in Cpanel anywhere.

I got him to do a traceroute to the server. The tracert makes about 18 hops, then gets to the switch at the managed.com NOC. The last IP address on the tracert below is the managed.com switch. On a successful tracert, my server would be the next and last IP listed.

6 18 ms 17 ms 18 ms so0-0-0.chcgilL3-rtr1.kc.rr.com [24.94.160.5]
7 18 ms 19 ms 19 ms pop1-chi-P7-0.atdn.net [66.185.136.109]
8 18 ms 17 ms 17 ms bb1-chi-P0-0.atdn.net [66.185.141.84]
9 20 ms 19 ms 19 ms pop2-chi-P0-0.atdn.net [66.185.148.65]
10 20 ms 17 ms 20 ms XO.atdn.net [66.185.132.106]
11 19 ms 19 ms 20 ms p5-0-0.RAR1.Chicago-IL.us.xo.net [65.106.6.133]

12 57 ms 44 ms 43 ms p6-0-0.RAR2.Denver-CO.us.xo.net [65.106.0.25]
13 60 ms 43 ms 52 ms p0-0-0-2.RAR1.Denver-CO.us.xo.net [65.106.1.81]

14 75 ms 74 ms 73 ms p6-0-0.RAR1.SanJose-CA.us.xo.net [65.106.0.21]
15 75 ms 75 ms 91 ms p0-0-0.MAR1.Fremont-CA.us.xo.net [65.106.5.134]

16 75 ms 75 ms 75 ms p0-0.CHR1.Fremont-CA.us.xo.net [207.88.80.178]
17 112 ms 95 ms 66 ms 67.104.60.222.ptr.us.xo.net [67.104.60.222]
18 66 ms 67 ms 66 ms 66.79.175.2
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.

I have been in touch with managed.com's tech support and they claim there are no blocks/bans on IP addresses in that switch.

I got my client to do a tracert to the domain 'managed.com'. That tracert was successful, and goes through the very same switch - 66.79.175.2.

Some more info - my client cannot access the site through the connection at his house, his friend's house, or his mother's house. They are all on RoadRunner cable in Kansas City, MO.

What other steps can I take to determine exactly where this problem is happening? I'm not quite sure how to read the results of the tracert. Does the tracert show that it is getting to the 66.79.175.2 switch getting routed to the next server, and the next server is not responding? Or is it showing that the signal is not getting all the way through the switch?

Any help would be greatly appreciated.

Lonnienlonnie@meanpc.com

Archived topic from Iceteks, old topic ID:2221, old post ID:18739

Red Squirrel · Post by **Red Squirrel** » Mon Apr 05, 2004 5:11 pm

hmmm, do all those computers happen to run some type of anti-riaa software or something? I find allot of major servers get accidentally blocked by those lists. This site's server is one of them. Maybe get the data center to do a traceroute back to the client's IP to see what it gives. It should be clear though but worth a shot, since if not, it means there is somethingin between stopping access, but it looks more like a one way thing, otherwise more people would be affected.

Archived topic from Iceteks, old topic ID:2221, old post ID:18740