Dolphin, the GameCube and Wii emulator - Forums

Full Version: IRC issue.
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I hate EFNet, and I'm still wondering why it was decided to use EFnet, since it doesn't have anything like nickname registrations, etc. No way around it though. In any case, I'm having issues connecting to EFnet.

This is the only server giving me these issues, every other IRC server works perfect. I tried EVERY Efnet server listed on their site too, but it all ends up the same:

It either doesn't connect at all, and just gets 'stuck' (Doesn't even disconnect).

Or it does this:
Quote:[23:35:00] * [10053] Software caused connection abort
-
[23:35:00] * Disconnected
In an endless loop.

I don't have a Firewall running, DNS servers are fine, every other IRC server connects within 2 seconds with no problems.

Does anyone have a clue what's causing this?
Do you have a router or something like that ?

Note that "10053" is a generic WinSock error code

Try this generic solutions

Code:
-disable winxp's firewall

-dont use port 6667 to connect to a network. Most networks have a range of ports, usually within 6660-6669,7000-7001 and you can specify a port with /server some.server.here:7000

-dont use "speed patches" that supposedly increase your download speed. (note some of them effect your registry, use speed patch as your search term)

-update your router drivers/firmware. (some have said they needed to use something other than the ones supplied by the manufacturer)

-connect to the server's ip instead of domain (ie, /server 123.456.789.123 instead of /server some.domain.here)

-limit how many networks or other apps you are running

-some have the prob not while dcc sending, but when idle for long periods of time. try creating a channel and using a timer to make a post every so often.

-changing NIC card

-uninstall MSN IM

-check for patches for everything from windows to the equipment you have.

-ONLY for the advanced user: look into default MTU registry values with relation to the router you use.

-some ppl have reported this happening with scripts that appear to have compatibility issues, so try with a clean copy of mIRC to check
I have a modem only, but it acts as a router as well. The ports are already open.
I already tried disabling the Windows Firewall, and that gave the same results.
Don't have any speed patches or any of the sorts installed.
Not running any strange network apps either, nor am I downloading or uploading or doing anything else that might interfere with the connection.


I read on some other forum that another possible cause could have been the fact that the IRC client is connecting to too many channels at the same time, but I tried it with connecting to EFNet alone too, but it still didn't work.

This is honestly stupid, considering every single IRC Server works fine except for EFNet.
Still having problems with this.

It randomly connects from time to time, but 95% of the time it doesn't work.

Once it's connected it's fine, but the connecting process is pure hell.