1. Open GateKeeper, go to the Help menu and select License Management
   The Qbik License Viewer will open displaying your activated licenses
   
2. Click the Add new button
   
3. Click the Next button
   
4. Select the radio button Activate a license key
   
5. Enter your license details
   
6. Click the Next button

1. Open the License Manager
   
2. Highlight the license that you wish to deactivate
   
3. Click the Deactivate button

Attempt to access a FTP server results in a "requires authorization" error message

Description

Attempting to access a FTP server results in the following error message when using Internet Explorer

 "FTP server requires authorization" 

 ftp://user:pass@someserver.com/ 

In this context, the term "binding" refers to creating an association between a service and a network interface. This association makes the service available to network users connected to this interface.

WinGate uses binding to control which network interfaces its services will be available on. For instance it is common to make services available on internal networks, and unavailable on external untrusted networks. The latter is used to prevent abuse of your proxy by unknown external users.

Services in WinGate 6 use a set of binding policies to determine which interfaces they will bind to. Using a policy makes it possible for WinGate to automatically select the correct actual interfaces to bind to, as well as react to changes in the network (such as disconnection or connection of interfaces, changes in IP address etc). This means WinGate can ship with a secure default configuration that will just work.

Binding policies allow you to specify binding based on the type or usage of a network adapter. All network connections in WinGate are automatically classified as either internal or external (may also be manually specified). WinGate uses the IP address of the adapter to choose. Public IP addresses result in the adapter being deemed to be external.

Default binding policies for services are normally configured to bind to any internal adapter. So if the usage of an adapter is changed, this will cause the binding policy to be re-evaluated, and may result in bindings being added to or removed from adapters.

Adapter usage also affects firewall rules.

• Disable Network name broadcasts to the Internet
  Checked by default stops LAN traffic from broadcasting their Netbios network details to the Internet.
• Allow users to ping this machine locally.
  This allows clients to be able to test TCP/IP connectivity to the WinGate server via ICMP ping utility and is checked by default.
• Allow users to ping this machine from the Internet
  Not checked by default, as there are some will known ping type attacks that can be generated by attackers on the Internet.
• Discard Spoof packets
  This option is enabled by default, WinGate will check to ensure that the source IP address in the packet header is really the computer that made the request. If it is not, the packet will be discarded. This is also a well known form of exploitation on the Internet. ]]> ENS – The General Tab
  ENS (Extended Networking Services) was introduced to WinGate as a plug-in and then fully integrated in Version 4.3, to provide support for a Firewall, Network Address Translation, and Routing services. The settings for ENS can be found under the System tab in Gatekeeper on the WinGate Server.
  
  Enable the Extended Network Driver :
  ENS has its own driver for low level networking support which is loaded on Operating System startup. To disable ENS (and the driver from loading), make sure this check box is unticked. If selected during installation WinGate ENS will be installed and started when WinGate starts.
  
  General Purpose Internet Sharing (NAT):
  By enabling this check box it will allow WinGate to provide Network Address Translation (NAT) for clients to access the Internet through WinGate. When disabling this option clients will require either the WinGate Internet Client or Proxy method of connection to use WinGate. For more detailed explanation on how NAT works please refer to the WinGate helpfile.
  
  Support for Multiple Subnetworks (Router)
  This option allows for the support of multiple subnets and uses WinGates ability to route packets (network traffic) between dissimilar IP subnets when they are both connected to the WinGate Server.
  
  Firewall
  This setting allows you to set default levels of security with the WinGate firewall based on the general purpose of WinGate activity. Due to the central focus of the firewall opening and closing specific ranges of ports further manipulation of the Firewall can also be achieved through configuration of the Port Security tab.
  The following is a brief explaination of each of the standard firewall settings.
  
  
  • Disable WinGate Firewall
    By disabling the Firewall, all protection for the WinGate Servers external connection is removed and no port restrictions implemented. This can seriously undermine WinGate’s ability to defend from malicious port based attacks from the Internet.
  • Low: Allow Servers to run behind WinGate
    When this setting is chosen TCP Ports 20,21(ftp), 23(telnet), 25 (Smtp), 80(http), 110(pop3) 113 (Authentication) 119 Network News Server, are opened to receive connections from the Internet who are trying to access these common Internet Protocol Server types that could be running on or behind WinGate.
  • Medium : For Games and Internet Applications
    When this setting is selected only TCP Ports 1024 – 4096 are allowed for access for most common Internet games and applications, such as Messenging services, newsgroup apps etc. No server app ports or ports below 1024 are permitted with this setting.
  • High Denies all connections from the Outside
    As it suggests this setting will block all incoming connections that were not initiated from a request by a client application and are being responded to by a host server on the Internet. Most client apps will work fine when the firewall is at this setting, as long as they don’t require the server to initiate the connection (e.g. active mode ftp).
  • Custom: For Advanced users
    As mentioned previously users can allow or deny access to ports used in the Firewall through the Port Security tab. When ever ports are managed this way the WinGate will automatically change to this setting on the General Tab.
  ]]> The Port security tab in the ENS configuration in WinGate is where you can configure and customize how it will handle the use of application ports in the WinGate Firewall. While it may look like being a simple matter of allowing or preventing ports to be opened or closed there are a number of advanced features that will allow greater control of how traffic is handled through WinGate.
  
  Default Action.
  
  Configuring any setting under the Port Security Tab applies to all Network Interfaces. What this means is that for any interface/protocol (Tcp/Udp) combination you can set a default action for all interfaces/packets.
  
  (To understand how WinGate treats interfaces and Private versus External Ip addresses please click here)
  
  It is recommended that the defaults be kept as these generally provide the safest approach to defending WinGate from network attacks.
  
  Suggested Default Interface Action
  
