Knowledgebase: General Networking
Configuring WinGate in the Active Directory
Posted by Adrien de Croy (Import) on 30 January 2004 04:26 PM
With the move to Active Directory by more Windows based networks, there are several things that are needed in order to make WinGate work within this type of scenario.

It is recommended that you read the knowledge base article relating to Active Directory factors that could influence your WinGate Configuration, before attempting to instigate WinGate in the Active Directory. You can read this article by clicking here.

The following steps outline what is necessary to have WinGate work successfully in an Active Directory environment where WinGate is running on a machine that is not a Domain Controller, and not a (Dynamic) DNS server.

Please Note the Following:
  • If client machines receive their IP addresses and network details that they require to function in the Active Directory from a DHCP server on the LAN, then this should be MS DHCP server providing these, not the WinGate DHCP service.
  • When setting up WinGate in Active Directory it is recommended that the WinGate machines internal IP details be set statically, and recorded as required in the AD.
  • For WinGate NAT (Network Address Translation) clients to function properly, the MS network DHCP server should be set to give the internal IP of the WinGate machine as the Gateway(Router)option to client machines, as part of its scope settings when issuing Ip addresses.

Once WinGate is installed on the machine:
  1. Open Gatekeeper
  2. Under the System tab click on the DHCP service
  3. Stop the DHCP service
  4. On the generaltab set the Service Start up to Disabled.
  5. Click OK.
  6. Save changes in GateKeeper.
  7. Open the WinGate Advanced Options that is found under Start Menu\Programs\WinGate Advanced options.
  8. Enter the IP address of the Active Directory DNS server. This is required to prevent DNS Loops occuring between WinGate and the Active Directory DNS server.
  9. Click OK
(Dynamic) DNS Server configuration

If the (Dynamic) DNS server is configured to be a root server, it will need to have the Root Forward Lookup zone (entered as a (.) in the DDNS server’s DNS server properties) deleted to allow the forwarders option to be available. ( please refer to Microsoft knowledge base on how to do this.)

Once this is done, then the option to enter a DNS server will become available under the Forwarders tab in the (Dynamic) DNS server’s DNS server properties.

Here you should enter the internal IP of the WinGate machine. This will allow client Internet requests from clients to be forwarded by the Dynamic DNS server to be handled by the WinGate machine.

Once this has been done,then you will need to enter the IP address of the DNS Active Directory server in the DNS server option of the WinGate Advanced Options. These options are found on the start menu under Start Menu\Programs\WinGate Advanced options.

This is required to prevent DNS loops occuring between WinGate and the Active Directory DNS server.

(Dynamic) DNS Server running on the SAME machine as WinGate

For the case where WinGate may be installed on the same machine as the (Dynamic)DNS server then you must disable both DHCP service and DNS service in WinGate. There is no need in this scenario to set the Forwarders option to WinGate IP in the DNS server properties as described previously as they are now on the same machine.

(1449 vote(s))
Not helpful

Comments (1)
19 February 2012 04:42 AM
pls post with screen shot it will helps