Club Arnage - access problems?

[Rich - Team Gulp Racing]

I've just managed to gain access to the CA forum (in fact any URL with the words clubarnage in) since being 'locked out' for about two weeks. It seems my browser or firewall or something just didn't like Club Arnage (kept getting access error messages - but ONLY for Club Arnage).

I tried checking my firewall and found nothing - then googled < Club Arnage Firewall > and the results are really quite worrying - now I'm no boffin but lots of sites have the words 'club' and 'arnage' alongside lots of other scary virussy and scammy looking stuff.

Anyone else had problems?

[smokie]

Well yours is the first complaint I've had...and others have been posting - so I guess it's at your end!

I did the Google, intersting how prominent RS2 Babe is innit! Otherwise it looks just weird - but probably nothing to worry about.

Glad you've found your way back anyway! 

[Ferrari Spider]

YEP, I've had this a few times, reported to Smokie, with the same response.  So its not new, it does happen and its not funny.  no rhyme or reason just nothing, the first time it was a couple of days the last was for a few weeks.  Didn't matter if i tried IE, Firefox or Netscape.

anguished of Southampton

[Robspot]

Peter, do you need a hug 

[Ferrari Spider]

Peter, do you need a hug 

only if you have my big eye   now get back onto topic

[smokie]

Maybe you are using the same ISP?

[rcutler]

Maybe you are using the same ISP?

JP had a problem accessing the site the other night while i was on the phone to him I was able to access the site. I would recon that it is an ISP issue.

[smokie]

It'd be handy if people could note the exact error they are seeing when reporting it.

ISPs do quite frequently have prtoblems with their DNS routing tables, so an IE Explorer Cannot Find Page message (even when other pages are OK) is likely to be a problem somewhere other than the CA server host.

If you open a DOS window (run CMD) and type tracert www.clubarnage.com then you will see the route it is taking to reach the web site. If it doesn't even recognise www.clubarnage.com ("Unable to resolve target system" then the problem is in your ISP DNS routing tables.

If it starts the trace but never reaches the destination, then the problem is with one of the relays along the way. My route to www.clubarnage.com currently involves 19 hops so there is plenty of scope for one being at fault. Eventually routing tables may be automatically updated to bypass a failed hop but this may not happen for a long long time.

Or it may not be a completely failed hop. The step may simply be very very slow, but your browser times out before a response is recieved. (I believe in Firefox there is a parameter you can configure to adjust the timeout - but the reason that the timeout is there is to prevent you waitig too long for updates, so really changing it isn't worth it - you would get v slow browsing)

And just so y'all know, us mods do not have any sight of or control over the servers. All we can see is the forum, plus an admin area - but this is solely forum admin, not server admin. Any problems outside the forum have to be referred to de management...

[Lawnmower Man]

Actualy Smokie,  There are some pretty serious erros in the clubarnage.com DNS.   

http://www.dnsreport.com/tools/dnsreport.ch?domain=clubarnarge.com
will show you all the problems.

Regards,
T.

[Ferrari Spider]

Actualy Smokie,  There are some pretty serious erros in the clubarnage.com DNS.   

http://www.dnsreport.com/tools/dnsreport.ch?domain=clubarnarge.com
will show you all the problems.

Regards,
T.

Tom, thanks for that, well Smokie that makes it a lot clearer for all of us, I think   Looks like its over to you computer geeks to sort, Mr I and myself we'll carry on discussing our blowin' and suckin'   Let us known when you've fixed it all

[Jay (Team Cannonball)]

I have the same problem from my work PC (i.e the uni network) I can access CA from home, but have been locked out from my uni PC for a few months now. Strangely enough it is only my PC, my colleague can access CA. I originally though may'be smokie or steve had banned my IP address because it could have launched a spam attack since I'm part of a very large network. I'm no expert but I don't think this is an isolated problem.

[LangTall]

Actualy Smokie,  There are some pretty serious erros in the clubarnage.com DNS.   

http://www.dnsreport.com/tools/dnsreport.ch?domain=clubarnarge.com
will show you all the problems.

Regards,
T.

You're absolutely right, but I'm not sure whether Smokie is able to resolve these errors, as you need access to the hosting account to set those DNS records. (And then it is still a pain to figure out what to set, had the same issue at work) But Smokester can answer that for himself I guess.

Some ISP's will block content from sites where certain DNS records aren't correct, so it would explain some of the problems some members are suffering from.

[Ferrari Spider]

what's the point of having high end geeks attached to this website if they can't fix the blessed thing

[Lawnmower Man]

You're absolutely right, but I'm not sure whether Smokie is able to resolve these errors,

You're quite right Lang Tall, Smokie is only a moderator.    Grand Fomage needs to talk to the hosting people really.

t.

[Rich - Team Gulp Racing]

It'd be handy if people could note the exact error they are seeing when reporting it.

Smokie,

I'm not sure if it will help much but the attached screengrab is the error message I was getting in Firefox when either;

- trying to access the forum directly from my bookmark
- trying to access any other club arnage thread found by google

This error message would appear literally immediately on screen - it wasn't timing out, it didn't have a chance to.  As I said, not sure how much help this is as it seems to be the generic Firefox error message - can't load site / badly typed URL / etc.

When I tried to access the www.clubarnage.com home page I would get a glimpse of the page for a micro-second, then replaced with a blank window with the above error message.

It was as though my ISP was recognizing  a 'bad site' and immediately blocking it from loading up.
Anyway, glad to be back here again.