ePlace
Home
Problems
Solutions
- Sample Setup
- Wingate Security
- Local Security
- Applications
- Line Tests
- Security Tests
- Wingate 3.0 FAQ
- Wingate 4 FAQ
Links
Forums
Add Your URL
Disclaimer

Other Languages

email

Applications

The Wingate 3/4 Winsock Redirection Service provides the Winsock redirection protocol or WRP. 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. 

Manual application configuration longer required, although any proxy-configured software will still work.   

Applications must be set up to access the proxy properly if they are to work as expected.  Applications that don't have proxy setup options may not work with a proxy server.

The problems described here are associated with Wingate, but other proxies have similar problems.

Problems associated with applications usually are related to application proxy settings.  Information on many applications can be found in other links on this page. Searches and queries can be made at the Wingate Forum Site.  These include discussions of problem solutions with virtual domains, most mail programs, Compuserve, AOL, MSN, ICQ, many games, MIRC, Agent, PCAnywhere, CuteFTP, browsers, internet utilities.

A few issues that are typical of application problems are mentioned below..

 

  • Browser.  If you have problems using your browser on a Wingate client, try these settings in Internet Explorer:

In IE, select Tools>InternetOptions...>Connections
Select LAN Settings...
Check "Use proxy server"
Select Advanced.
Enter HTTP: 192.168.0.x Port 80
Enter Secure: 192.168.0.x Port 80
Enter FTP: 192.168.0.x Port 80
Leave Gopher blank
Enter SOCKS 192.168.0.x Port 1080

where 192.168.0.x is the IP assigned to your Wingate server PC, usually 
192.168.0.1. The indicated ports are Wingate defaults.

Your Wingate Server PC can use these settings to route traffic through the proxy 
(recommended since this puts browser behind Wingate 4 firewall) or the browser can access Internet  directly by not checking "Use proxy server".

Netscape and other browsers have similar setting options.

Back to Top

  • FrontPage.  Microsoft FrontPage 98 includes the PWS (Personal Web Server); see below. 

Setup FrontPage as follows; Start up FrontPage, go to tools, options, proxies tab, in HTTP proxy field put Wingate or (the name or IP address of the Wingate machine). Select site to edit.

Notes:

  • Also see Personal Web Server
  • Your ISP server must run FrontPage Extensions for you to be able to use the FrontPage Publish function.
  • User problems with publishing have been noticed.  The procedure that I've used is outlined.  In FrontPage Explorer:

1.   Select:  File | Publish FrontPage Web … (do NOT use Publish button for a first-time upload).

2.    In the Publish Dialog, select:  More Webs.  If this is an update rather than a first-time upload, the target URL will appear in the Publish Dialog and the target directory initialization information will be retrieved from your prior upload.  Select the target URL and steps 3 and 4 will be skipped.

3.   In Publish FrontPage Dialog, Enter ftp://URL of your ISP's server.

4.   In Microsoft Web Publishing Wizard enter

--FTP Server name: Enter URL of your server without "ftp://".

--Directory Path: path for your startup web page. This path should be pre-defined by your ISP.

  5.   In the next dialog, enter User Name and Password. If this is a second upload for the current FrontPage program load, the User Name and Password will not be requested.

Back to Top

  • Game Zone.   From: "WinGate Technical Support"

Currently the best solution we have found to connect to the Game Zone through WinGate is via a third party utility called Kali. You can find Kali at  http://www.kali.net

This is a gaming server proxy application that will force your game connections through WinGate’s SOCKS proxy service and should get it going for you.

Deerfield indicated that Wingate 3 will provide direct support for this type of connection, making the need for any third party applications unnecessary.

Back to Top

  • ICQ.  Wingate Tech Support writes:

