Open WinGate and under the System Tab double click on the Email Option. Under the Delivery Tab, select from the How to deliver pull down menu ''Use Gateway'' and enter in the 3rd party mail server you wish the mail to be sent to. You can also select ''Use Gateway for Undeliverable Mail'' and all mail that can not be sent directly would use the 3rd party mail server to send the mail.

Open WinGate and under the System Tab double click on the Email option. Under the Domains tab click the Add button at the bottom. In the pop up window enter in the domain name you want WinGate to use and then select the option you wish this domain to be associated with (This domain is hosted locally, This domain points to a local domain, or Relay for this domain)

Occasionally WinGate history files either become corrupt, or reach their maximum limit and are not purged. Deleting these files usually corrects this situation. KB article 2127 can guide you through this process.

This is because the firewall, by default, only allows traffic from private IP addresses. Please refer to KB article 2003 for a complete workaround on this.

This is an issue that has been reported infrequently, and is specific to version 4.5. In all cases, reentering the dialer account details does allow the dialer to connect. The WinGate developers are currently working on a solution, and the next WinGate release will eliminate this problem.

Please review the knowledge base article, Performance Issues with WinGate 4.5.

Click on Options, Advanced then the Syslog Options tab. Remove the check from the Auto-activate Syslog and firewallLog when event occurs box.

In some rare circumstances the actual SSL port (443) needs to be specified in the WWW service located within GateKeeper. KB article 1947 explains how to correct this, in detail.

WinGate 4.3 has Extended Network Support (ENS) built into the installer. ENS includes a firewall which is enabled by default, this will prevent external users from accessing servers running on or behind the WinGate server. KB article 1601 explains how to modify ENS to allow access.

To verify this open GateKeeper, click Options, then click on Plug-ins. You should see a listing for Extended Network Support option. If this is visible, the plug-in has been installed.

Yes, however, if the network uses a public IP addressing scheme (i.e.; NOT 192.168.0.x, 172.16.x.x, or 10.x.x.x), you must use WinGate Standard or Pro. To enable this, log into the GateKeeper and in EACH service, under both the System Tab and the Services tab, click on the bindings tab. Note: DO NOT change THE REMOTE CONTOL SERVICE.

From the bindings tab, under the heading Available, the internal IP address should be listed. If it is, double click it and the address will be moved to the bound field. You may need to click OK to an error telling you this is a Non-Private IP Address and there is a security risk.

Go into the Control Panel, Double click the WinGate Internet Client, click the applications tab. If iexplore.exe is listed here, remove it. The same would hold true if you are using Netscape and netscape.exe is listed here, remove it. Click apply, then OK at the bottom. Now open the browser and you should have no problems.

Click the users tab and then right click anywhere in the listing on the left hand side. Select Export Users. This will export all of the users and their passwords into a text file which will be placed in the c:\program files\wingate folder. You can export using a Tab Delimited text file or a Comma delimited text file.

