Proxies and Firewalls.

Latest News
Download mIRC
How to Install
Message Boards

Intro to IRC

Intro to mIRC
Command List

How to Register

Mailing Lists
IRC Networks
Chat Links
More Info

0.0. Introduction

This is a help file on the use of mIRC behind firewalls and proxies. Your firewall or proxy has to be SOCKS compliant. Alternatively you can connect to IRC through a HTTP or HTTPS proxy.

We hope, with your help, this info will grow into a usefull resource for all users behind proxies and firewalls. Please provide me with additional info and solutions on the firewall and/or proxy you use, regarding the use of mIRC and the use of DCC?!

You can help a lot by simply sharing the settings that proofed to be succesfull for you. State clearly what mIRC version you use and what proxy or firewall you have. Also of value is any information on setups, proxies and firewalls that do -not- seem to work.

This file is not ment to provide you with information on how to pass by proxies and firewalls raised by parents or companies for example, to keep you -away- from IRC. Especially firewalls are often used to keep your place safe and free of intruders and virusses. If your companies policies directly or indirectly forbid the use of IRC then please respect these rules?

This file is permanently under construction. In the end of the file you'll see lots of unstructured comments and snippets that need to be re-written or deleted. You might find something usefull in there but read it with care! Feel free to send additional and/or better info for this file!! Thanks a lot to all who contributed to this information!

1.0. What is a Proxy?

In the context of this file a proxy is a central machine (P) in a small network that allows other machines (A, B and C) in that network to use a shared Internet connection. The software on the central machine is called proxy software. The proxy is also called 'server' or 'gateway'. Most proxy software works perfectly for browsing the Web, sending files with FTP and sending E-mail. Normally proxy software does not understand IRC connections or DCC File transfers by default. Very often this is easily fixed!

Lots of companies use proxies to allow multiple machines access to the Web. There are a lot of proxies (and programs alike) that you can use _yourself_ in a small network to give all your computers access to the Net through one modem, cable of (A)DSL line. Examples of proxies are the Internet Connection Sharing (ICS - built in in Windows), and programs like Winproxy and Wingate.

More information:

1.1. What is a Firewall?

A firewall is not that different from a proxy. A firewall again offers Internet access to lots of other computers on a network but is mostly deployed to provide safety or security; control over the information going in and out the network. Firewalls are used in business environments, at schools, universities and the like. Please keep in mind that most proxies and firewalls in use in business situations are there for a reason; to protect your work environment from the evil Internet. If your companies policy is to block IRC then stick to the rules, ok?

1.2. What is a HTTP or HTTPS Proxy?

Do not mix up the proxies (sharing your Internet Conection) we're talking about in most of this file, with a (caching) web proxy as lots of companies use to speed up your surfing over the web with your web browser. Only recently mIRC 5.81 introduced an option you can use to connect to IRC through a HTTP Proxy. In this case mIRC uses a smart method to open a persistent connection to such a HTTP Proxy and from there to the IRC server.

2.0. IRC

Our goal of course is to get IRC through your proxy (or firewall) working. But lets first look at a normal situation where no proxies or firewalls are used at all;

		IRC Server ports 6660-6669
		# Internet #
		Internet Provider
		PC you are using
		IRC Client port 6668 

You have mIRC (your IRC Client) installed on your PC. You have a connection to the Internet by your Internet Provider. When you start your IRC session you try to connect to some IRC server on the Net. You connect to one of its open ports (by default 6667). IRC Servers usually have open ports in the range 6660-6669. mIRC by default randomly selects one of the ports defined in the servers' settings in the /File/Connect/ menu. As long as your IRC session continues all communication between the IRC server and the IRC client on your PC will use this port.

2.1. DCC and IdentD

The use of IRC includes the use of Ident services and DCC. mIRC has a built in IdentD or Ident server. This server listens on port 113 for Ident requests from the IRC server. The server uses this rather old fashioned system (they really should ditch it!) to confirm your identity. The server will ask mIRC, on port 113, to confirm the identity of the user (you). Of course mIRC will say 'Yup, that is okay - let him in!', replying with the system you use (UNIX) and your user ID (username, the first part of your email address).

