by erwin » Aug 15 06 1:18 pm
Hi Ian
I take it the WinGate machine has an IP address to the LAN and one to an Internet router on the DMZ
LAN>>WinGate>>Router>>Internet
If this is the case then you could set all of your LAN clients to use the LAN IP of WinGate as their Gateway and DNS. This way clients will use NAT on WinGate to send their Internet requests.
There are several ways of authenticating clients using NTLM
I'll explain one of the easiest, assuming clients are using NAT described above
1. Select NTLM auth option in the WWW proxy.
2. Set a policy in the WWW proxy ("User can access services" right)
3. Select the users to be affected on the Recipient tab of the policy, and
4. Select User must be authenticated radio button at the bottom.
5. Select the System policies (default rights ) on the General screen of the WWW proxy to Are ignored (so that this policy will not be affected by any System policy that may have been set in WinGate).
6. Turn on transparent proxy for port 80 in the WWW proxy\Sessions config in WinGate, and this will catch all NAT requests and force them to be authenticated by the policy set in WWW proxy.
All clients using an NTLM compatible browser (eg IE) will be able to be authenticated via NTLM, when they attempt to access the Internet through WinGate. The user credentials that the client is logged into their machine will be passed to WinGate automatically. If these are not valid with WinGate then they will be prompted to log in.
With NTLM auth option in WinGate there are several other ways for clients to authenticate themselves which are all explained in the WinGate helpfile, under the WinGate Security Model\Authentication section, so there might be one that suits your needs better.
Hope this helps
Erwin