Since the purpose of WinGate VPN is to extend you local network, if it is configured correctly, it is possible to have remote WinGate VPN clients log into the domain or Active Directory that the hosted WinGate VPN belongs to.

Before the remote WinGate VPN machine can log into a domain via the hosted WinGate VPN it must be configured to be part of that domain initially.

This is usually done the normal way the any Windows machine is configured to become a member of a domain or Active Directory. (Please refer to Microsoft documentation if you are unsure of how to do this.)

Once the WinGate VPN has been setup on both ends of the proposed VPN. Then two further things are necessary:

On the domain /Active Directory of the WinGate Host:

A Domain controller on the Active Directory /domain where the WinGate VPN host machine is located, must be configured to take part in the WinGate VPN.

This means either it must have its gateway IP address set to the WinGate VPN server or have the RIP client installed. (Please refer to the WinGate VPN help, or the VPN Whitepaper on our support page, for more information on how to make LAN machines participate in a WinGate VPN.)

This is required so that the Remote client can communicate with the Domain Controller for the purposes of logging in.

On the WinGate VPN Client: (The remote machine joining the hosted WinGate VPN)

1. Open the WinGate VPN configuration.
2. Select the VPN you wish to join and click the Properties button
3. At the bottom of the properties page select the On engine start from the When to join VPN box.
4. Click OK.

What this will do is make sure that when a user starts up the Remote client machine it will automatically attempt to connect to the WinGate VPN host (in the background). This obviously requires a working Internet connection to be available.

Once the VPN is connected, the user will then be able to log onto the domain from the main windows logon (ctrl-alt-del).

The other more manually orientated option is for the remote user to log into Windows (onto the machine itself as Domain login will be unavailable) and connect manually to the WinGate VPN.

Once connected the user can then log out of Windows, and log back onto the Domain, as access to the Domain Controller will now be available, since the WinGate VPN will remain connected, throughout the logon, log off, log onto domain process.