Getting the latest version of ICQ to work through WinGate is actually very simple. Select the Preference window in ICQ. Click on the Connection tab. Select "I am using a permanent connection (LAN)" and "I am behind a firewall or Proxy". Press the "firewall settings" button. Select "I am using a SOCKS 5 Proxy server", and click the "Next" button. Then enter the IP address of your WinGate machine, and the port that WinGate’s SOCKS proxy is using (normally 1080). Do not configure a SOCKS password. Click the "Next" button, and then press the test firewall connection button. The rest of ICQ does not relate to Wingate!

ICQ's Wingate Help Page at icq.mirablis.com.

Microsoft Outlook 98 with ICQ:

  • In ICQ Preferences | Check E-Mail, Set:
    • Mail Server Address = 192.168.0.1 or your Wingate server IP
    • Pop3Account = your_user_name#your_ISP_mail_server
    • Password = your mail password.
  • In ICQ Preferences | E-Mail, Set:
    • Select: Use specified e-mail client
    • Client Path = your Outlook 98 path, no options
    • Command Line -c IPM.Note /m %e

Back to Top

  • ISDN.  For an example of how ISDN has been setup using Wingate, see the HELP section at Website Makeovers.

Back to Top

To a certain extent WinGate 3.0 works with NetMeeting.  When using the WinGate Internet client you can make an outgoing call from ONE workstation at a time (regardless of license size.) You will not be able to receive incoming calls. This is due to the way Netmeeting uses its ports. It was not designed to connect through a proxy server and will not connect through any proxy server except an H323 proxy, which WinGate is not. Ms needs to modify Netmeeting in order to get this to work correctly. We are working with them on this.

Back to Top

From: "WinGate Technical Support" <wgtechsupp@deerfield.com>

To connect to more than one news server through WinGate you will need to add an additional TCP mapping for each additioinal news server you want to connect to. These additional mappings will all have to be on different ports as well. For instance, your primary news server mapping service in WinGate will be on port 119 (by default,) with the news server set as the default mapping on port 119. To add a second news server mapping, simply create a new TCP mapping service, set to accept connections on port 120 (for example.) Then, enable the default mapping and enter the name of the second news server you wish to connect to but be sure to set the default mapping on port 119, not120. Now to connect to the second news server from your workstation machine, simply configure the news reader to connect to wingate on port 120 instead of the default port of 119 (not possible with some news readers, you will have to verify that this is possible before you try it.) WinGate will take the connection on port 120 and route it directly to the news server you specified in the default mapping onthat port. You can add as many new servers as you wish in this manner, but again, you have to be sure that your news client program will support connecting on ports other than the standard 119.

Back to Top

  • Norton Live Update.  Open Live Update Settings.

1.    Connections Tab:  Set "How do you want to connect?" to Internet.
2.    Internet Tab:  Check "Use passive mode FTP transfers".
3.    Proxy Tab:  Check "Connect to Proxy Service".  Select "Custom Proxy Settings" option.  Complete entries for FTP and HTTP. Typical settings are FTP: Address 192.168.0.1, port 21; HTTP Address 192.168.0.1, port 80.  where the address is the Wingate server and the ports are as specified in the Wingate Gatekeeper.

Back to Top

  • Outlook. 

Microsoft Outlook requires:

Pop3 proxy, on port 110.

SMTP mapping service mapped to SMTP server on port 25.

  1. Start MS Outlook 97 or MS Outlook 98
  2. From the menu bar, select Tools, then Services
  3. Select ADD, and Internet Mail
  4. Fill in the information fields as normal until you come to Internet Mail Server
  5. In the Internet Mail Server field, enter the name or IP address of your Wingate server (e.g. 192.168.0.1)
  6. In the Account Name field, enter your POP3 account including your username in this manner: user#mailhost.domain (e.g.. BillG#microsoft.com)
  7. In the Password field, enter your Pop3 password

