COMODO Firewall + mIRC


Occasionally, I am disconnected from mIRC and/or lose file transfer connections. Also, I’m not sure if my file transfer speeds are as fast as they could be.

Edit: Btw, these problems occur on my desktop which isn’t running COMODO Firewall at all. My desktop is using Windows XP Firewall. Even adding mIRC to exclusions didn’t seem to make a difference. I haven’t used mIRC with COMODO Firewall yet.

I’d like to see if the above tutorial helps at all but I have a few questions.

  • Configuring mIRC
  1. The guide says, I can use a single port or as many as ten ports for downloading/uploading. mIRC defines ports 1024-5000 by default. Should I change it so mIRC only defines 10 ports? If so, what ports should I use?

  2. The guide says, if I am behind a router, I must check ‘Binds sockets to IP address’ and in the box type my router’s external IP address. Is my router’s external IP address the same IP displayed on websites such as ‘’? If not, how do I figure it out?

  • Configuring COMODO Firewall
  1. The guide tells me to use my computer’s internal IP address for ‘Remote IP’. If the IP address displayed on websites such as ‘’ is my router’s external IP address then how do I figure out my computer’s internal IP address?

  2. It sounds like the rule for TCP/UDP protocol should be placed in Global Rules. Is this correct?

Dont panic :smiley:
Its not important what “those” guides will tell you what you have to do first. Opening ports and such things. Not necessary. Only do what is necessary in your cases.

Install a firewall, make the settings of function. Then start programs and answer the questions one time. All will work, relatively sure.

Press, stealth port wizard, choose setting 3. And you dont get questions about traffic attempts which you dont need to answer. It creates a little set in global rules.

Read the manual too. And look calm :slight_smile:

mirc will work, as nearly every thing, with a rule in application rules:
Allow (that program) OUTgoing tcp+udp.
You dont need to open ports, or allowing ingoing.
I guess, if a file transfer is about to start, maybe you get asked a question. If you temporary allow it, you are protected in unwanted cases.

So, I just need to add the following application rule for mIRC:

Allow TCP Or UDP Out From MAC Any To MAC Any Where Source Port Is Any And Destination Port Is Any

Is this correct?

This rule would allow any attempts of the program to connect to the internet, and to update. It covers 99% of the programs out there (its rather unspecific but safe enough). If you want more specific rules, for any reason, just keep in mind: You dont need to allow ingoing traffic for something to work (apart from running a server, or p2p).
You could be more specific for example about ports or addresses, if they are not countless for a given program :wink:
As long as your program and computer is safe, an OUTgoing rule structure is the easiest way which provide a good security.
If you use a program that connects to a few addresses, and uses the same port allways, its a good idea to create a rule based on this needs for this program.

CAUTION: If any program is malicious, or if its replaced by something else, an OUTgoing rule like that isnt safe anymore!

Now, lets say, you used stealth port wizard setting 3, and so you dont get questions about unrequested ingoing traffic (what is desireable), and your mirc is allowed by an OUTgoing only rule, … when your friend wants to send you a FILE, you get a question for an INgoing attempt though. Because this INgoing attempt is in a way requested, but not allowed yet (you use mirc, and you accept a data transfer). Answer those questions temporary with allow.
AVOID to create permanent rules to allow ingoing traffic. Rule of thumb.
NEVER use a rather unspecific rule like that for ingoing traffic!

Rules are read related to their position in the list. From top to bottom. So dont allow something on top, what you want to block on bottom. It will be not blocked!

So, if I allowed incoming traffic for mIRC, it wouldn’t affect file transfer speeds? I had a feeling it wouldn’t but I wanted to make sure. I’m using Windows XP Firewall on my desktop and I add mIRC to exclusions. It didn’t seem to affect my file transfer speeds at all.

You have the windows firewall together with comodo? Choose only one at a time. Comodo is a two way firewall. It can protect you from leaking. Windows firewall allows outgoing rather per default.

You mean, if you allow specific ingoing requests if you get a file transfer from your friend? I hope i made it clear, that you dont need to create ingoing rules PRIOR without a reason.
You dont need ingoing rules AND you dont need to put something in “exclusions” to have no slow down.
The firewall setting is important to protect you. It doesnt need a setting to avoid slow downs. As there are no slow downs.

I want to make sure that you didnt misunderstand something. Thats why i may repeated some things.

Okay, cool.

I thought I may have needed to setup rules for mIRC like I needed to for uTorrent in order for mIRC to function correctly. That’s why I went looking for a guide. I found a guide but some of the instructions weren’t clear to me and that’s what led to me creating this topic. If I understand correctly, none of this is necessary for mIRC to function correctly (including file transfers).


