Legit Reviews

Hi guys,
Im getting an awful lot of "unable to connect" pages when i try to view or post on the forums... also it is very very slow for me compared to all the other pages i go to!

I dont think its a problem on my end cause the web works fine for me!

Any thoughts?

anyone else having problems?

I have not noticed anything, but like Apop said, anyone else noticing problems?

nope - fine here

Mike

I lied - for some reason I cant post a response to the Nascar post in off-topic...tried 3 times now and it just sits there

i havent noticed anything either

no issues here either!

no probs here

strange... im defo having problems... and its been going on for a few days...

what browser are you using? Might want to clean out your cookies/cache and see if that helps. So far this is the first issue I have been hearing. The forums were updated on Saturday, so if that is when the issues started let me know and we can dig around a bit.

i have the same type of problems on and off. and i know it's not's my browser or my OS b/c i've tried many browsers and this is a fresh install OS.

what it most likely is, a node that certain users are routed through. best way to figure this thing out would be for the forums members affected by this, like me, would be to do a trace route when the problem is happening and the IP address that has a really high ping or not able to connect to type of problem, thats the culprit. then once we find out who admins the node by doing a whois on the IP, send an email to them compainling about the their computers routing problems and tell them several people have complained about this and the admin will usually work on the problem to resolve the issue.

but, it doesn't happen that much to me, so i never made anything out of it. but it does affect me also. so you're not the only one.

TGM

im using Firefox, and it is an intermittent problem with me aswell, for now its working as it should!
The problem is that sometimes i have to refresh a page multiple times to get it to load as it will keep giving me an unable to connect error.

Il do a trace now thats its working and then when it happens next time, il do a trace to the legit forums!

UPDATE: heres my trace now its working fine:

Tracing route to http://forums.legitreviews.com [72.10.44.189]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 15 ms * * 62.241.161.230
3 17 ms 15 ms 30 ms 62.241.161.177
4 15 ms 15 ms 14 ms 213.248.75.57
5 16 ms 15 ms 14 ms 213.248.74.38
6 56 ms 154 ms 51 ms 213.248.100.2
7 157 ms 157 ms 157 ms 67.17.64.45
8 156 ms 306 ms 157 ms 64.215.185.202
9 157 ms 157 ms 156 ms 69.89.64.246
10 158 ms 156 ms 157 ms 69.89.93.2
11 156 ms 155 ms 156 ms 72.10.63.250
12 158 ms 157 ms 157 ms 72.10.44.13
13 157 ms 154 ms 158 ms 72.10.44.189

Trace complete.

Imnot sure how to interpret this correctly, but it seems the second node isnt doing to well or the 8th?

Immortal,
i totally understand your problem, like i have already stated, i have exact same problems, and it's not the browser or my OS or my router or my internet connection. like i have already stated, it's a node that connects us to this website, millions of people connect out of the eastern states thru the chicago node. the nodes are the backbone of the internet, these are what we travel on/through to get to our destination server.

the trace route does no good if you can get to the intended website, how can you see the problem node having routing issues if it's working correctly at the time you ping it?

you must do the ping test while the problem is happening.

TGM

any network experts want to take a guess as to what is going on?

Apoptosis wrote:any network experts want to take a guess as to what is going on?

Not a network expert but it might be related to DNS recursion.
http://www.us-cert.gov/reading_room/DNS ... 033006.pdf

TGM thanx for he reply, to clear some things up, im in the UK thats where im connecting from, also i posted my current working trace route so that when the problem resurfaces again i can post the trace route then so we can contrast and compare them to see where the problem lies!

DNS is NOT the issue!!!
Routing might be an issue, but I seriously doubt it!
If routing was an issue the all IP's in the 72.10.44.* range would have intermittent issues! I could still be a routing issue affecting some ISP's.....Likewise it could be a DNS issue with an ISP but as I said I doubt it!!!

I checked the LR dns details in my companies authoritive dns server(s) and also on a few other very large companies and everything is fine.

hop 8 on that tracert is gblx.net which is a large Co. who have multiple "nodes" -> also they would be only one possible route. If that route was down then the internet would find another!