Account Properties are the same on Outlook 98 and Outlook Express except that there is an additional Security Tab on Outlook Express.  The property settings in this example are used on both the Wingate Server and clients of the server.

  • ASSUME:

    • 192.168.0.1 = IP of your Wingate machine
    • Username = uname
    • email address = uname@yourisp.net
    • incoming mail server= mail.yourisp.net
    • password = ********

  • ACCOUNT PROPERTIES:

    • General Tab:
    • --Mail account: Lastname, Firstname
    • --User information
    • ----Name: uname
    • ----E-mail address: uname@yourisp.net
    • Server Tab:
    • --Server information
    • ----Outgoing mail (SMTP) 192.168.0.1
    • ----Incoming mail (POP3) 192.168.0.1
    • --Incoming mail server
    • ----Log on using
    • --------Account name uname#mail.yourisp.net
    • --------Password ********
    • --Outgoing mail server
    • ----This can be used if required.
    • Connection Tab
    • --Connect using my local area network (LAN)
    • Advanced Tab
    • --Server port numbers
    • ----Outgoing mail (SMTP) 25
    • ----Incoming mail (POP3) 110

Back to Top

  • Personal Web Server.  Microsoft PWS uses Port 80. The default for the Wingate WWW Proxy server is also Port 80. Change this Wingate port to 85. You'll also need to change apps that use the proxy server (IExplorer, Netscape, others). There's also a .INI file for FrontPage98 in which the port can be changed. See serk\enu\admin.htm on the FrontPage 98 CD-ROM.

Back to Top

  1. SMTP.  To add a SMTP mapping service, complete the following steps:

    1. Logon to GateKeeper with Administrative rights

    2. In the right hand pane, right click the word Services

    3. Click New

    4. Click Service

    5. Click TCP mapping

    6. Change the service name to SMTP mapping

    7. Change the description to enables the sending of mail

    8. Accept connections on port 25

    9. Put a check in the Enable default mapping to checkbox

    10. In the server textbox enter either the name or IP Address of the SMTP server

    11. Click the bindings tab

    12. Click the Specify interfaces connections will be accepted on radio button

    13. Ensure that the IP addresses of 192.168.0.1 and 127.0.0.1 are both in the Bound que

    14. Click OK

    15. Click on the save changes icon

Wingate provided the following SMTP troubleshooting tips.

Here are several options you have to trouble shoot your SMTP problems.

Please try any or all of the following:

----Option 1----

From the WinGate machine connect to the internet. Go to a DOS prompt and type ping localhost you should receive four replies with 32 bytes of data. Then ping your ISP’s SMTP server you should receive four replies with 32 bytes of data. If not, verify your DNS configuration per ISP’s instructions. Then verify your DNS configuration per the WinGate help desk at:http://www.wingate.net/help.htm

----Option 2----

On the WinGate machine go to a DOS prompt. Type: telnet (your ISP’s SMTP server) 25. You should be able to connect with a response that states "you are connected to a SMTP server", "(your ISP’s SMTP server) ESMTP Send mail". Exit the telnet window and at the DOS prompt type: telnet localhost 25. You should be able to connect with the response "your ISP’s SMTP server ESMTP Send mail". If not, then you need to verify that the SMTP mapping created in the WinGate services is created as follows;Accept connection on port 25. Uncheck "Bind to specific interface" or you may check "Bind to specific interface" if you want to bind to the IP address of the WinGate machine. For more information please refer to: http://www.wingate.net/secure-wingate.htm

Check enable default mapping to server (your ISP’s SMTP server) on port 25.

All other settings left at default.

You might also need to delete then create a new SMTP mapping. With the WinGate machine still connected to the internet go to a workstation and at a DOS prompt type telnet "wingate 25" (or what ever you call the wingate machine in the hosts file), with out the quotes. You should be able to connect with a response "your ISP’s SMTP server ESMTP Send mail". If you can connect with the above respond or a respond that says you are connected to a SMTP server, then WinGate is configured correctly to send mail on port 25, if not, verify your DNS configuration per the WinGate help desk at http://www.wingate.net/help.htm and verify that the application you are using to send mail is setup to send on port 25.

Back to Top

Last Updated July 29, 2002 10:20:11 PM