Nev wrote:Not Logan, not quite ½ as useful but I'll try.
You should give yourself more credit Nev :).
Andyt3e wrote:Will this allow remote access on wireless mahinces as I know that you can lock this out on other programs ?
Could you clarify what you mean by remote access on wireless machines?
Andyt3e wrote:How good is the firewall that si built in to wingate?
It's a stateful packet inspecting firewall (SPI), which means it not only blocks/allows packets, but it also keeps a track of TCP sessions and can discard bad packets even if that port was allowed. The firewall also stays active even if the WinGate engine is stopped or crashes for whatever reason, so you're not left with an unprotected network.
Andyt3e wrote:Do I have to use Kaspersky AV for Wingate or can I use my own Firewall and Av?
You have to use an AV plugin developed specifically for WinGate, so that rules out using any ol' AV suite. Your two options are; Kaspersky AntiVirus for WinGate, or Dr.Web for WinGate.
Kaspersky AntiVirus for WinGate is the AV product developed in house and licensed from Kaspersky Labs. However it is based on one of their older engines which is showing it's age. A new version of KAV based on the latest engine from Kaspersky Labs is in development.
Dr.Web for WinGate is a third party product developed by Dr.Web themselves. I haven't tried it myself, but it sounds like a good product. Their website is
http://products.drweb.com/gateway/qbik/Both these products have free trial periods, so I recommend trying them both and deciding which one you like better. Obviously, don't install them both in the same WinGate installation at the same time though.
Andyt3e wrote:If I can use my own versionn of Firewall and AV do I have to disable Wingate firewall or can both run along side each other on the proxy server?
WinGate would run alongside a third party firewall, but it's not recommended because it makes administering the firewalls complicated. Anything you do to one firewall has to be done to another. Do you plan on using WinGate to provide NAT access for the client computers on your network, or do you just want the WWW Proxy service? If you just want the proxy service, then I think it's reasonable to disable WinGate's firewall and use your own firewall if you want, but if you want to use WinGate for NAT, then I recommend using WinGate's firewall and disabling any third party firewalls.
If you're running an antivirus suite on the WinGate computer (not an AV plugin for WinGate, but a personal AV suite), then make sure it's configured so that it does not scan the WinGate engine or the WinGate directory. WinGate constantly handles files in it's directory, so having an AV suite trying to lock and scan those files all the time puts a bit of a performance hit on WinGate.
Andyt3e wrote:We have a BT bussiness router at this point in time which is configuered to work with auto IP on the client end can I keep the auto ip (wingate server has auto ip) or do I have to use static IP and get the wingate to use DHCP for all users connected to it?
If you're not planning on using WinGate for NAT, then you could leave the BT router doing DHCP for the network and simply configure the clients to use the WinGate server as their proxy.
If you are planning on using WinGate for NAT, then you would be better off disabling the BT routers DHCP service, configuring WinGate with a static IP and letting WinGate handle DHCP for the network.
We uploaded a video to YouTube recently that briefly demonstrates installing WinGate and getting DHCP, DNS and NAT working out of the box. You might find it interesting to watch before embarking on setting up your own test network.
http://www.youtube.com/watch?v=KKaEVQe3nwUIf you have any further questions, let us know.