There are many problems you are likely to come across on IRC, we can't possibly
cover them all here. However, we can try and cover some of the most common ones
that you are almost definitely going to experience at some point, or even be asked
by someone else how to resolve!
DCC Rejected (file type ignored)
This message may occur when you try and get a file from a friend. All you need to
do to resolve this issue is type /dcc ignore off. By default this ignore feature
will turn itself back on again after 3 minutes. You can change your DCC ignore options
in ALT+O > DCC > Ignore.
Note: Networks such as DALnet have a DCCALLOW feature in their IRCd. This
is not an mIRC feature, but to add someone to your DCCALLOW list use /dccallow +nickname.
For further help try /dccallow help or ask in the network's #help channel.
[10053] Software Caused Connection Abort
Possibly one of the most common connection errors you'll see whilst using IRC. This
is a Winsock error and cannot be prevented most of the time. There are a huge number
of ideas/tips to prevent this error message in this forum post.
For convenience purposes here are some of the general tips in that forum listed here:
Disable winxp's firewall.
Don't 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.
Don't 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 (i.e., /server 123.456.789.123 instead of /server some.domain.here).
Limit how many networks or other apps you are running.
Some have the problem 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 people have reported this happening with scripts that appear to have compatibility issues, so try with a clean copy of mIRC to check.
Infected with a Trojan
If you are being banned from a server, network or channel for being infected with
a virus/worm or trojan then there is only one method to sort yourself out - run 2-3
good virus/trojan scanners and clean your system, then wait 24-72+ (1-3+) days for your
ban to expire. Normally a ban wouldn't last longer than 3 days, but it might. If your ban isn't
lifted then you're going to need to contact the network administration or, in the case of a channel ban,
the channel ops.
For a huge number of resources check out this forum thread.
Also take note of the tips there to keep safe in the future.
Reconnecting too fast - Throttled
If you try and reconnect to a server too many times then the server will 'throttle' you.
The number of times you can reconnect changes depending on what the Server Administrator
has set the time limit to. Each time you get throttled, you get throttled for a little bit
longer. If you have been throttled, then wait 5 or so minutes before reconnecting or try another
server. There is nothing you can do to get around the throttle, and there's no point
in evading it anyway.
IdentD
There are lots of issues you can find with IdentD. Some networks such as DALnet, will
automatically ban you if you don't have Ident instaled and you're with a certain ISP.
The reason for this is spam bots and 'zombies' - these usually do not have ident installed, so
to help keep them off the network the most abused ISPs are put on a sort of "ident check". Any
user connecting from those ISPs that doesn't respond to an Ident request will be banned.
To enable IdentD the most simple method is typing /IdentD ON. For a lot of systems
however, this won't be enough. IdentD needs port 113 to work. Firewalls block ports.
Firewalls, a lot of the time, block 113, therefore preventing from IdentD working.
You will need to look at your firewalls help files to get this working, look for "port forwarding".
The same principal can be said for routers, you need to forward the correct ports.
Also, DCC applies here. Not being able to DCC send often means that you have the necessary ports
blocked due to a firewall or router.
If you use Windows XP then it's highly likely you have the Windows XP Personal Firewall
enabled. To learn how to set it up to work with DCC/IdentD see http://toidyman.net/xp-dcc.
For further help with enabling identd and other problems you may experience, see this thread.
For further help with problems you may have sending files with DCC, see this thread.
Do note that the DCC port options in 6.14 and above appear in ALT+O > Connect > Options > [Advanced...].
DCC Receive
As I pretty much covered DCC sending above I thought I might aswell cover problems you might
have receiving files. Do be aware that most of the time you won't have trouble receiving and it
will be because the sender has an issue that you can't receive a file from someone. Sometimes
problems do occur on your end however, some of which are covered below:
DCC Ignore - See above for details
Wrong IP - Try typing /localinfo -u. Also tell the person sending to you
to type this and then retry sending. Your Local Info options are available in ALT+O > Connect > Local Info.
Locked - Check that DCC has not been locked in mIRC options. Go to ALT+O > Other > Lock and
check your settings there. You will need to unlock with the password to change the settings. Make
sure the 'Get' box has not been checked. If you find that this area is locked but you
have forgotten the password you set, check out this page.
Could not find firewall address
If you are receiving this error it's because you've filled out incorrect Firewall
details in mIRC options, or you've done it unintentionally. Simply type /firewall off
and this problem should stop. You can find Firewall options in ALT+O > Connect > Firewall.
Suppoer should be set to 'None'.
99% of mIRC users do not need to use this even if you have a firewall on your system!
Can't find the Linux version of mIRC?
Sorry, but mIRC is ONLY available on Windows. The 32-bit version is the only flavour in
current development. The last 16-bit version is 5.91 and you can find it (along with the
latest version) on this page.
There is unlikely ever to be a Linux/Mac/Etc. version of mIRC. You can, however, run mIRC under Linux using WINE. See this page.
(address is banned)
mIRC is just an IRC client. If you have been banned from a channel then there is nothing
the mIRC creator can do, nor is there anything anyone else can do except for the channel ops.
Therefore, if you have been banned from a channel then you will need to speak to the ops of the channel
to get unbanned. The best thing to do would be to wait for the ban to expire - most bans
don't last longer than 24-48 hours (1-2 days).
To message an op type /msg nickname msgHERE. You can open a new message window (query window)
with an op by using /query nickname msgHERE. You might want to check if their idle
first or away, use /whois nickname nickname.
These same principals apply to bans from servers and networks. To be unbanned you need
to contact the network administration. You might check out the network's website. If you don't
know the networks website then search Google.
