ENS Firewall Blocking Incoming Connection (Dial In)

[cb_oz]

After recently rebuilding a Wingate 5.2.3 server I added a Win XP 'incoming connection' after the setup and configuration of both WinGate and ENS incl Firewall.

Since adding the incoming connection the Internet to WinGate firewall settings are effective on this interface, previously this was not the case. I can't see this interface in 'Advanced' so I am unable to change the interfaces pubic/trusted status.

How can I convince ENS Firewall that this interface is a trusted (i.e. local) interface? Therefore applying the LAN to WinGate Firewall rules.

[neil]

WinGate should see this interface, but it all depends on your routing table really. If you do a 'route print' can you see the IP assigned to this modem (waiting for incoming connections)? If so WinGate should see it as well. If not (in the routing table) then connect in with another modem, and that should force windows in to displaying this route in its table. Once this has happened you may need to restart the WinGate engine, and it should now appear in Gatekeeper, under Options - Advanced - Network Interfaces.

Regards

Neil

[cb_oz]

Neil,

Firstly, thanks for the advise so far...

I hadn't chased this up as it was a low priority... that is until now. :-)

The interface does not appear in "ipconfig" or "route" until a conenction is established. Once established WinGate also see's this and I was able to change the Adavanced settings and tighten up the firewall for internet access once again. This worked fine for this one connecton, then every subsequent connection appears to impose internet to WinGate firewall restrictions. I've tried the above twice to no avail.

Can you suggest another way of securing these settings? It is a remote site and difficult to access so I am keen for a fix.

[ingjoelsito]

Hi, your Remote Access Server, is Win2k or WinXp, thats is important for correct settings.