In GateKeeper, click on Options then clicked on Advanced. Select the Network Interfaces tab. Listed here you should see your internal network''''s IP Address. If you wish to change its status, click on the Interface, and then click the Edit button at the bottom. In the Interface Properties box, be sure to select the correct option for that specific Interface. Typically, for an internal IP Address, the settings are Public (No) and Trusted (Yes).

WinGate simply imports NT users from the Primary Domain Controller (PDC) or Backup Domain Controller (BDC). WinGate cannot administrate (add, delete or modify) current user accounts. All user maintenance must be accomplished in the actual NT or 2000 database itself. Once those changes are made, either stopping and restarting WinGate, or clicking on the "Synchronize now" button within the User Database Options window of WinGate will update WinGate accordingly.

Go into GateKeeper, and click on the Users Tab. Double click on the Database Options, then click on the Synchronize Now button. This will synchronize GateKeeper with the user database within NT and carry all users and groups into the GateKeeper user database.

During the installation of WinGate 4.X, the installation program will ask you if you want to use NT for User Authentication. Place a check in this box and then continue with the installation. This will automatically import the users and groups from NT/2000 into the GateKeeper user database.
Note: This is only available with the Pro version of WinGate 4.X

In GateKeeper, click Options then click Auto Save Changes. The check determines if the feature is enabled or disabled.

"Email Address Aliases" allow you to specify more than one Email address for a single user. They work for both incoming and outgoing mail to provide the following advantages. It is simple ­ any Email directed at the "original recipient" is sent to the "Change to" recipient. The SMTP Proxy will actively change the TO: address before it reaches the actual SMTP server (so it will work for both incoming and outgoing Email).
For Example, if you have Email addresses info@test.com, postmaster@test.com, and webmaster@test.com and you want them all to be received by user@test.com. Under the Aliases tab, you would enter in each Email address in the ''''Mail Received for Address'''' field. Then in the ''''Change Address To'''' field you would enter in user@test.com.
NOTE: This can only be used when you have an internal mail server. Internal meaning that the mail server is located on a computer behind WinGate.

This basic approach is effective in that it makes your SMTP server an unattractive option to a spammer. This is because "spammers" typically rely on open-relay mail servers to relay their message on to many thousands of recipients from a single send.
However, it does NOT prevent local users from sending an outbound message to as many recipients as they want. This way "spammers" are restricted but your local users are not.
You can tell when a message is dropped because it had too many recipients. Neither the sender, the intended recipient, nor the WinGate administrator is notified (there will be an error code 2 entry in the SMTP Proxy log file).
NOTE: This can only be used when you have an internal mail server. Internal meaning that the mail server is located on a computer behind WinGate.

You can specify a list of "Local Mail Domains" ­ only users who are members of one (or more) of these domains will be able to send and receive through this proxy. WinGate verifies this by checking the Email address of both the sender and recipients (via the "MAIL FROM" and "RCPT TO" commands specified in the SMTP protocol).
If the mail sender / recipient is not a member of a "local mail domain", you can configure the proxy to:

• Allow Relaying ­ Permits open relaying of Email (spamming)
• Reject Relay Attempts ­ Rejects the message and notifies the sender
• Silently Discard Relay Attempt ­ Rejects the message but does not notify the sender (annoying for the spammer since they think their message was successfully dispatched)

NOTE: This can only be used when you have an internal mail server. Internal meaning that the mail server is located on a computer behind WinGate.

Many ISP’s charge for the amount of data sent through their servers. You may choose to restrict the maximum size for an incoming message! (WinGate will not restrict outgoing Emails). Note that the message header/control fields are normally 20k (so you should allow for this when configuring your policy on Email size).
You can tell if this worked when a large message is dropped and neither the sender, the intended recipient, nor the WinGate administrator is notified (there will be an error code 2 entry in the SMTP Proxy log file).
NOTE: This can only be used when you have an internal mail server. Internal meaning that the mail server is located on a computer behind WinGate.

Using a USB connection is actually no different than a network adapter card on the WinGate server; the configurations will still apply from the WinGate helpdesk based on the operating system you are using. The USB connection will show up in the network properties and will be available for configuration.

Yes, MSN Messenger will work just fine behind WinGate. For more information about setting up MSN Messenger behind WinGate, see knowledge base article 1700.

For normal use, this is not a serious vulnerability. The Winsock Redirector Service is, by default, only bound to the local network adaptors. Additionally, there is no need to bind the Winsock Redirector Service to public (Internet) adaptors because such attacks originate from within the LAN (i.e. from a local user). GateKeeper will warn the operator if an attempt is made to bind the Winsock Redirector Service to a public adaptor.

The developers of WinGate have addressed this issue. If this is a concern in your network, be sure you are running a version of WinGate higher than 4.1.0. Download the latest version of WinGate here:

http://www.ccsoftware.ca/wingate/download.cfm

It is not suggested that you run WINS on a WinGate network. WINS is Microsoft’s own internal DNS server. Generally WINS is used for internal DNS only, meaning running WINS will resolve the internal computer names in the network. WINS needs special configuration for external DNS. Having both WINS and WinGate’s DNS service enabled will cause conflict and not allow the workstation computers to get DNS resolution.

The reason you are seeing this message is because the ISP is not accepting your account information. Most ISP’s, or Mail Servers, will not allow relaying, this is a setting within the Mail Server itself. If you do not have an account with the Mail Server for sending mail then you will get this message. If you get this message on a client computer then you will need to contact your ISP and ask them to add your account to the trusted domain for SMTP mail. If this is not possible, you maybe using the wrong SMTP server within your account. If you are looking for a Mail Server, try VisNetic MailServer. VisNetic MailServer has an MX resolver that, when used with WinGate, corrects these errors.

Yes, by using the Extended Network Support (ENS) function in WinGate 4, which features Network Address Translation (NAT), you can run Dimension 4.

Yes, both of these satellite systems are compatible with WinGate, utilizing the ENS firewall and Network Address Translation (NAT).

After testing JuniorNet with all versions of WinGate, the solution to get this working will be the implementation of Network Address Translation (NAT). This means you will need to install Extended Network Support (ENS).

Back to top

When the ISP requires you to enter an @ symbol or any other type of delimiter character, this may indicate that the ISP is using a proxy server.
FIX: Delete the pop3 mapping in GateKeeper, create a TCP mapping service to handle the pop Email through WinGate. For more, see Knowledge Base article 1650.

Follow these steps to make certain that your Internet browser has been properly configured on all computers.

1. Double-click the Internet icon or Internet Options in the Control Panel.
2. Click the Connection tab.
3. The Connection page will look different depending on the version of Windows running on your computer. If you have Windows 95, confirm that the box labeled Connect to the Internet using a local area network is selected. If you have Windows 98, confirm that the box labeled Never Dial a Connection is selected.

Certain printer manufacturers require that network computers run a proprietary software program to use the printer over the network. Consult your printer documentation for more information on how to share the printer on the network.

You must have a functioning Internet connection available prior to the installation of Network Setup Wizard in the Internet-Sharing PC. Uninstall the networking software and confirm that the computer can successfully access the Internet before running the Network Setup Wizard again.

Try the following steps:

1. Confirm that the Internet-Sharing PC is powered on and logged in to the network.
2. Verify that your network cables are connected to the computers.
3. Confirm that your network interface cards are installed properly.

We recommend that you keep the newer version of the file.

You will need either a Windows CD or diskettes to complete the installation of the Network Setup Wizard. If you do not have a Windows CD or diskettes, then it is possible that you may already have the Windows 95 or 98 installation files on your hard disk. These files are known as Windows Cabinet files or CAB files. The Windows Cabinet files are usually located in C:\WINDOWS\OPTIONS\CABS.

Yes you can, all the information on changing error strings can be obtained via GateKeeper help files:
Within GateKeeper click help / help topics / Index / type Advanced WinGate Configurations

This is actually a known issue with Windows 98. The reason this started happening after installing WinGate is that it WinGate uses some dll’s within the operating system that the OS is not able to shut down. There is a patch on the Microsoft Knowledge Base:
Some of the keywords to use for searching are: Shutdown, Reboot, winboot
Here is another link to check

A network is simply two or more computers connected together so they can exchange information. Networking makes it possible for one computer to use a device (such as a color printer) that is connected to a different computer. In the home, a network can be used to share a single Internet connection among several computers.

Home networking technology enables two or more PCs, located throughout your home or small office, to communicate. With home networking, your computers can:

• Share your fastest Internet connection
• Share printers and other peripheral devices
• Access and transfer files on any hard drive of any computer
• Play Multi-Player games

1. Click on the WinGate icon in the program tray to open the GateKeeper.
2. On the left side of the Dialog box, double click on Caching to open a Dialog box (although it should have opened to it, be sure that the systems tab is the highlighted tab on the bottom.)
3. Under the heading Cache Options, set limit cache size to zero (0)
4. Click OK

WinGate can be set up to block certain ports. When someone attempts to access these blocked ports, a log is created to track the event. For more, see Knowledge Base Article 1629

This is most often caused by running the software with an older license key. For more information see WinGate Knowledge Base Article 1624.

If you were using the 3.0 version of WinGate with a trial key and have upgraded to 4.0 without allowing the installer create a new 4.0 trial key, the 3.0 key will expire at the original trial expiration date. (30 days from the initial 3.0 installation, NOT the 4.0 installation)
To fix this, re-install the WinGate 4.0 file. During the installation you will be prompted for license information (the 3.0 license will be in the field). Select "Trial Key" (the middle radio button) and a new key will be created. This key will activate version 4.0 for the full 30 day trial period
Note: If you are running a licensed version of WinGate 3.0 and install a trial of 4.0, you will revert back to 3.0 when the trial period expires.

The instructions in the Application Specific setup articles are for connecting through WinGate’s manual proxy settings. If you are running WinGate 3.x or later, with the WinGate Internet Client (WGIC) Software installed on your workstations, or have installed the ENS plugin with WinGate 4.0, configure your applications per your ISP’s instructions. In most cases, this will be to simply leave the applications configured per default installation.

The instructions in the Application Specific setup articles are for connecting through WinGate’s manual proxy settings. If you are running WinGate 3.x or later, with the WinGate Internet Client (WGIC) Software installed on your workstations, or have installed the ENS plugin with WinGate 4.0, configure your applications per your ISP’s instructions. In most cases, this will be to simply leave the applications configured per default installation.

Extended Network Support is the new module in WinGate that includes Network Address Translation (NAT), Internet Firewall, and multiple network routing. All three features rely on the NAT engine being installed, but are all individually configurable

NAT stands for Network Address Translation (hereafter NAT) and provides WinGate with more power and flexibility for Internet sharing. NAT enables you to share an Internet connection among networked computers running virtually any application on any platform (including Windows, MacOS, Unix and Linux).

Log in to Gatekeeper and click the Help Menu item. Click the Register icon and enter the new license name and registration key. Click OK and you will be prompted to close and restart Gatekeeper to see your changes. If you are upgrading from the Home version to either Standard or Pro, you will have to stop and restart the WinGate Engine to complete the changes.

Yes 16 bit applications will work with WinGate. You will, however, need to use the Standard or Pro version for this connection (or the Extended Network Support with WinGate 4.0), due to the fact that 16 bit applications will not work with the LSP solution (WinGate Internet Client software). The 16 bit application will need to have proxy configurable settings to allow it to work with WinGate (or utilize the NAT function with ENS).

The home version of WinGate will not bind to a non-private IP address. This means that the client computers will not connect when you are using a non-private IP address. You MUST use 192.168.0.1 for the WinGate server when running WinGate Home.

Bytes sent to Client
This is the total number of bytes WinGate has sent to the client machine. In the case of HTTP use, a lot of this will come from the cache.

Bytes received from Client
This is the data that the client has sent to WinGate.

Bytes sent for Client
This is the data that WinGate has sent to servers on behalf of the client. This is usually different than the number of bytes received from the client.

Bytes received for Client
This is the amount of data WinGate has downloaded from the Internet on behalf of the client. This will likely be lower than the number of bytes sent to client, due to caching.

Second on-line
This is the number of seconds that a client was registered with WinGate. Note that this is not a reliable way of telling how much time a user spends on the net if they are logged on. Being logged on does not imply Internet use. Seconds online is updated at the end of all user sessions, when a user logs out.

The WinGate trial version offers the choice of all three WinGate versions when testing. It is important to note that these versions offer different features. For WinGate Home, using proxy settings is not an option. Rather, the WinGate Internet Client has to be used for all applications. If you purchased home, make sure that you have installed the WGIC on all client computers. Further, make sure that the Internet applications are set up as if they were directly connected to the Net.

Most likely, there are issues with the cache in WinGate. You should find that if you disable all caching (WinGate, browsers, web filters, etc.) and you purge the existing cache, you''ll receive Windows updates.

Edit the WinGate Internet Client by accessing it in the “control panel” (under “settings” in the “Start” menu). Double click the WinGate client icon in the control panel to open a dialog box. Click the applications tab, click the browse option and add the exe file that is using the CPU for local access.
You can find out which file is using the CPU by - hitting the ctrl / alt / delete button at the same time / choose task manager / click the processes tab and this will tell you what file is using the CPU.

Be sure you are using the latest version of WinGate (currently 4.X) and verify that there is no traffic in GateKeeper for the amount of time the auto-disconnect is set to. If there is traffic then there is something that is making a request and keeping the connection alive. Stop the application from making a request and that should solve the problem. Also, be sure no requests are being made on the server. The server activity will be tracked, although not seen, through GateKeeper.

It is unknown why port 139 stays open. This is NOT a WinGate issue, however. Port 139 is a NetBIOS port and WinGate only controls TCP ports.

For more information, please visit this site: http://grc.com/faq-shieldsup.htm#139

If the services in GateKeeper no longer appear, they can be manually restored. This may happen if you have installed something on the server that had a major effect on the TCP/IP settings. You can add the services back into the server to allow client machines to access the Internet using proxy settings. For more information see article 1495

If you lost the Administrator password for Gatekeeper, you will need to perform an uninstall/reinstall on your Server computer. This is necessary to best protect your WinGate network from unauthorized changes.
For more, see article 1696 in the Knowledge Base.

If you install the WinGate Server Software prior to statically assigning the IP address on the Internal NICthe DHCP Service will not function until the Everyone Group is added to the Policies tab.

You will need to edit your DHCP service in Gatekeeper, click the policies tab and add a policy. Click OK in the new policy to set it for Everyone, Unrestricted rights. Click OK and save your changes.

WinGate Home is a Circuit level proxy server while previous versions of WinGate were application level proxies. When using a Circuit level proxy, you don’t configure any of your client applications for manual proxy connections they will be configured to connect directly to the Internet through a Local Area Network. The WinGate Internet Client application will then connect them correctly through WinGate’s Winsock Redirector Proxy service.

Yes, Netmeeting, Internet Phone, and other video conferencing software is supported by WinGate 4.0. There are limitations to the H323 protocol, which is used for Internet conferencing. See article 1272 in the WinGate Knowledge Base for more information.

Yes, WinGate 4.0 with ENS will work with most Internet Games. For more information, see article 1139.

You need the WinGate Installer, a working TCP/IP network (all computers can PING one another), a working Internet connection, and Windows 95/98/NT/2000/ME or XP Operating Systems. .

Your Internet Applications should be configured as they would if you were connecting directly to your ISP. You should choose the option to connect via a LAN versus a direct connection or modem connection option.

No, there is a fee for upgrades. See the Pricing page for more information.

You will need to download the latest version from the WinGate Download Site: http://www.ccsoftware.ca/wingate/download.cfm

This could be caused by two different issues with IE4. One is a problem with the SOCKS client built into IE 4. Try disabling the SOCKS proxy setting in IE proxy configuration by simply deleting the entries in this field. Second is an HTTP 1.1 compatibility issue with WinGate. Since WinGate does not fully support HTTP 1.1, you will have to disable both HTTP 1.1 settings in IE 4 configurations. These are found under the [View] menu item, [Internet options] selection. Then click the [Advanced] button and scroll all the way to the bottom of the list. Simply remove the check from beside both HTTP 1.1 options to disable them.

Currently WinGate will only allow for outgoing VPN requests using Point to Point Tunneling Protocol (PPTP).

Yes, WinGate will work with a DirecPC connection. Users will have to manually connect. Once the Internet connection is made WinGate will allow your LAN access to the Internet.

Yes, WinGate will run on a Novell network. It will not run on a Novell server, but will run on a Win 95, 98 or NT machine on the network. You then simply configure TCP/IP networking on the network workstations per the instructions in the Knowledge Base and other help documentation. You do not need to add or configure TCP/IP in the Novell server unless it will act as a router between two separate TCP/IP network segments.

With WinGate version 4.0, there are a number of options that allow you to secure the network. One is by binding the individual proxy services to a specific interface. This tells WinGate not to accept connections from anywhere but that particular Interface. Another option is to setup your system policies to only accept connections coming from specific address ranges. By using the ENS (Extended Network Support) you will have a fully functioning firewall on the WinGate Server.

This is the result of a timing problem between WinGate and RAS. It relates to the rate at which WinGate's dialer polls the RAS connection for status.

If you have manual proxy settings in your browser it needs to be configured to use the WinGate WWW proxy server for FTP. You need to change your browsers FTP port number from port 21, to port 80 (or the same port number as the WinGate WWW proxy server in Gatekeeper). The WinGate FTP proxy is designed for stand alone FTP clients, such as FTP Voyager.

When connecting the WinGate machine to the Internet through a Cable Modem, you first need to be sure to have two Network Interface Card’s (NIC’s) installed in that computer. One connected directly to your Cable Mode and the other connected directly to your internal network. You should not try connecting the Cable Modem directly to your network hub. Then configure the Cable Modem NIC per your ISP’s instructions, so you can browse and successfully access the Internet from that machine. Install TCP/IP on the internal NIC. Configure it per the instructions in the WinGate documentation. Be sure not to change the DNS or Gateway settings in this NIC’s configuration, only assign a static IP address and subnet mask. The rest of the WinGate configuration will be the same as if you were connecting to the Internet through a standard modem. You will not need to configure a dialer.

Yes, you can block file downloads by changing your configuration settings in WinGate.

Minimum Requirements * Computer with a 486 or higher processor
* Microsoft Windows 95/98 or NT operating system
* 8 MB of memory
* Typical Hard disk space required: 50MB(100MB recommended), additional space for cache to be stored
* Winsock 2
* TWO (2) network adapter or NIC. One for the Internet, one for the Network
* Internet or Intranet communication capabilities and all required hardware for the connection (modem, NIC card, etc.)

Yes, WinGate can dial in to MSN through MS Dial Up Networking. Add [msn/] before your login name in WinGate's dialer (without the brackets of course). Without this addition, WinGate will not be able to login to MSN successfully.

Yes, you can connect PC Anywhere through WinGate to external hosts on the Internet. As well as connecting from the Internet to internal hosts.

It is not possible to configure Netmeeting to work with WinGate 2.x. While it is possible to configure the TCP ports that Netmeeting requires for directory services, it is not possible to connect to the dynamically assigned UDP port.

If you are running version 2.1 or 3.X, you will have to bind all available services to the IP address of the Internal network, as well as the standard loopback address of 127.0.0.1 when available. In version 4.X, you can use the firewall Plug-in to secure your network.

Yes you can connect your WinGate network through another proxy. This is called Cascading proxies. The configuration details can be found in article 1001.

Yes you can use AOL Instant Messenger through WinGate. In the WinGate 2.x versions you will need to manually point the application through the Socks 5 proxy. WinGate 3.x with the WinGate Internet Client (WGIC), or WinGate 4.0 with WGIC or ENS, will allow you to simply configure IM to connect via a LAN, with NO proxy settings needed.

To add users you need to have WinGate Pro version. This error message occurs when you try to enter new users, groups or locations in any other version such as in the 2.x Lite, 3.x Home or Standard, or 4.0 Home or Standard.

The IP address you are seeing in Gatekeeper is merely the [Local host Loopback] address. This is a standard address for all TCP/IP stacks that simply indicates that you are connected to a service on the [Localhost] machine. There is no need to, nor should you try to, change this address.

You can configure WinGate policies so all users must be authenticated before they have access to the Internet.

Due to the fact that DCC requires a dynamically assigned port, it is not possible to create a mapping or other type of service in WinGate 2.x. However, when using the WinGate 3.x engine with the WinGate Internet Client (WGIC), or WinGate 4.X with the WGIC or ENS, running on the client machines, most users have been successful in sending and receiving files via DCC from the IRC client.

You enter the registration in Gatekeeper, under the System Info icon. In 2.x this is located in the right pane. In WinGate 3.x and 4.X, it is located under the Help menu.

The first time you log in to Gatekeeper, you need to leave the username set to Administrator and the password blank. In fact, you should not add or remove any information from any of the fields there. You will get a warning that you are logging in without a password, click [OK}. You will then be notified that you will have no rights on the system until you change your password, that is ok too. As soon as you press [OK] you will be prompted to change your password. Leave the old password blank and type in your password in the [New] and [Confirm] fields. Press [OK] and you will be logged in to Gatekeeper for the first time.

WinGate version information is displayed in Gatekeeper under the [System info] icon.

The problem of WinGate randomly dialing out is most likely caused by DNS lookups coming from your workstations. These do not have to be Internet DNS lookups, but can be requests for workstation names on your local network. Some TCP/IP stacks also have built in name resolvers that periodically refresh their cache, NT 4, and MS office 97 are examples.

Back to top

Yes, you can block access to certain sites through WinGate. You can also restrict users access through WinGate to only certain, pre-determined sites using the Ban list feature in WinGate.

Yes, you can run an SMTP server on your internal network behind WinGate. Step by step instructions can be found in article 1030.