Running Wingate On A Static (LAN)

[robinconc]

Hello

I'd really appreciate some more details on setting up and configuring of Wingate 6.0.3 on a network using static ip address. I have a problem where i had to disable NAT because it denies all network clients internet services as soon a it is enabled. Basically my understanding is QBick is saying its best to run Wingate using DHCP. Is there some configuration that i missed? Any help will be appreciated.. its working ok now, running (http service and socks service) but the are a few issues i am facing. one in particaular where i have a client logging on to a web server using Ports 80 and 443 and she has been having problems now for weeks trying to logon. What has happen is i have narrowed it down to the Wingate Proxy. What i cat figure out is what has happen to stop her from accessing that particular web server? I am also running MDaemon Server on the same system that the Wingate server is on. Thanks in advance...

[MattP]

Hi,

Really there is no difference between running your LAN with static IP addresses or dynamic IP addresses (using DHCP). We certainly don't have a preference, you'll find it tends to be determined by the size of your network. If you have 100 machines then you're much better off using DHCP, just to avoid the headache of having to keep track of that many IP addresses.

If you're only running a handful of machines on your network then it will be much easier to run static IP addresses, but still not necessary. The cool thing about the WinGate DHCP service is it's all set up to run automatically, all you have to do is give the LAN adapter in the WinGate server a private IP address and WinGate will allocate IP addresses to the LAN clients based on the IP range that you're using, specifying itself as the default gateway and DNS server.

This allows you to set up the LAN clients with the minimum of fuss, you can just set their adapters to "obtain an IP address automatically" and you're away.

I'm a bit concerned that you say enabling NAT killed your network. Do you have a Network card in the WinGate server that runs the Realtek 8029 Chipset? If you do then you'll need to enable support for this in the WinGate advanced options applet (Start-->Programs-->WinGate-->Advanced options-->Hardware specific).

Regarding the problem website, if it requires the users to login using NTLM authentication and you're making a proxy connection, IE6 won't present the login box. As soon as it sees the proxy setting it stops the authentication process. So you'll need to use either a NAT connection or the WinGate Internet Client and leave the proxy settings blank.