Reply to thread

Message

<blockquote data-quote="IronWolf" data-source="post: 3519446" data-attributes="member: 21076">I did some more looking this evening.&nbsp; The problem area does appear to be:63-144-217-198.cust.neotechus.com [63.144.217.198]This is the spot in the traces from remote computers trying to access <a href="http://www.enworld.org" target="_blank">www.enworld.org</a> that varies depending on which style trace we run.&nbsp; I have worked mainly off the traces rycanada has provided me.&nbsp; I was able to get access to a computer that could trace a path through Qwest's network similar to rycanada's does.&nbsp; That computer has no issues access enworld.org.&nbsp; I can run both ICMP and UDP traces from that computer and they both succeed.&nbsp; In rycanada's case the ICMP ones work, but the UDP ones do not.&nbsp; That more or less points that *something* on that segment is configured differently for certain IP ranges out there.It's the weekend now, so support is apt not to be staffed save for emergencies.&nbsp; I plan on contacting Cyberstreet once again with this additional information.&nbsp; I am hoping either the more specific information will be enough to give them something to look at on their end or pass along to their upstream provider.&nbsp; We'll see where that takes us.</blockquote>

[QUOTE="IronWolf, post: 3519446, member: 21076"] I did some more looking this evening. The problem area does appear to be: 63-144-217-198.cust.neotechus.com [63.144.217.198] This is the spot in the traces from remote computers trying to access [url]www.enworld.org[/url] that varies depending on which style trace we run. I have worked mainly off the traces rycanada has provided me. I was able to get access to a computer that could trace a path through Qwest's network similar to rycanada's does. That computer has no issues access enworld.org. I can run both ICMP and UDP traces from that computer and they both succeed. In rycanada's case the ICMP ones work, but the UDP ones do not. That more or less points that *something* on that segment is configured differently for certain IP ranges out there. It's the weekend now, so support is apt not to be staffed save for emergencies. I plan on contacting Cyberstreet once again with this additional information. I am hoping either the more specific information will be enough to give them something to look at on their end or pass along to their upstream provider. We'll see where that takes us. [/QUOTE]

Verification