I am trying to correctly configure Wingate to allow me to share my AOL Broadband connection, via my BT ADSL line in the UK (I have with 2 PCs in a SOHO setup)
The normal AOL login (via the AOL screen name) creates a WAN VPN (L2TP) connection using the BT Voyager 100 DSL Modem. However, it is also possible to make a standard dial-in connection to AOL by entering "AOLScreenname@aol.com" into the BT Voyager Modem dial-in entry under Start >>Connect to option. This then connects to an AOL proxy server (xxx.proxy.aol.com) and does not creat a VPN.
MY WINGATE CONFIGURATION
I have successfully configured Wingate to share the IC (using NAT) when connected via the non-VPN dial-in method using the following config:
- ENS: NAT (Enabled), Firewall (Disabled)
- DCHP Server (Fully automatic)
- TCP / IP Settings on gateway PC (IP = 192.168.0.1, no gateway entered, no DNS entered)
- WWW Proxy Service: Transparent Redirection = On (client PC not using http proxy)
Using the non-standard (ie non VPN dial-in) method is not ideal as I do not have access to the AOL browser. But this at least provides a baseline to show that Wingate is working on a non VPN dial-in connection.
PROBLEM
If I use the above configuration but then use the correct AOL login process (that creates a L2TP VPN) then I am unable to connect to Websites that require SSL (eg hotmail or windows update). I am also unable to connect my Hotmail account from within Outlook
Note: I am able to connect to SSL websites if I change from NAT to either http proxy or WGIC connection method. However, I do not wish to use the http Proxy method (does not work with Outlook/Hotmail) or WGIC method (I find that WGIC will lockup the client PC on startup if the Wingate/WGIC connection gets dropped)
Is there a better way to configure Wingate to work with my AOL L2TP VPN connection?