• External - TCP/UDP Default Action - Deny
  
• Internal - TCP/UDP Default Action - Allow
  
  The security filters included with WinGate port security tab allow you to open close ports depending on Applications that require access through WinGate both to and from the Internet.
  
  These security filters work by:
  • Providing maximum protection from attacks originating from the Internet.(by denying all LAN-bound packets arriving on the external interface)
  • Providing maximum flexibility for Internet users on your LAN (by allowing all Internet-bound packets from your LAN out).
  The security filters can be set by doing the following:
  1. Open the ENS properties in GateKeeper on the WinGate machine
  2. Open the Port Security tab.
  3. Click the Add button.
     
     In the Port Range Configuration:
     
  4. Select the type of connection that will be affected by the security filter (Connections. to/from etc), and the appropriate protocol (either Tcp or Udp).
  5. Specify the appropriate port (port range) that is influenced with this filter and a description that will easily identify its purpose.
  6. Select an action to take when a packet uses this port either Allow, Drop, or redirect the packet to another IP address (for example a Web server running behind WinGate)
  
  In simple terms the Use Syn cookies option, allows the WinGate to control a session of packets before they are allowed to even enter the port by keeping track of valid Ack requests from a host on the Internet, so that bogus packets (which can be used in a Network attack called a SynFlood type of attack) will have less chance to penetrate WinGate’s defences.
  This option is not ticked by default to allow for maximum application session compatibility and should only be implemented by administrators who are experienced with TCP session mechanisms.
  
  Under Options
  • Use standard time out values is the default settings and these are generally never need to be altered.
    Setting packets to never time out is considered dangerous and not recommended.
  • If the Notify when this range is accessed then it will display in the Firewall tab in Gatekeeper.
    
  • The Cloak connection failures option is ticked by default. What this means in simple terms is that when a would be attacker is scanning the WinGate server to find vunerable ports, WinGate will disguise the port’s status by so it will be overlooked by the port scanner. For an explanation on port cloaking, please to the WinGate helpfile.
  ]]> The purpose of this tab is to show all of the routes currently listed in the routing table that WinGate uses. This tab will only appear if Support for multiple Subnet works has been enabled on the General tab of ENS, as WinGate's routing table will be able to determine where traffic from one subnet is to be sent in order to reach the other subnet. There are several options that can be configured to allow WinGate to handle this routing.
  • Relay UDP broadcast packets
    Most Windows based network PC’s use Netbios broadcast to advertise themselves and discover machine identities on the LAN. Usually they will send UDP packets on ports 137,138, to discover this information. This option allows these Netbios broadcasts to travel across the dissimilar subnets that are being bridged by WinGate and inturn allow the sharing of Network information shared resources, machine identities etc.
    In the advanced section (accessed by clicking the Advanced button on the Routing tab) you can set specific ports which UDP broadcasts are allowed to be sent on if required. Obviously Ports 137 and 138 are listed by default, but this is useful for other LAN applications that require the use of UDP broadcast packets such as DHCP and certain LAN games.
  • Indicate UDP broadcasts (Ports < 1024)
    Excessive UDP broadcasts on ports under 1024 can lead higher then normal memory consumption. By enabling this option (ticked by default) ONLY excessive UDP broadcasts (lasting longer then 20 seconds and at least 10 seconds since the last activity) will be displayed in the Activity screen in GateKeeper. (This is switched on by default).
  • Enable Support for Multiple Default routes
    One of the problems that arises in routing is where more then one default route is given. For example: A default gateway is listed for the internal network interface on a machine, but whenever the machines Dialup connection connects to it's ISP, it is given another default gateway. This new gateway is sometimes given a higher priority for traffic then the internal interface's existing gateway, which will break the internal routing of traffic between differing subnets. Enabling this option will rectify this by allowing all privately addressed packets to use the proper internal gateway.
  ]]> Background:

  Reverse proxies are useful if you are hosting websites on your network and want to have a single access point for connections from the Internet. WinGate's WWW proxy service can be configured to reverse proxy incoming connections from the Internet to the web server running on your network.

  When WinGate is used for both a forward proxy and a reverse proxy, ideally there will be at least two network adapters in the WinGate server to allow the separation of forward and reverse proxies. This allows you to run both proxies on the same port, but on different adapters, and allows you to apply access rules separately to both forward and reverse proxies.

  We recommend that you set up a new WWW proxy service to use as a reverse proxy.

  ---

  Task:

  Create and configure the reverse proxy

  Secure the reverse proxy

  ---

  Steps:

  Create and configure the reverse proxy

  1. In the WinGate console, go to Control Panel::Services and choose Install Service.
  2. Select the WWW Proxy Service, click Next
  3. Name the service, e.g. Reverse Proxy Service
  4. Select the Bindings tab, delete the binding policies "Bind to any IP address on any internal adapter" and "Bind only to 127.0.0.1 on Software Loopback Adapter", Click Add and create a new binding policy to bind to "Any External Adapter". To accept https connections, add a second binding policy and check the port override box to listen on port 443. Check the box under Channel Security to "immediately negotiate secure channel", note that you will need to have imported a certificate into WinGate to use this option.
  5. Select the Web Server tab, leave the default site set to reject request and click Add to add a new site
  6. Name the site for your reference, e.g. reverse proxy, set the action to Reverse proxy
  7. Enter the IP address or network name of the web server hosting the site, enter the port that the site is running on
  8. Select the Hosts tab, enter the site name that users will use to reach the site, e.g. reverse.wingate.com For https connections, add a new site, enter the server IP and port, enter the site name on the Hosts tab and check the box to match if request is https

   

  Secure the reverse proxy

  1. In the WinGate console, go to Web Access Control::Access Rules, choose Add Rule from the Tasks panel
  2. Name the rule, e.g. Secure reverse proxy
  3. Set the rule result to "Deny access and show", select a different block page if required
  4. Uncheck the box "Rule applies to all WWW proxies" and select the Reverse proxy, click Next
  5. On the Who tab, choose Everyone from the dropdown, click Next
  6. On the Where tab, leave All IPs selected, click Next
  7. On the What tab, choose "All categories/sites except those specified" and add a new site, enter the site name, e.g. reverse.wingate.com, click Next                                                                                                                     
  8. On the When tab, leave the "Rule applies always" box checked, click Finish
  ]]> Background:

  After installation of WinGate is complete and a license has been activated, a user database provider must be selected. Choices available are the WinGate user database provider, the Windows user database provider, and if a trial, Professional or Enterprise license was activated, the Active Directory user database provider. If the WinGate user database provider is selected the Administrator user does not yet have a password.

  ---

  Tasks:

  Log in to the WinGate console as Administrator with the appropriate credentials

  ---

  Steps:

  1. Select a user database provider from the available options
  2. Enter the Administrator credentials for the user database provider selected 
     • WinGate user database provider - Administrator/no password (see fig.1 below)
     • Windows user database provider - Local machine administrator credentials
     • Active Directory user database provider - Domain administrator credentials

   

  (figure 1)

   

  ]]> Background:

  There are various reasons to move WinGate to a new server. Moving WinGate is a straight-forward process that involves installing the same version on the new computer, exporting and importing the WinGate configuration and moving the license. It is important to run the same version of WinGate on both machines to make importing the configuration as easy as possible. Sometimes that can require you to update the original WinGate installation to the same version before exporting the configuration, or installing the old version on the new computer, importing the configuration and then updating to the latest version.

  A WinGate license can only be activated on one machine at any time, so activating a 30 day free trial allows you to configure and test the new server before deactivating the license off the original server and moving it to the new server.

  ---

   

  Tasks:

  Check the version of the existing server and install the same version on the new server

  Export the configuration from the existing server and import it into the new server

  Move the license

   

  ---

   

  Steps:

  Check the version and install WinGate

  1. Check the version by clicking the Qbik icon in the upper left of the console and choosing About WinGate Administrator
  2. Check the \WinGate\Update to see if the installation file is listed there, if so copy to the new server and run the installation file. If not there, download from www.wingate.com or contact support for an archived version
  3. Install WinGate on thew new machine

  Export and import the configuration

  1. Open the Configuration utility in \WinGate\Utilities
  2. Export the configuration
  3. Copy the wingate.config file to the new server
  4. Open the Configuration utility in \WinGate\Utilities
  5. Import the configuration

  Move the license

  1. Deactivate the license from the original server by navigating to Control Panel::Licensing in the WinGate console, right click the license and choose "Copy key to clipboard", then right click and choose "Deactivate"
  2. Activate the license on the new server by navigating to Control Panel::Licensing in the WinGate console. Choose Add license from the tasks panel and paste in the license key

  ---

   

  Additional Tasks:

  Test connectivity to the new server. If the new server will have a different IP address than the old server, you may need to update the proxy server IP address in the browser settings on the LAN clients. Update any wpad.dat file locations in the DHCP server and any GPOs that reference the server location.

   

  ]]> Unless it's a special multi-activation licence, a WinGate or WinGate VPN license can only be activated on one machine at a time. This means if you need to move your licence to an installation on another computer you must deactivate the licence on the current installation first.

  (For information on exporting your registry settings for use in the new server, please see the following article)

  To de-activate a licence:
  

