/!\ This page was reviewed and chosen for deletion. It contains woefully outdated and inaccurate information today. The contents serve little archival value besides historic interest. This page should be replaced with a general article touching on proxies, firewalls and other network traffic forwarding technologies. Reviewed by a raccoon on Aug 21, 2016.

[ This is an emergency mirror of the original page at Wingate’s home page. ]

Article Number: 1014

Title:

How to configure mIRC to connect through WinGate

Author:

WinGate Technical Support

Last Modified:

1998-12-30

Product(s):

WinGate 2.1

Issue Type:

How-To

Platform:

Win95/98,WinNT

  • These instructions are for WinGate 1.x and 2.x versions. If you have WinGate 3.0 your applications need to be configured per your ISP’s instructions, as if they were directly connected to the Internet.

WinGate does not include an IRC proxy. For a general Internet Chat application to work through WinGate, WinGate requires a mapped link to your IRC server. The standard port for IRC connections is 6667, and this link will be installed when you install WinGate. Some IRC Chat applications will use the SOCKS proxy of WinGate for firewall access, by default WinGate installs a SOCKS proxy on port 1080.

mIRC

Requires:

SOCKS4 proxy, no specific port number (default port is 1080.)

  1. In mIRC, click on the File menu
  1. Select Setup
  1. Select the Firewall tab
  1. Enable the Use SOCKS firewall option
  1. Under Hostname enter WinGate, or the name of the WinGate machine
  1. Check that the port number is where the WinGate SOCKS proxy is configured to accept connections on (usually 1080)
  1. The User ID and Password fields are redundant and do not require entries
  1. Under the Identd tab, check that the Identd server option is disabled
  1. Under the Local Info tab, you must enter the IP Address that was assigned to your machine (suggested as being in the 192.168.0 subnet) when it was configured to connect to your TCP/IP LAN. The Local Host name will also have been assigned to your machine and must be entered. mIRC will not be able to detect these fields as WinGate does not support reverse look-ups
  1. Under Local Info, the On connect, always get: options are not fully understood. It is trial and error as to which of the two options should be enabled to make the application work. Both the Normal and Quick IP method options seem to work
  1. The rest of the mIRC set up does not relate to WinGate

Keywords: chat mIRC Internet Relay Chat

WinGate Home Page | WinGate Support | WinGate Help Desk

&nbsp_place_holder;