rycanada's endless connection saga
- Thread starter Ry
- Start date
IronWolf
blank
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 www.enworld.org 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.
63-144-217-198.cust.neotechus.com [63.144.217.198]
This is the spot in the traces from remote computers trying to access www.enworld.org 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.
IronWolf
blank
I waited until this morning to send an email to support figuring they wouldn't be watching the address over the weekend. I included lots of traces to help show them where the issue is. I am hoping with the more specific information they can either resolve it or have adequate information to contact their upstream with.
humble minion
Legend
Glad to hear it's working, guys, and thanks to Ironwolf et al for the work they've put into this one. And I hope it stays up - I've been getting the neotech problem on and off since September, often for weeks at a time. It sometimes seems to resolve itself briefly, but it always comes back. Here's hoping you do better than me!
*posting from work again, into the second week of no home enworld access again, wants to feed neotech to the Eyeball Squirrels again...*
*posting from work again, into the second week of no home enworld access again, wants to feed neotech to the Eyeball Squirrels again...*
IronWolf
blank
humble minion said:
From the computer you cannot access www.enworld.org from, can you tell me what your IP is? You can go to http://www.whatismyip.org to tell you.
humble minion
Legend
IronWolf said:
Will do, but it won't be until Monday (since I need to go home to check the IP, and then come in to work to post it here). Thanks again!
Similar Threads