DCC is used for file transfers and private chats between IRC users. By default DCC sessions use random port numbers above 1024, up to 5000.

As you see apart from the server ports (6660-6669) also ports 113 and a random range above 1024 are needed for your full IRC experience!

3.0. IRC through a proxy or firewall.

As stated above a proxy is a central machine (P) in a small network that allows other machines (A and B) in that network to use a shared Internet connection.

		IRC Server ports 6660-6669
		# Internet #
		Internet Provider
		P - Proxy Server in your network ---------------
			|			|			|
			|			|			C (PC)
			|			B (PC)		*
			|			*			
			A (PC)	IRC Client port 6668 
		IRC Client port 6667

As you see the main difference is the proxy in your network. The Proxy server (P) is connected to the Internet (either by modem, DSL, ADSL or cable) and, by a small network to one or more computers (clients) A, B, C,.... The proxy distributes all Internet traffic over the PC's connected to it.

Our goal is to get IRC working from those computers behind the Proxy. The proxy has to allow your IRC traffic to go to the Internet and to send the proper information back to the proper PC. Normally you have a network setup something like this;

	Server P 	the machine running the proxy connecting to the internet
			IP subnet mask

	Client A	IP subnet mask
	Client B	IP subnet mask
	Client C	......

Alternative setups (like with ICS) use other IP Addresses like the 192.168.0.X range. What range you use doesnt really matter.

I assume you have installed the proxy software on the machine connected to the Internet. I really can not help you with this standard setup. Most settings will be done automagically. You might have to fill in some general information like your Internet Providers primary DNS. You should already know most of this info. Look for it in the manual of your Internet Provider. If you get stuck somewhere read the proxy's helpfile and website!

Test the behaviour of your proxy by browsing the web from (one of) the client machine(s). Hey, give mIRC a try, maybe it already works! Surfing the Web and sending E-mail should all work perfectly from all your machines. As long as this is not the case it makes no sense to work on your IRC access. From the server (the machine with the Internet connection) you use of IRC should -always- work. This machine is not bothered by your proxy setup or proxy related problems. If you install mIRC on this machine it should work perfectly, including DCC and Ident thingies. As long as this is not the case it makes no sense to work on your IRC access from the other machines (the clients A, B and C).

3.1. Proxy server setup (machine P) for the use of IRC.

As you know already, the connection between the IRC client (mIRC) and the IRC server uses port 6667 by default. IRC servers normally allow a range of port numbers from 6660 to 6669. Assume you have a Proxy (P) and two machines behind it (A and B). If you want to be able to use IRC on the Clients A and B with all those ports you might have to make Port Mappings for all those ports on the proxy to both of the Client machines (and back). So, in the proxy software map each port (TCP and UDP) for each client machine to the IRC server. Example;

	PORT 6660 to
	PORT 6660 to
	PORT 6661 to
	PORT 6661 to
	PORT 6669 to
	PORT 6669 to

