Or if you're having to use a proxy. Let everyone who can't get on know that since Snorkel doesn't seem to be helping I'm going to e-mail Comcast about the server thing.
Let anyone that can't get on know that I need their IP address, location, and ISP as well as the traceroute of Valentrinne.com sent in an e-mail to
[email protected]To do a traceroute on Windows type "tracert valentrinne.com". On OS X type "traceroute valentrinne.com", both without the quotes.
Let anyone who can't get on know.
Stickied.
You're also going to have to contact Charter, because they've had their fair share of problems too.
You're also going to have to praise Time Warner, because they're not having any problems.
It's actually not Comcast, I discovered... but it's still some common server along the way to the site.
Quote from: Valentrinne on October 28, 2007, 08:55:22 PM
It's actually not Comcast, I discovered... but it's still some common server along the way to the site.
It might be one that comcast, among other ISPs, use.
I still think my theory of a node being taken out by the fires in California works.
Quote from: JMV290 on October 28, 2007, 08:57:44 PM
It might be one that comcast, among other ISPs, use.
I still think my theory of a node being taken out by the fires in California works.
Yeah, it could be some random server at a super-ISP (I'm not joking).
This was happening before the San Diego fires. santa;
Quote from: Valentrinne on October 28, 2007, 09:00:10 PM
Yeah, it could be some random server at a super-ISP (I'm not joking).
This was happening before the San Diego fires. santa;
But not on the level that it's happening now.
Snorkel needs to get the fuck off Half-life and fix the damn site.
Quote from: Geno. on October 28, 2007, 09:56:07 PM
Snorkel needs to get the fuck off Half-life and fix the damn site.
If we find the exact server and manage to figure out who owns it, I can try to contact them. Otherwise there's really nothing I can do. poppy;
Quote from: JMV290 on October 28, 2007, 08:57:44 PM
I still think my theory of a node being taken out by the fires in California works.
what kind of node psyduck;
and why would it affect me
Quote from: JMV290 on October 28, 2007, 08:57:44 PM
It might be one that comcast, among other ISPs, use.
I still think my theory of a node being taken out by the fires in California works.
All cheap hosting servers are located in Taiwan or something. powerofone;
Quote from: Bassir C. on November 01, 2007, 02:09:43 PM
All cheap hosting servers are located in Taiwan or something. powerofone;
But There are servers that connect to other servers.
Our ISP doesn't connect directly to the server. It connects to a server, which connects to another server, which connects to another, and it goes on.
Quote from: Commodore Guff on November 01, 2007, 12:40:37 PM
what kind of node psyduck;
and why would it affect me
Somewhere along the line we might be using a common server to connect to this server.
Quote from: JMV290 on November 01, 2007, 02:34:19 PM
But There are servers that connect to other servers.
Our ISP doesn't connect directly to the server. It connects to a server, which connects to another server, which connects to another, and it goes on.
what servers
Quote from: JMV290 on November 01, 2007, 02:34:19 PM
Somewhere along the line we might be using a common server to connect to this server.
doubtful
Why is it that sometimes I can post without a proxy and other times I need one? psyduck;
Quote from: Commodore Guff on November 01, 2007, 03:48:16 PM
what serversdoubtful
james-valentes-computer:~ jamesvalente$ traceroute valentrinne.com
traceroute to valentrinne.com (69.72.149.25), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 2.053 ms 1.494 ms 1.438 ms
2 c-3-0-ubr03.lynn.ma.boston.comcast.net (73.169.196.1) 8.451 ms 11.364 ms 9.537 ms
3 ge-1-39-ur01.lynn.ma.boston.comcast.net (68.87.153.81) 10.440 ms 10.867 ms 9.093 ms
4 68.87.147.90 (68.87.147.90) 9.240 ms 14.731 ms 9.783 ms
5 te-9-4-ar01.woburn.ma.boston.comcast.net (68.87.144.165) 10.259 ms 10.766 ms 10.706 ms
6 68.86.85.22 (68.86.85.22) 13.651 ms 10.609 ms 10.135 ms
7 comcast-ip-services-llc.tengigabitethernet1-4.ar5.nyc1.gblx.net (64.208.222.58) 17.724 ms 17.936 ms 17.275 ms
8 tengigabitethernet1-4.ar5.nyc1.gblx.net (64.208.222.57) 21.997 ms 19.041 ms 18.389 ms
9 te1-4-10g.ar4.nyc1.gblx.net (67.17.108.245) 17.199 ms 18.522 ms 15.928 ms
10 64.209.110.30 (64.209.110.30) 19.828 ms 19.347 ms 15.074 ms
11 208.116.63.246 (208.116.63.246) 21.790 ms 17.553 ms 31.842 ms
12 pi.fastbighost.com (69.72.149.25) 21.003 ms 17.514 ms 17.206 ms
james-valentes-computer:~ jamesvalente$
Those servers. We don't connect directly to the server of the website. It gets passed along through several servers.
Quote from: NINTENDUDE312 on November 01, 2007, 03:50:13 PM
Why is it that sometimes I can post without a proxy and other times I need one? psyduck;
because your gey
Quote from: JMV290 on November 01, 2007, 03:50:45 PM
Those servers. We don't connect directly to the server of the website. It gets passed along through several servers.
Really? You mean it's like every other server on the internet?
oh and the only hop in common is the destination
Quote from: Commodore Guff on November 01, 2007, 04:20:43 PM
Really? You mean it's like every other server on the internet?
oh and the only hop in common is the destination
Yes. I'm glad you know how how the internets work
Also, you might not share anything other than the destination with me, but other users (Kaz for example) had the same point at the time out. For some reason I'm getting a different IP now, so I think they fixed it.
Okay, well it seems to be fixed. Thread over.