Wingate 5.2.2 - Problem getting ENS to work

[nick_mcruk]

I am running WIngate 5.2.2 on a Win 2k Server, using a dialup broadband connection. When I enable the extended network driver, no client machines can access the internet. In the firewall log, every request seems to be blocked from each client. I tried disabling the wingate firewall, this stopped the firewall logs, but still didnt allow clients to connect. We have had our Win2k support person take a look, but he is not very familier with wingate and could not manage to solve the problem.
With the ENS inactive, the clients can all get access but obviously I want to get the firewall back online asap.

Thanks in advance for any help.

[genie]

Make sure that the properties of the interfaces are correct (internal/external).

[adrien]

Hi

Depending on what IP addresses you use on your LAN, WinGate makes an assumption about which interfaces are external or internal. For instance if you are using public IP addresses, then WinGate may have set your LAN adapter as external, therefore blocking everything.

Private addresses (for use on internal networks) are defined as:

192.168.X.X
172.16.X.X - 172.31.X.X
10.X.X.X

If you are using any addresses other than these, then check in GateKeeper under Options->Advanced->Network Interfaces, and make sure that the IP address of your LAN adapter is marked as trusted.

Adrien

[nick_mcruk]

Hi,

I have checked the network properties in GateKeeper under Options->Advanced->Network Interfaces and it is setup as follows:

BTOpenworld (internet connection) Public:yes Trusted:No
127.0.0.1 Public:no Trusted:yes
192.168.0.2 (the server IP) Public:no Trusted:yes

All network Clients are allocated IPs in the range 192.168.###.###

[adrien]

OK, the next step would be to check the Port Security settings in the ENS.

Make sure that the ports you are trying to use are allowed on "Lan connections to WinGate PC" and "LAN connections to the Internet"

watch out for the default action as well, if you don't have a specific rule allowing a port, then the default action will apply. Check also UDP. You will need to be able to access ports 137 and 138 UDP plus some others for normal Windows networking.

Adrien