Normally spoken the proxy software already did this for you when it was installed. Or your Proxy software might use some automatic thingy doing this on the fly when you start mIRC. Also it might be smarter to map one port to one machine, or ports 6660 to 6664 to PC A ( and ports 6665 to 6669 to PC B ( Then make sure your mIRC on those machines is properly configured to use only those port ranges that are available on the PC mIRC runs on! capiche? More information in section 3.3.

3.2. Setup of the clients (machine A, B and C) for the use of IRC.

Now that the Proxy setup is done, lets proceed to the machine running mIRC. We assume you have a working SOCKS4 or 5 compliant proxy. I hope you have a SOCKS5 edition since SOCKS4 support is limited in functionality. The most you will be able to do with a SOCKS4 server is to connect to an IRC server. Better forget about DCC!

In mIRC open the File/Options/Connect/Firewall/ menu. Mark the "Use SOCKS Firewall" box and select the protocol. Fill in the other options;
- Hostname: The machine name of your SOCKS server. This can be either a named address or an IP address. Better set this to the IP Number, not the name, of the proxy server machine; in our example.
- User ID: This is the account or user name you have on your proxy system. For most people this will be the User ID portion of their email address (the text before the @ sign). BUT, very often you do not need a login on the proxy at all! Most proxies are 'open' from the inside. Logins and passwords are only needed if only certain users may travel to the Internet. If you dont need (or dont have) a login leave this setting blank.
- Password: The password required, in combination with the Login, to access the firewall. Do not fill in anything if no login and password are needed.
- Port: This is usually 1080, the default port on which Proxies accept connections.

Also check the "Initiate DCC's through firewall" option. Well get back to this later!

Now go to the File/Options/Connect/Local_Info/ menu and set the "On Connect always get" options 'Local host' and 'IP Address' to active. Set the "Lookup method" to Server.

Then connect to IRC. This should work fine. Once fully connected do a DNS lookup on your self by typing the command /DNS and write down what the results are. They show up in your Status window. It will look like this;
*** Looking up
*** Resolved to

Go to the File/Options/Connect/Local_Info/ menu again and double check your IP Address and Local Host settings. Make sure the IP Address matches to what the DNS result told you! (The Local Host settings doesn't really matter.) This sometimes does not get set correctly in mIRC. Don't worry, if the IP Address doesn't match simply edit the IP address settings in mIRC to match what you wrote down from the DNS request and all will work! After this editing set the "On Connect always get" options 'Local host' and 'IP Address' to INACTIVE. If the IP Address was okay leave everything as it was.

Wrong IP Address setting will not block your use of IRC but will mess up DCC Sends and Initiation of DCC Chats. You will almost always be able to recieve files though and accept DCC Chats regardless any wrong settings.

3.3 The Proxy Server setup (machine P) for the use of DCC.

Now here is the tough part. You already have done some preparations above but if you want to get the DCC working properly you have a little more todo. If plain chatting is enough for you for now you could pick up the process here, later.

Ok, figure out how many client machines may all be on IRC at one time and how many DCC transfers may take place on each machine at one time. You might consider 2 parallel DCC sessions so that you can DCC chat and send 1 file at a time, or send 2 files parallel.

With your limit set to 2 for this example you need to open ports on the Proxy for the DCC transfers. mIRC by has default uses ports for DCC from 1024 up to 5000. We will limit this to a smaller range later, for instance 1024-1025. In the proxy you have to map ports 1024 and 1025 TCP and UDP to PC A with IP Address Do not use the same ports for more then one PC in your network!

3.4 Setup of the clients (machine A, B and C) for the use of DCC.

As you know DCC is used for file transfers and private chats between IRC users. By default DCC sessions use random port numbers above 1024. See File/Options/DCC/Options/ "DCC Ports Range". If these port numbers are blocked by your proxy you will not be able to exchange files with other IRC users. This is what we dealt with in 3.3.

In mIRC on PC A go to the File/Options/DCC/Options menu. Remember which ports you set for this machine for DCC? Look at the DCC Ports range. Set the first to the lowest port number (1024) you chose and the last to the highest number (1025).

Check if you still have the "Initiate DCC's through firewall" option set to active. This will make mIRC to use a passive protocol to establish DCC connections when a client is behind a SOCKS5 firewall. This will not work btw with older versions of mIRC or other brands of IRC clients.

4.0. IRC through a HTTP proxy.

As said, do not mix up the proxies (sharing your Internet Conection) we're talking about in most of this file, with a (caching) web proxy as lots of companies use to speed up your surfing over the web with your web browser. Only recently mIRC 5.81 introduced an option you can use to connect to IRC through a HTTP Proxy.

Make very sure you realy have to use a HTTP proxy to connect to IRC! Are you really in some protected environment without direct and free access to Internet? Are you really sure mIRC will not work without using the last resort solution of using a HTTP proxy?

When connecting through a HPPT Proxy mIRC first opens a connection to the proxy server, on some port that it has available. HTTP Proxies typically listen on ports 3128, 5865, 8080 eventually even port 80. You can look in your web brower's settings or windows registry file for your local Proxy configuration. On my machine it tells me; port 5865. This you have to fill in in the File/Options/Connect/Firewall/ Hostname and Port settings.

Once connected to the Proxy, mIRC will instruct it to open a persistent connection to the IRC server of your choice. Et Voila. Keep in mind that all sorts of other IRC thingies like DCC and Ident will absolutely NOT work through a HTTP Proxy. You're stuck to barebone chatting!

Lots of default proxy configurations (as in 90% of them) allow you to connect to remote machines on ports in the 6660-6669 range that you need for IRC. Better configured proxies only allow web related remote ports like 80, 443, 8080.... or they emtirely block this use of persistent connections. In those cases you're out of luck. Most IRC servers do not yet allow people to connect on port 80, 443 or 8080. You could of course ask the admin of your local IRC server to open up these ports, but little chance...

5.0 Links

ICS help

ICS Configuration is a handy utility that makes it easy to open, close and otherwise manage ports in ICS.

6.0. Other aspects

Other aspects of the use of IRC include the use of Ident services. mIRC has a built in Ident server. This server listens on port 113 for Ident requests from the IRC server. The server uses this rather old fashioned system (they really should ditch it!) to confirm your identity. If it does not hear something back (when you have disabled the Ident server of when it is blocked by your proxy!) it will not allow you access to IRC. This means you also have to map port 113, which is used for Ident requests, in your proxy to your PC (A) running mIRC. That way Indent request appearing from the net on the proxy will be forwarded to mIRC and answered by mIRC's built in Ident server.

As you have seen proxies often enable more then one PC to connect to the Internet through a shared Internet connection. This often leads to multiple IRC clients like mIRC trying to connect to one IRC server. Since the proxy will make the server to see multiple clients coming from one address(!) it might refuse some of them access! Servers normally only accept two or three mIRC's from the same address.

Do not mix up the proxies we have been talking about here with a (caching) web proxy lots of companies use to speed up your surfing over the web with your web browser. All information you see regarding proxies and surfing the web, and settings you might need in your web browser, are USELESS in regard to IRC and mIRC.

The same goes for HTTPS or Secure HTTP connections. There are techniques that enable programs to use the port 443 used for secure HTTP connections to connect to the 'outside world' from your local network. Sorry but mIRC (and as far as I know no other IRC programs) is not capable of connecting to IRC through such a Secure connection.

7.0. Open Proxies.

You might not be aware of this but other people already on Internet might also be able to connect to your proxy server! A proxy often is not aware of the direction a user is coming from. This opens the possibility for others to connect to your proxy, and from there to an IRC server, thus getting on IRC WITH YOUR ADDRESS! It is easily understandable what mess that could cause. Imagine people harrassing others through your proxy! ...or hacking machines, or trading porno, ...or whatever. As you see you have to make sure you dont have an Open Proxy

Due to the overwhelming (ab)use of malconfigured Wingate and Proxy servers being exploited daily, most IRC networks are checking all users for open and exploitable Wingate/Proxy servers upon connection. You were probably wondering why you are getting connection attempts to port 23 and 1080 on your computer? That is the check for an Open Proxy. If an Open Proxy is found you will NOT be allowed in on IRC.

8.0. Proxy Server Programs

8.1. ICS - Microsoft's Internet Connection Sharing ICS provides networked computers with the ability to share a single connection to the Internet. If you have multiple computers, you can use ICS to allow you and others on your local area network (LAN) to perform different tasks simultaneously. For example, one person can send and receive e-mail, while another person downloads a file, and another person browses the Internet.

When you use ICS I advise you to install ICSCFG (ICS configuration) as well. This small program will ease up the port configuration of ICS a lot! See for more info.

8.2. NAT32 - Network Address Translation

NAT32 is a Windows Application which gives all computers on your private LAN direct Internet access. NAT32 runs on the computer with the Internet connection and acts as an enhanced IP Router for the other computers on your private LAN. NAT32 gives all the other machines direct Internet access. NAT32 supports Connection Sharing of Modems, ISDN Adapters and Cable Modems.

Each of your other computers is configured to use NAT32 as its Name Server and Gateway to the Internet. NAT32's built-in DHCP Server can configure those other computers automatically if you set them to "Obtain an IP address automatically" in Control Panel Network, TCP/IP Properties.

8.3. WinGate 3.0 (Home edition)

WinGate allows networked computers to simultaneously share an Internet connection. It serves as a firewall, prohibiting intruders from accessing your network. The WinGate SOCKS server is SOCKS 4 and SOCKS 5 compliant.

WinGate 3.0 has an installation wizzard that should do all the work for you. WinGate 3.0 also includes the WinGate Internet Client software that automatically configures the client computer to use WinGate and eliminates the need to configure client applications, allowing for simple and transparent usage of client computers through a WinGate server.

Also the new Winsock redirection protocol (WRP) allows nearly all your applications to run as if they are directly connected to the Internet. Once the WinGate Internet Client (WGIC) is installed on your client machines, no Internet software configuration is needed. Previous versions of WinGate required each application to be configured manually for proxy operation. This is no longer required, although any proxy-configured software will still work.

Eventually the 'mapped links' option can be used. Mapped links (sometimes called "plugs") are used to support applications which do not support traversing a firewall, or working through a proxy server. IRC works on port 6667. You need to configure a Mapped Link in WinGate listening on port 6667, with the remote host being the name of the IRC server you wish to connect to, on port 6667. In your mIRC program, you then set your server to be "gateway"

8.4. WinProxy (Ositit)

This WinProxy allows you to connect your entire LAN to the internet from a single IP address. Provides logging of all internet access and a secure connection to the internet for multiple users from a single IP address. Supports HTTP, Secure Sockets Tunneling, FTP (CERN and Socks), Telnet, NNTP, SMTP, POP3, Dial-Up-Networking, Blacklisting, Local and Remote Logging, Remote Administration, and more.

You can use IRC and mIRC when you are behind this WinProxy. You'll need to enable socks and DNS in WinProxy, socks in Mirc, and DNS on the client computer that has Mirc.

In WinProxy, WinProxy - File - Advanced Properties - Protocols, enable socks and enable DNS; In the DNS setup box put the IP address(es) of your service provider (the search order, not mail and news servers). You may have to call your service provider to these; most provide them on the initial signup paperwork. Don't enable DNS on the WinProxy machine through the control panel. You should stop and restart WinProxy to save and enable the settings.

On the client machine (with mIRC on it), Control Panel - Network - Identification; take note of the name in the 'Computer name' box; this is the NetBios name and you'll need it in a moment. Control - Network - Configuration, find the protocol line that says TCP/IP LAN adapter and double-click on it (install it if it isn't there); you should already have an IP address specified for this machine. Go to DNS configuration, check 'Enable DNS', in 'Host' put the NetBios name you just got, in domain make something up like '', and in the DNS server search order put the IP address of the WinProxy machine. You'll probably have to restart here, as well.

In Mirc, go to File - Setup - Firewalls, and enable 'use Socks firewall'. In the 'Host' box put the IP address of the WinProxy machine; for the port use the default 1080. You should now be able to connect. As far as we know WinProxy will not handle DCC File transfers and DCC Chats, but all other IRC features will work.

As far as we know WinProxy will not handle DCC File transfers and DCC Chats, but all other IRC features will work.

8.5. WinRoute

Network Address Translation, or NAT, is one of WinRoute's most powerful security features. NAT is an Internet draft standard protocol for "hiding" private network addresses behind a single address or multiple addresses. A version of NAT called "IP Masquerading" has been popular for many years with the Linux community and WinRoute is one of few products for the Windows platform to actually provide entry-level NAT functionality.

NAT and Proxy are not the same thing. In proxy each machine is only aware of the Proxy and has to be setup for each application to go through it. In NAT each machine thinks it has its own direct connection to the internet. Nothing to setup for each application. No need as each one thinks it is directly connected. What this means is I do not need to go to any of my 40 machines to setup an applicatoin for the internet. Unless you specify otherwise all aplications will work with you doing NOTHING on the client machine. You need only make changes at the server. Example of things you can not proxy but will work on all machines simultaeneously with NAT from any of your machines to any machine on the net. DCC's, PPTP, VPN, Dialpad,Netmeeting etc.,

NAT can be implemented in many ways, but essentially it creates a nearly unlimited private address space for internal networks that is "translated" by WinRoute so that communications can pass to and from public networks without revealing information about sensitive internal systems. Absent knowledge of the private address space on the internal interface of a WinRoute firewall, it is practically impossible to directly attack a system on the NAT-ed internal network.

8.6. Sambar

8.7. Netproxy

NetProxy is a multiple-protocol proxy server and firewall for Windows 95/98/2000/NT. NetProxy provides simultaneous Internet access to multiple users on your network using just a single Internet account of practically any type (modem, ISDN, cable modem, DSL, leased line, etc.).

NetProxy provides transparent support for versions 4, 4a and 5 of the SOCKS protocol. This means that if you configure mIRC to use the 'firewall' and give it the IP address (or hostname) (typically and socks port number (typically 1080) of your NetProxy PC, you should be able to use IRC without problems. (Dont use the User ID and/or Password fields in mIRC.) Alternatively you can use Port mapping.

8.8. Zensoft IRC Proxy

This IrcProxy (for Windows 95) lets you use irc from a lan or through a firewall completely transparently, the main benefit using this server is that you can use dccs (ie chats and sends) without any problem. It acts like a normal server but simulates a client running from the server host. It is completely transparent and supports all of the irc functions, as it simulates a normal server it will work with any client on any platform.

As the local ip put your internet IP address (for instance As the lan ip put your machine's IP as it is seen from your local lan machines (for instance Then fill in the port to listen on - put the port which you will connect to from mIRC (6667 wouldnt be a bad choice). For the server fill in your local IRC server (like or similar). For the port to connect to put the irc servers' port which will usually be 6667. Set Enable DCC's to active.

Now in mIRC you have to tell it it should connect to the Proxy 1. Go to File/Setup. 2. Select 'Add an IRC server' 3. Description: 4. Server: ircproxy (or whatever your ircproxy server is named) 5. Port: 6667 6. In the Local Info tab set the 'On connect always get local host' to active 7. Method normal. (server works too) 8. Set Identd off and do not enable the firewall.

8.9. SOCKSCAP for Windows

When you're trying to get mIRC (and other Internet applications) to work behind your schools or companies SOCKS compatible firewall you might want to try SocksCap! When you have SocksCap installed and properly configured on your machine you dont have to set up all individual applications to work with your firewall, you just configure SocksCap. This way you can even use (old) programs that do not even support firewalls or proxies!

SocksCap has been prooved to work with lots of applications like NewsAgent, several Telnet applications, Ws-ftp, Realplayer and for instance Outlook Express. mIRC works successfully on SocksCap for Windows exept for initiating DCC File Sends and DCC Chats. It works fine for DCC File Get, accepting a DCC Chat, and all other normal IRC functions.

You should be able to use SocksCap to run with mIRC (disable all socks settings on mIRC) and Winproxy 2.1. The settings for SocksCap are easy to follow, look on the website and in the helpfile!

Socks Server: (ip address of winproxy server) Port : (1080) Protocol: (Socks5) Name Resolution: (resolve all names locally) Direct connection: (add ip address of other computer)

You should be able to -get- DCC's but I think you are unable to send files with this setup.

9.0. Frequently Asked Questions.... and their answers.

9.1. Is it possible to access mIRC if you are behind an HTTPS firewall? At my company, we don't have a SOCKS server. A Secure HTTP firewall, often called a proxy, is available in a lot of networks to provide an interface for secure transactions through your web browser. Indeed, technically spoken mIRC could be made to use such a service to connect to an IRC server (on port 443) but at the moment this is NOT possible.

9.2. I have an Internet cafe with 5 PC's. We are connected to the Net through a Proxy. When some customers are connected to IRC all others are refused access... how can I help that? I am a new mirc user, and i have been download a versions mIRC v5.7 for a month ago. And now we are using link network with winproxy 3.0r1i software, we have 8 computer link together. But there are only 3 to 4 computer that can be connect to irc and the other come out with massage (ERROR You may not connect a clone), can you please tell me what should i do to make sure all the computer can be connect together to mirc. Do not forget IRC Servers only accept up to two connections from the same address. More mIRC's will be regarded as 'clones'. All your users behind the Proxy will have the SAME ADDRESS seen from the perspective of the IRC server they want to use. So the server will see more then 2 people trying to access and thus refuse them! Make sure your customers connect to different IRC servers (probably on the same IRC Network) to solve this problem.

9.3. The problem was that when i signed on to Mirc, it read my Ip as the number that the Dsl Provider gave me ..but when I typed /DNS it gave me a completely different number , that conflict was the problem. After hours of useless tech. support I just kept messing with the options on Mirc until it finally worked. The solution can be found in the File/Options/Connect/'Local Info' menu. Simply change the 'Lookup Method' to 'server'. That should fix your problem!

9.4. Why can I not send or receive files via DCC from my IRC client through WinGate? Due to the fact that DCC requires a dynamically (random) assigned port, it is not possible to create a mapping or other type of service in WinGate 2.x. It makes no sense to map the entire range of ports above 1024 (up to 5000) to get DCC working... However, when using the WinGate 3.x engine with the WinGate Internet Client running on the client machines, most users have been successful in sending and receiving files via DCC from mIRC.

9.5. I just had a DSL line put in and since then have not been able to connect to mirc.... I get the following message... Misconfigured Wingate or Proxy Server -visit for details. I can not connect to IRC. I get strange messages like "Quit (You are banned from this network. Machine is running an unsecured proxy)" and "ERROR You are banned from this network. Machine is running an unsecured proxy" I can't connect up to irc, it always gives various reasons, something about "open proxy denied" I get messages like "Closing Link: (Open wingate or socks proxy. Visit for help or information. *** Disconnected". Well, read the information above about Open Proxies, as well as the information provided on those DALnet and Undernet websites.

9.6. Are you aware of any other proxies supporting IRC and if so what ones ?? Any proxy that has a socks server or 'port mapping' capability should handle IRC to some degree.

9.7. Does anyvbody know how i can use mirc behind a firewall? Open the firewall for the ports you want to use for mIRC - 6667 for starters. If you want to dcc send, or start dcc chats (receiving files and receiving chat requests does not need this), you'll also want to allow incoming tcp connections (yes, OUTgoing dcc is an INcoming connection) on a small range of ports and set mIRC to use that same range for dcc. If you can't change the settings in the firewall (like if it's a school or company firewall), then you can't use mIRC thru it. Sorry, but there's no way to make mIRC work on ports other than the ones the IRC servers are using.

9.8. I keep hearing differing stories about whether a PC home network equipped with WinGate will be allowed to access IRC. Some folks say, "IRCs generally ban ALL wingates." Others say, "If you properly configure the security features of WinGate (and set your chat program to operate with your firewall), you can pretty much use any IRC server." What's the truth? That very much depends on the IRC net you chat at. Some IRC net's don't have a problem and some auto k-line wingates on sight. What I would suggest you do is to learn how to use wingate properly and make sure that it is as secure as you can make it. Once properly secured you shouldn't have any trouble IRC'ing off it.

9.9. I am not sure if I am running a proxy. Is there a way I can check it? Are you connecting more than one computer to the internet? If you are, you're most likely running a proxy server. If not, then you most likely aren't.

9.10. I'm running mIRC and Wingate 3.02 without the client (it messes up my system) How can I properly get DCC transfering to work? DCC can be done with Wingate version 3.0 with no special setup. You can set what DCC port to use in mIRC's settings. In mIRC, press Alt-O. Expand the DCC menu on the left and look under DCC Options. To allow one dcc at a time set the first and last DCC ports to the same port and set your Wingate to allow connections through that port by setting a TCP service on the port you want to use. You can also set mIRC to do dcc thru a range of ports - say 3000 to 3009 - and set Wingate to match that range, if you want more than 1 dcc at a time. Just set up a TCP service on each of the ports you want to use.

9.11. I would like to know if it is possible, or when it will be possible, to use Mirc behind a HTTP Proxy. I noticed that the new version of ICQ allows it. Waiting for your comments.