Edit: I’m not using Windows Firewall with COMODO Firewall. Windows Firewall is used on my desktop and COMODO Firewall is used on my laptop.

A last basic thought to get it clear:
“Do i want other people to connect to my computer without my consent?”

For all cases where you would answer with “No”, 99,9% :smiley: , you dont need an ingoing rule, and you should block these attempts. (Stealth port setting 3).

For all cases where you would answer with “Only this time/ this case”, you make very specific rules, or you allow it temporary (p2p, or mirc filetransfer from friend).

“For all cases where you would answer with “Only this time/ this case”, you make very specific rules, or you allow it temporary (p2p, or mirc filetransfer from friend).”

Now I’m confused. So, I should create specific rules to allow incoming traffic for mIRC if I want to file share? That is what the guide is for, isn’t it?

if you’re sharing files via DCC you’ll need to create rules to allow the inbound connections. Depending on your configuration, you may need to create Global rules, in addition to the Applications rules for MIRC. Also, depending on the IRC servers you use, you may need to allow IDENT (TCP port 113) inbound.

I see. Then I should try following the instructions provided by the guide I had originally linked to, yes? It’s a pretty old guide but so is the uTorrent guide I followed and that worked well. Can you help me with my original questions so I can properly set it up?

Would you post a screenshot of your Firewall Global rules first, it’ll help deciding what’s needed.

Sure can. It’s attached.

Edit: I thought your name looked familiar. The uTorrent tutorial I used was one you posted on another thread. It actually isn’t that old. I was thinking of the tutorial I was originally going to use.

[attachment deleted by admin]

Assuming you’re not setting up a specialised DCC/Fserve bot, you can use the utorrent tutorial as a template. Basically, create a Global rule that allows TCP/UDP In to your DCC port range - the default is 1024-5000 - then add an inbound application rule for MIRC to do the same.

With regard to IDENT, some IRC servers will bounce you if you don’t allow IDENT, so I’d suggest trying to connect and see what happens. You’ll see the server response as you try to connect. if it fails on IDENT, add a Global/Application rule to allow TCP In on port 113

The rule should look like this, right?

Allow TCP Or UDP In From MAC Any To MAC Any Where Source Port Is Any And Destination Port Is In [1024-5000]

Why do I have to create a Global Rule if the rule is already an Application Rule? Global Rule allows this for all applications, right? Shouldn’t I only want this rule for mIRC?

If I have to allow IDENT, the rule should look like this, right?

Allow TCP In From MAC Any To MAC Any Where Source Port Is Any And Destination Port Is 113

Correct. :slight_smile:

Why do I have to create a Global Rule if the rule is already an Application Rule? Global Rule allows this for all applications, right? Shouldn't I only want this rule for mIRC?

The reason you need this, is the same reason you have the Global torrent rule, the last item in you Global list blocks all unsolicited inbound connections. Without these explicit allow rules, the application would never see the inbound requests.

Remember, when you allow connections through Global rules, only an application listening on those ports will respond. That said, if you wish to make the port window smaller, choose a smaller number of ports in MIRC.

If I have to allow IDENT, the rule should look like this, right?

Allow TCP In From MAC Any To MAC Any Where Source Port Is Any And Destination Port Is 113

Correct. :slight_smile:

So… If I understand correctly, Global Rules take precedence over Application Rules so we have to add the Global Rule?

You only need a Global rule for applications requiring server rights and then only if you have a block rule that denies all unsolicited inbound connections. If you were to remove the final rule in your Global list, you wouldn’t need to allow these connections, other than with Application rules, but then you’d loose some control over unwanted traffic that can create a lot of junk entries in your logs. One consideration, if you’re behind a router with a decent firewall, you can probably dispense with Global rules, as the router is doing that job already.

Take a look at:
Application Rules
Global Rules

Okay, thanks. I’ve added the rules.

Just to explain what i had in mind :wink: :
I keep my programs in a state, where they can connect to the internet, and where they can receive requested packets.
If someone wants to send me a file, and the program would require ingoing traffic beyond the “outgoing only” structure (example msn; but not skype which can do it with only an outgoing rule at all), i would just allow it per case. As it isnt regularly happening here.
Thats why i said: Allow it temporary.
And if its for you regularly happening, and you dont want to answer that questions, i mentioned: Make very specific rules for that case.

Maybe language lead to confusions.

Sidenote: Its very usefull that we get a question about ingoing filetransfer attempts which are initiated in a chat of a program that got outgoing only permission, while having also a global rule which blocks unrequested ingoing traffic attempts in the same time. Otherwise we would have to make exceptions in global rules. Thats a smart aspect of this firewall.