Since this site was updated I always get this message when I try to go on it at home. It works OK if I’m at work, but I’m so busy right now I don’t have the time when I’m there.
I’m thinking of pointing my finger at the router for this. Does anyone have any ideas?

Could be the router. Rebooting the router might fix it, ditto resetting it to “factory defaults”. If your router is separate from your modem (pretty much always the case if you have a cable connection rather than ADSL over a ‘phone line) then you could try connecting the PC directly to the modem - that would eliminate the router as the cause, or prove that it is the cause.

Could also be anything else which sits between you and The Area - think Firewalls, Anti Virus etc. Also your browser could be be cause, especially if you have lots of “addons” like ad blockers, script blockers, cookie blockers and so on.

Finally, it could be the Area itself - misconfiguration of the webserver providing the site - it’s unlikely to be the site software as most “forum software” doesn’t deal with data transmission at a low enough level. Thing is, if it was the webserver I would imagine everyone would have the same problems, which we clearly don’t (and neither do you, at work). One point to note is that the IP address for the Area has changed - maybe the DNS servers you’re using haven’t updated properly and you’re being directed to the wrong place (not likely, but worth a mention).

Max 4.2 through 2013.
XP-64 (SP2)
NVidia 9800GTX-512 (Driver 266.58).
Core 2 Quad Q6600 2.4GHz, 8Gb Ram, DX9.0c.

Cheers Steve, I’ll look into it. When I tried Googling the error I couldn’t make much sense out of what I found, apart from the mention of security software causing it, so that’s something else to look at.

Using Firefox instead of IE has solved it.
On Monday afternoon I had the same error on my work computer (with IE7), but the next day it was OK.
At home it still doesn’t work with IE8.
Anyone else seen this error? If you do, you are probably not reading this…

Samab,

I remember seeing this error once some time ago, but it seems fine on both IE8 and Firefox. I don’t use IE unless I have to.

E. K. Anna Hennequet [FA]