ATT Blocks Nagafen.everquest2.com

[tooloose]

<p>I am a user that has an ATT buisness DSL and Time Warner Cable modem. I have found that ATT blocks certain IP addresses, I can tracert through antoniabayle.everquest2.com but not nagafen.everquest2.com. Nagafen comes back as unresolvable. I cando a full tracert on Time Warner. My guess is that ATT buisness blocks it because its a buisness line, yet I can find no proof or reason in the litterature, customer service is a joke tbh. They really have no clue as to what I mean at the call center in Delhi.</p><p>Anyone have any ideas on this one?</p>

[harleygjc]

<p>I've a similar problem to you, although I'm uk based and using virginmedia as my isp my route to the splitpaw server goes through AT&T to get to it's destination. I've found that I'm getting blocked on a certain part of the route which traces back to AT&T so far had no real help from them soe or my isp! so if you manage to sort this out I'd be intrested to know the answer.</p>

[Wingrider01]

<p><cite>tooloose wrote:</cite></p><blockquote><p>I am a user that has an ATT buisness DSL and Time Warner Cable modem. I have found that ATT blocks certain IP addresses, I can tracert through antoniabayle.everquest2.com but not nagafen.everquest2.com. Nagafen comes back as unresolvable. I cando a full tracert on Time Warner. My guess is that ATT buisness blocks it because its a buisness line, yet I can find no proof or reason in the litterature, customer service is a joke tbh. They really have no clue as to what I mean at the call center in Delhi.</p><p>Anyone have any ideas on this one?</p></blockquote><p>More then likely a DNS resolution issue rather then a full block on, have AT&T at the office and am able to tracert to the server. They are more likely to block at the residential level then at the business level due to the SLA agreement in place.</p><p>you can try a restart of the modem and router then a ipconfig /flushdns on the machine in question and try the tracert again.</p><p>If that fails change the DNS resolvers to either the opendns (<a href="http://www.opendns.com/0ones">http://www.opendns.com/0ones</a> or if I rememebr correctly 4.2.2.1 and 4.2.2.2 to test.</p>

[TSR-DanielH]

<p>Greetings,</p><p>Wingrider has posted some good information and I would try those steps first.  Please keep in mind that many of the nodes on the AT&T network will not respond to tracert/pathpings like other networks.  When tracing a connection through their network you will usually see 100% packet loss but that doesn't always mean that they're blocking the connection.  If the problem persists after trying the steps Wingrider suggested then you'll probably want to post your tracert/pathping results so we can take a look.</p>