• run the licence management tool (Help-Licence Manager or Start Menu-Programs-WinGate-Licence Manager)
• highlight the relevant licence and click the de-activate button. A connection will be made to our activation server and your licence will be deactivated.
  
  Once this has been done the licence key can be activated on the target installation.
  
  If you can't connect to the activation server you can generate an email deactivation request from within the Licence Manager, click the configure button and change activation type to "Activate licences by email". An encoded request will be generated, copy and paste this into an email and send to activation@qbik.com

  

  If you uninstalled WinGate without deactivating your licence you can log into the wingate website and deactivate your license from there. If you still cannot deactivate your license then you'll need to contact your reseller or Qbik support to deactivate your licence. To submit a ticket to Qbik support click here ]]>

  Symptoms

  After exporting a WinGateConfig.reg file from a 32bit server and importing it on a 64bit server (or vice versa), WinGate does not see the newly imported registry settings and loads its default settings instead.

  Summary

  This happens because the WinGate configuration is stored in a different location of the registry on different operating system architectures. This is due to "registry redirection" which is a function of Windows 64 bit OSes designed to support 32 bit applications. WinGate is a 32 bit application.

  On 32bit Windows, WinGate's configuration is located in: HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate

  On 64bit Windows, WinGate's configuration is located in: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Qbik Software\WinGate

  Solution

  On the 64bit target computer you will need to import the registry file using the 32 bit version of Regedit.exe.

  1. Open Regedit.exe from the folder Windows\SysWOW64
  2. Click Open
  3. Find the registry file
  4. Click OK.

  More information

  For further questions, please contact our support helpdesk.

  ]]>
  
  
  Select the Port Security menu and click ADD to create a new port opening.
  Choose INTERNET COMPUTERS TO THE WINGATE PC
  Enter the port range (1503 to 1503)
  Choose whether you need TCP/UDP or both
  Choose ACTION--ALLOW PACKET
  Please note, if you need to map this port to a machine behind the WinGate server, choose REDIRECT PACKET TO IP ADDRESS and enter the IP address of the machine you are redirecting to. If you have problems with the connection try checking the box DON\'T TRANSLATE SOURCE IP.
  Click OK, you should now see the new port opening in the list with Action ALLOW or REDIRECT.
  
  ]]>

  Background:

  SSL inspection is required for WinGate to access HTTPS traffic for AV scanning, caching and web access rules.  Some sites will validate the entire certificate chain and break the connection when it is inspected.  These sites will need to be exempted from SSL inspection via policy.

  ---

  Task:

  Create a policy to exempt sites from SSL Inspection

  ---

  Steps:

   1. Create a new policy at Control Panel::Policy, for Any HTTP proxy, ConnectRequest event. Name the policy and enter a description if required.

  

  2. Build the policy:

  • Drag the WWW Proxy Server:ConnectRequest event onto the workspace
  • Drag a Data boolean check onto the workspace. Enter Enable SSL inspection exemption policy into the Check boolean field. Name the element "Enable SSL inspection exemption policy?". Connect to the ConnectRequest event.
  • Drag a result to the No output of the boolean check and set the result to allow. Connect to the "Enable SSL inspection exemption policy?" element.
  • Drag a data list lookup onto the workspace.  Enter or select {{Request.Server}} into the "Check that the value of" field, enter No SSL Inspection sites into the "Is contained in" field.  Name the element "Is excepted site?". Connect to "Enable SSL inspection exemption policy?".
  • Drag an expression evaluator onto the workspace. Enter or select Session.EnableSSLInspection = "false". Uncheck "resolve expression into true/false result". Name the element "Disable SSL Inspection". Connect to the Yes output of "Is excepted site?".
  • Drag an expression evaluator onto the workspace. Enter or select Session.SetData("SSL_Inspection", Session.EnableSSLInspection), uncheck "resolve expression into true/false result". Name the element "Store SSL inspection state".  Connect to the Yes output of the Disable SSL Inspection element and the No output of the Is excepted site element

  

   

  ---

   Further tasks:

  This policy will automatically create the boolean "Enable SSL inspection exemption policy" and the data list "No SSL Inspection sites" in Control Panel::Data::Global Data.  The boolean can be used to create a button on a dashboard to quickly bypass the policy.  The list of sites will need to be populated. Note that only the server part of the request will be added to the list, e.g. wingate.com, a URL will not be read. e.g. https://www.wingate.com/purchase/wingate/purchase.php.

  This policy allows the SSL inspection state to be logged, this must be added manually to the WWW Proxy Usage log.  For information on adding this field to the log file, see this kb article.

  ]]> Symptoms

  Downloading of automatic updates for applications such as Antivirus, spyware, Windows Updates etc fails even though normal Internet access appears to work without problems.

  Summary

  This problem could be caused by either caching or by using Kaspersky AntiVirus for WinGate (KAV). These applications use the BITS service which does partial downloads but KAV requires the entire file for scanning purposes so it prevents partial downloads.

  Solution

  Disable cache lookups for update sites
  Refer to this knowledge base article to create a cache exception

  Create a KAV scanning exception
  Refer to this knowledge base article to create a KAV scanning exception

  More information

  For further questions, please contact our support helpdesk.

  ]]> Symptom

  Selecting gateway rotation from a WinGate service does not rotate connections out through gateways, all traffic continues to go out the main gateway.

  This is often related to the Windows Application Layer Gateway Service. ALG is a service that provides optimum gateway selection duties for Windows and breaks gateway selection for WinGate in the process. It handles outgoing connections post WinGate and overrides any specific gateway that WinGate has chosen to use. Disabling the service is the quickest fix, and is non consequential.

  Solution

  1. Go to Start -> Control Panel -> Administrative Tools -> Services
  2. Find and double-click 'Application Layer Gateway Service'
  3. Change the Startup type to Disabled
  4. Click the Stop button
  5. And then Click OK

  If WinGate's gateway selection still doesn't work after disabling ALG, check to see if there are there any Internet Security Suites/Virus Scanners installed on the WinGate computer as some suites that intercept outgoing connections will override the selected gateway in the process, similar to what ALG does.

  ]]> If you are considering changing the location of History logging (in the History Logging option in GateKeeper on the WinGate server) then it is recommended that you avoid selecting a non-directory location such as root directory (e.g C:\)
  
  Due to restrictions that can occur with certain Windows operating system handling of root directory locations, it is suggested to specify a new folder location for the WinGate history logging, rather then a plain root drive location. E.g. C:\\WGHistory rather then just C:\\

  To change the location of the history database:

  1. go to the History tab in GateKeeper
  2. right click in the History pane and select properties
  3. this will open the History settings dialogue box where you can specify the database path

  ]]> If you forget the password for the administrator account and need to recover access to WinGate, you can remove the administrator by doing the following.

  • Stop the WinGate Engine from the system tray (by right clicking it and selecting stop) then open the registry editor.
  • Find: HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\UserDatabase\administrator
  • Delete the data for the Password value and restart the WinGate engine. Open Gatekeeper and log in as administrator with a blank password.

  We do not recommend running WinGate without an Administrator password. To set a new Administrator password:

  • Go to the Users tab in GateKeeper
  • Right click the user Administrator and select properties
  • Enter a password in the password field and confirm it

  

  ]]>

  Background:

  SSL inspection is required for WinGate to get access to the full URL of a requested HTTPS resource for AV scanning, caching and web access rules. It is also required to return a block page to an HTTPS request.  Without SSL inspection, WinGate is able to see the requested site, but not the full URL of a request, and if the page is blocked by web access rules, a connection error is presented instead of the WinGate block page.

   

  ---

  Task:

  1. Create or import a certificate into WinGate to use for SSL inspection
  2. Configure clients to use the WinGate WWW proxy for HTTPS
  3. Configure client to trust the signing certificate
  4. Enable SSL inspection in the WWW proxy

   

  ---

  Steps:

  1. Create or import a certificate into WinGate to use for SSL inspection

  From Control Panel::Certificates, choose New Certificate from the tasks panel.  Alternatively, choose Import to import an existing certificate.

  

  Fill in the required fields to create the certificate.  The certificate will appear in the Certificates panel when it has been generated.

  Double click the certificate, choose the Details tab and click the Copy to file button to export the certificate.

  

  2. Configure clients to use the WinGate WWW proxy for HTTPS

  For Internet Explorer/Chrome go to Internet Options::Connections and click the LAN settings button. Enable the Proxy Server check box and enter the IP address and port of the WinGate WWW proxy. Click the Advanced button and select the option to "Use the same proxy server for all protocols".

  Note: This option can be configured in a Group Policy Object in an Active Directory environment

  For Firefox go to Options::Network Proxy::Settings and choose the option for Manual proxy configuration.  Enter the IP address and port of the WinGate WWW proxy and select the option to "Use this proxy server for all protocols"

  For Edge go to More::Settings::View Advanced Settings and click the switch beneath Use a proxy server.  Enter the IP address and port of the WinGate WWW proxy. Click Save.

   

  3. Configure client to trust the signing certificate

  

  The certificate that will be used by WinGate for SSL inspection must be placed in the Trusted Root folder for the local machine on the LAN clients.  Launch the Microsoft Management Console (type mmc.exe from the run command) and add the Certificates snap-in for the computer account. Navigate to the Trusted Root Certification Authorities::Certificates folder, right click and choose All Tasks::Import and import the certificate.

  Note: This option can be configured in a Group Policy Object in an Active Directory environment

  4. Enable SSL inspection in the WWW proxy

  

  In the WinGate console go to Control Panel::Services::WWW Proxy service, select the SSL inspection tab.  Check the box to "enable inspection of encrypted content" and select the certificate from the drop-down box.

  

  Inspected connections appear on the activity panel as having a gold padlock beside them, and are presented as https connections instead of CONNECT requests.

   

  ---

   

  Further Tasks:

  Some sites validate the entire certificate chain and will break with SSL inspection. These sites should be added to a policy to exempt them from SSL inspection.  See this kb article for more information.

   

   

   

   

  ---

   

   

   

  ]]>
  You can submit a support request here for any questions that you have about any of the Qbik products. We offer free support to our customers and take the approach that the more we can help you, the happier you'll be. And if you're happy we're happy!
  
  From time to time problems can occur when tickets are submitted. If you haven't heard from us within one business day (bearing in mind that we are in New Zealand) then you should assume that your support request was not received by the Qbik Support team.
  
  We make it our policy to reply to all emails within one business day, but it is often much sooner than that, and we try very hard not to leave our customers hanging. If you've submitted a ticket but you still haven't recieved a reply please send an email to support@qbik.com and let us know.
  
  Thank you!]]> When checking to see if WinGate is functioning as it should, there are several factors to check to ensure that everything is correctly configured. These checks should be done once basic network connectivity has been established between the client and WinGate machine, and Internet connectivity has been established between the WinGate PC and the ISP(Internet Service Provider).
  
  On the WinGate Server:
  1. Open Gatekeeper.
  2. Check that all System services are shown and enabled in the System tab of GateKeeper.
  3. Check to see there are no port conflicts on any of the Proxy services. This will be indicated by the appearance of a red circle with a white X beside the particular service. These will appear this way in GateKeeper if there is another application or service running on the machine that is using the same port (Such as a Webserver running on port 80 or FTP server running on port 21).
  4. Check that all System and Proxy Services have the appropriate interfaces bound to each service so that client machines can communicate with theses services. For more information on understanding Bindings and Interfaces click here.
  5. Check that users/groups have appropriate connection rights and that they are conforming to appropriate policies that may have been set.
  On the Client Machine
  
  If using NAT:
  • Does the client have the correct network details IP address, Gateway and DNS of the internal IP address of the WinGate Server. (It is common to use the Ipconfig utility to find these details)
  WinGate Internet Client (WGIC)
  1. Open the WGIC from either control panel or from the start menu/WinGate Internet Client entry.
  2. Select the General tab and make sure both options are checked.
  3. Open the WinGate Server tab, and check to see that the WGIC has discovered the location of the WinGate server. The server and its IP address should be in the window. If this is not the case then click the refresh button.
     If it still does not appear then check the client and server machines network details and make sure they are configured as per the WinGate helpfile, reconfirm that you have basic network connectivity to the WinGate server. Check also that the Generic discovery Protocol and Winsock Redirection services are enabled running, and correctly configured in Gatekeeper on the WinGate server.
  4. If the server appears under this tab and there is still problems connecting the client open the Application tab.
  5. If there are any browser/email applications listed then remove them all and click the Advanced tab.
  6. Here click the Reset Client button. This will refresh any Winsock connection and applications that are used on the machine.
  Important:
  
  If the WGIC client is using IE for a browser:
  If you access the connections tab you should set the connection to “never dial a connection” and check the “use Lan settings” configuration. You should make sure that there are no details entered under this option and ensure the “Use proxy” option is not selected. ]]> Problem:

  There is no prompt to authenticate when logging in to the console and the WinGate console shows the navigation tree but branches only show Certificates, Licensing, Logging and Modules and when you click on any branch the main panel shows a blank screen.

  

   

  ---

   

  Resolution:

  This problem can occur when the GlobalSign Root CA certificate has expired or is missing on the WinGate server. To verify this, check the properties of the WinGate.exe file in the WinGate program folder. On the Digital Signatures tab, double click the signature, check the certificate and make sure that the root certificate in the certificate chain isn't showing as invalid.  If the root certificate is invalid then it will need to be renewed.
  
  When you add the GlobalSign root certificate, it needs to be added to the trusted root section for the computer (rather than for a user). To do this you'll need to add the certificates add-on to the Microsoft Management Console and select the Computer Account option.

  Renew the certificate and restart the WinGate engine. The WinGate console should now look like this:

  

   

   

   

   

  ]]>