IRC channel error ...

[Carol Haynes]

Any idea why I get "Socket Error: 10053 : Connection is aborted due to timeout or other failure (Server)" errors every few minutes on the #donationcoder channel? It leads to a disconnect which basically means it is hard to follow conversations as a lurker ?

I presume it is some sort of time out - but is there some way to extend this?

[app103]

What IRC client are you using, what firewall are you running, and which server are you connecting to?

[Carol Haynes]

Client: IceChat7

Firewall: Agnitum Outpost - behind a Linksys wireless router with a firewall - it seems to get the correct IP address automatically - and seems to work - just disconnects frequently.

Server: efnet.demon.co.uk

[app103]

I could suggest trying a different server...or a different IRC client (there are quite a few free ones)

And check your firewall logs for any kind of blocking related to the IP of the server you connect to.

See if that makes any difference.

[Carol Haynes]

Thanks I'll see how it goes - I am going to have to restore an oldish backup and reinstall a load of stuff as my system went caput yesterday and I spent most of the day offline. Don't quite know what happened - I did a bit of cleaning up (using crap cleaner) and then my system wouldn't restart. For some reason all the permissions seem to have got messed up (on files and in the registry) so that even admin doesn't have access.

I tried running a system repair from the windows disc - and even the installer doesn't appear to have access to replace files!!!

Now I get a load of system erros in my logs about COM+ needing to be resinstalled (amongst loads of other odd errors) but there don't seem to be an MS KB articles on how to fix any of the errors. MS KB can be brilliant but when you actually need help with THEIR error messgaes it is often a complete PITA ...

Hopefull see everone again soon once I have tried to restore the backup (lets hope it still works!).

[f0dder]

Sounds like we should really keep away from those "registry cleanres" 

[mouser]

hurry back carol, we miss you already 

[Carol Haynes]

Sounds like we should really keep away from those "registry cleanres" 

LOL - yep, I keep saying stay away from the registry cleaners ...

Guess what ... I used "Scan for issues" and thought 'well so long as I back up any registry entries I fix it should all be OK' - guess what .... 'I was wrong'. Having 'fixed' the issues present (and backing up the registry) my system never started again and Windows repair didn't work. A lot of use my 'repair' backups were eh?

My advice stands again ... "Don't use registry cleaners" - I have learned my lesson and I won't do it again, at least not without a full disk image backup first.

Luckily my backup was only a wcouple of weeks old so Acronis TrueImage restored my system back to working order, and all my data is stored off the system disc so there wasn't much data to recover before doing a system restore.