Time Warner Cable - Legacy → Re: [TWC] American Express website will not resolve

Typing in the IP address doesn't have any bearing, so it appears to not be a resolution issue, but rather "something else."

I probably won't have time to try the Linux approach tonight, but I did try my Windows Mobile device (T-Mobile dash): When I have it on EDGE, it works great! When I switch over to wi-fi on my network - no amex and no msnbc.

So I'm reasonably confident that it is not a local issue, but I doubt the TWC rep will agree. They'll be sure that rebooting my computer will solve the problem. Does anyone have a L3 tech or engineering contact at TWC who might be able to help? This is clearly breaking down between the node and my apartment, somewhere.

Thanks again everyone for all of your assistance on this - what a mystery!

OK, you also used yet another device with yet another OS version. You also found that a different network (EDGE would be a different network) makes a difference even from your location. Getting off EDGE and then going to Wi-Fi on your own local network at your location puts your Windows Mobile device on the TWC network (and RoadRunner). What is blocking the sites on the TWC network is also blocking them on the T-Mobile device when connected to the same network.

This seems to pin it down exactly to TWC and RoadRunner. You can still try the linux CD for fun if you want, but it probably won't make a difference. The hardware won't be different, just the software.

Now, somehow you have to make TWC listen to the logic of this, unless, of course, the problem disappears overnight.

Mind posting a trace to www.americanexpress.com?

It seems some TWC/RR users have had issues with getting to certain sites from the NYC area due to routing issues with providers upstream of TWC...

»www2.dslreports.com/foru ··· 17966305

Yes, this is most definitely the issue. Thank you for the link; I was pulling my hair out.

My IP starts with 98.

I see that the issue was originally posted on 3/8 - that's quite a while for no resolution!

Any idea how to get a hold of a L3 tech without going through multiple songs and dances with L1 and L2?

Thank you,
Lewis

I was wondering how the tracert might help. Two of us on RR did a tracert to the same sites and got the same failures reported by tracert (see my earlier post of my experiments), yet we were able to connect to ALL those same sites in our browsers in spite of the failure of the tracert. There's no doubt we started from different locations, and it's probable that we just can't see what the problem is, because everything else is working for us. Only the OP seemed to be unable to reach those sites given the same conditions.

Your traces were failing at the server at the end because of server security. The OPs traces should end before the server at the network where the failures are happening.

Because you are in a different location, the trace will take a different path then the OPs. He will see different hops to get to the end server.

It's the difference in the path that is part of the problem. His path is crossing to a network with issues right now, your path is not.

OK, I see that each trace I ran stopped at hop 12, and he had said that his stopped at hop 15.

Also, I forgot that one trace I ran (to home.americanexpress.com) was completed successfully at the 11th hop, which is just before 12. One other trace (msnbc.com) simply timed out on the 12th hop and I manually canceled it after a few more timeouts. The OP did _not_ successfully complete a trace to home.americanexpress.com. I guess that should have been the most significant clue, if there were nothing else.

Obviously, even for me, the trace that successfully completed to home.americanexpress.com must have bypassed something that affected the trace to www.americanexpress.com.

Anyway, as you say, he's in a different location, so we could not really compare what was happening. Plus, I have not used tracert much. I have also seen that many have suggested better versions of tracert than the one with Windows XP. My instinct was that the problem was in his area, and he pretty much eliminated the hardware and software on his systems as affecting things.

For anyone else having the same problem (or just curious) I spoke with a L3 tech and indeed this is a known issue that is frustrating TWC. They have no ETA for a fix, but say it is being worked on at the corporate level. He said they just got a bad block of IP addys and there is no way to re-assign me an IP because the address is tied to the modem's MAC.

He is having me send tracerts, but I am not sure how that will be helpful since they have isolated the problem to a specific block. In any event, I am happy to help.

I guess the good part is that you went through everything carefully and ruled out other causes, leaving only the RoadRunner network as the culprit. Having the support people acknowledge that you were right is worth something.

Yeah, he even offered to swap out my modem, which is a strong sign that they are at their wits end on this problem internally (but no guarantee that would even work because my node could be only spitting out the 98.x addys.)

While this is an annoying problem, I was impressed that I relatively easily reached an L3 who was well-aware of what was going on.

Best,
Lewis