I'll get some of the real experts in work to have a look, but I seriously doubt it's a IP issue!!!

it's not an IP issue as the IP we're trying to get to is always available unless you are doing some administrating to your site.

it's not the routing from your site to other node routing. it's the people coming in from where ever they are all over the world. it could, and probably is, that my connecting problems and Immortal's connecting probleams are from two different nodes with router issues. the admins that work on the many, many nodes routing people from all over the world from their ISP's to where ever they are requesting to go. is where the randomess of the connection issues come from. i used ot have this problem with another forum website, and i emailed the admin b/c it was horribly bad. i made a thread in that forum ezpressing the same issues as are expressed here about my connection issues. i just thought that there was something wrong with the forum website's server, but i was wrong. i was the only one that appearently was having these issues. so i was instructed on how to fix my connection issues by a very good friend that i had made there and met in real life. he is a network admin for Oricle. so he told me on the phone what to do and by finding the problem node with the intermitant routing issues, then emailing the admin getting the email adress from doing a WHOIS on the problem IP ping, i emailed the admin and then i got an email back stating that he would look at the config logs and next thing i know, the problem went away and i had no issues for the rest of my 2 year stay posting at that forum.

the reason why we see these connection problems in forums, for the majority, is b/c the forums are "sat on" by many people reading or waiting to for a reply from other members or looking for new threads to post in. this is a very long stay comapred to non forum type websites. the average stay at other commercial websites are minutes compare to half hours or hours at visit time at forum type websites.

as for the rerouting that's being spoke of, that's only if there is another backbone routing path for the request to go through. this could very weel mean the main node that;s routing your request and giving you the problem could be the one that;s closest to the members ISP and be the only node they can go through to get out. like i have stated, my only way out to the rest of the net is the chicago node. unless i'm going to a candian or other eastern world websties, then i'm routed through the Detroit node. these are the only two nodes that i am able to be routed through from my end. if either of these nodes go down i'd not be able to get anywhere, which is why they are known as "backbone" routing nodes. it's literally the backbone of the net's structure.

the only thing that a website can do for their members to always have your website available to them is if you had mirrors set up on servers in optimal spots around the world so that there would always be an "east coast" or "west coast" or eastern world or western world mirrors on servers for the member to view. that's just not done much since these problems are noticed by the node admins and fixed within a reasonable time. that's what my friend does all day doing 18 hours shifts a day for 4 days on and 4 days off, everyday for a job. he's the one that get the notification emails from the routing nodes that Orical admins. once he is notified of the routing issue, he then tries to admin the server remotely to fix the data error. if it's a hardware issue, he has network IT personal go out to the node where ever it is with in his area, to replace hardware components and these nodes never shut down, they all have multiple back up hardware systems, like hundreds of SCSI hard drives that are mirrored or back up power supplies and cpu's and ram, and motherboard. these are the huge rack mount systems that we see. these are the routing nodes that a select few companies around the world run for the "backbone" of the net. the smaller servers that websites by space on to host their websites can't control or admin these backbone nodes, only companies like Oricle can service them as they own them.

as a website admin, you could ask your hosting admin to check routing logs out on their servers, but if they find no problems, than there's nothing else you can do. then it's up to the person either waiting for the problem goes away, or being proactive and pinging all the routing nodes that they go through to get to this website and find the problem routing node and email them and ask them to look for a problem as not all routing nodes are run my such big compaines as Oricle. there are many "local" routing nodes that you are routed though off the backbone routing nodes to get ot the local server where this website is hosted.

TGM

When I said IP issue is mean internet protocol! not IP address!!!!

I work for a large ISP and deal with this stuff all the time.......
I've opened a ticket with our NOC this morning to get some of the real experts to look @ it....but it's low priority!!!

Immortal --> can't you post some trace routes here....I'll need some from your pc when it's NOT working.

Kenc, like i said when it stops working again it will be the first thing i do, for now it seems to be behaving itself and working...

ok guys.. id like to say the problem resurfaced this morning and is happening NOW as im typing, tere are periods when it works and then periods where it absolutley refuses to...ive got a tracert of it in action so il post that when its done.

Ok guys, ive got two tracerts so far and a third in progress jus to check it for sure:

Tracing route to http://forums.legitreviews.com [72.10.44.18
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 49 ms 375 ms 388 ms 62.241.161.230
3 221 ms 78 ms 27 ms 62.241.161.177
4 14 ms 14 ms 18 ms 213.248.75.57
5 233 ms 154 ms 119 ms 213.248.74.38
6 301 ms 195 ms 76 ms 213.248.100.2
7 684 ms 161 ms 202 ms 67.17.73.42
8 220 ms 310 ms 216 ms 64.215.185.202
9 162 ms 397 ms 386 ms 69.89.64.246
10 285 ms 287 ms 207 ms 69.89.93.2
11 212 ms 168 ms 160 ms 72.10.63.250
12 166 ms 209 ms 191 ms 72.10.44.13
13 * * * Request timed out.
14 156 ms 160 ms 188 ms 72.10.44.189

Trace complete.


Trace2:

Tracing route to http://forums.legitreviews.com [72.10.44.18
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 49 ms 375 ms 388 ms 62.241.161.230
3 221 ms 78 ms 27 ms 62.241.161.177
4 14 ms 14 ms 18 ms 213.248.75.57
5 233 ms 154 ms 119 ms 213.248.74.38
6 301 ms 195 ms 76 ms 213.248.100.2
7 684 ms 161 ms 202 ms 67.17.73.42
8 220 ms 310 ms 216 ms 64.215.185.202
9 162 ms 397 ms 386 ms 69.89.64.246
10 285 ms 287 ms 207 ms 69.89.93.2
11 212 ms 168 ms 160 ms 72.10.63.250
12 166 ms 209 ms 191 ms 72.10.44.13
13 * * * Request timed out.
14 156 ms 160 ms 188 ms 72.10.44.189

Trace complete.


Notice anything strange... Node 13 times out on both occasions.... and thats the final node when its working properly...

UPDATE: Ok, im pretty sure its node 13, cause ive just done another 2 tracerts.
During the ever so short period it was working normally, node 13 responded properly and i got a proper 13 hop route:

Tracing route to http://forums.legitreviews.com [72.10.44.189]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 16 ms 15 ms 19 ms 62.241.161.230
3 149 ms 106 ms 102 ms 62.241.161.177
4 101 ms 63 ms 65 ms 213.248.75.57
5 41 ms 20 ms 23 ms 213.248.74.38
6 27 ms 17 ms 23 ms 213.248.100.2
7 308 ms 444 ms 435 ms 67.17.73.42
8 287 ms 246 ms 270 ms 64.215.185.202
9 203 ms 267 ms 186 ms 69.89.64.246
10 218 ms 205 ms 1171 ms 69.89.93.2
11 354 ms 377 ms 464 ms 72.10.63.250
12 269 ms 276 ms 215 ms 72.10.44.13
13 223 ms 239 ms 262 ms 72.10.44.189

Now what is interesting is i managed to get the next tracert to finish on the point where it suddenley started working again, take a look at this:

Tracing route to http://forums.legitreviews.com [72.10.44.189]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 108 ms 127 ms 52 ms 62.241.161.230
3 26 ms 19 ms 16 ms 62.241.161.177
4 151 ms 195 ms 115 ms 213.248.75.57
5 59 ms 77 ms 95 ms 213.248.74.38
6 29 ms 75 ms 42 ms 213.248.100.2
7 194 ms 1200 ms 306 ms 67.17.73.42
8 350 ms 362 ms 451 ms 64.215.185.202
9 1218 ms 494 ms 387 ms 69.89.64.246
10 280 ms 157 ms 265 ms 69.89.93.2
11 246 ms 243 ms 345 ms 72.10.63.250
12 1217 ms 317 ms 242 ms 72.10.44.13
13 * * 267 ms 72.10.44.189

Trace complete.

As you can see, the first two attempts at node 13 fail, but when it started working again it responded. I say it started working because the second it finished that trace, my page loaded when it had been stuck for 30 odd seconds.