Protect my system before Wingate has started...

[n0ticer]

i like this feature, so i ticked the thing, reboot... but when i check what i ticked its unticked. why?

[erwin]

Hi NOticer

Thanks for the feedback
Your certainly living up to your name this week.
This is a known gui glitch in this release.
The protection is still provided and functional by the WinGate driver on startup.

The gui glitch has been fixed (so the tick will stay after reboot) in the next release.

Regards
Erwin

[n0ticer]

tnx for all the replies...

i wud also like to include, that other apps behind & within wingate that may require online updates fail to connect.

apps behind wingate that cuddnt connect:
1) *Ad-Aware <-- can connect if within the wingate server
http://forums.qbik.com/viewtopic.php?t= ... ht=adaware

apps within the wingate server that cuddnt connect:
1) *CWShredder <-- can connect if behind LAN

*note that these apps can do updates in ver 5.2.3 & lower

[adrien]

Is this in the situation where WinGate has not started but is still protecting the PC?

In this case, WinGate allows outbound connections from the WinGate PC itself, but all inbound traffic will be blocked.

Therefore this option should not be used if WinGate is not going to be started automatically, since your machine will be unavailable until WinGate has started.

Adrien

[n0ticer]

Is this in the situation where WinGate has not started but is still protecting the PC?

nope. this (the blocking) happens when wingate has started. if u cud try installing Ad-Aware & Cwshredder on w/s & server & do updates, u'll see :) tnx

[Mickey]

I think that Security StartUp should be on External adapter ONLY.
Internal NIC should work normal to take a remote sesion on startup from LAN etc
External Interface (to internet)should be started after WinGate Start.

[genie]

Unfortunately before the engine starts the driver has no knowledge about interfaces roles - all interfaces are equal - the engine then says that this interface is external, while this one is internal. That is why we decided to block all incoming connections while allowing outgoing ones.

[Mickey]

Unfortunately before the engine starts the driver has no knowledge about interfaces roles - all interfaces are equal - the engine then says that this interface is external, while this one is internal. That is why we decided to block all incoming connections while allowing outgoing ones.

But after first start of Engine the driver can write in registry which interface is internal and which external and after next rebot it is possible to block only incoming traffic on external interface and allow in/out on internal interface :)

[genie]

Absolutely and we will probably add this feature to the next release - but it is not 100% reliable, unfortunately - some systems do not report interface names, so we will need to make some assumptions if the name is not found.

[n0ticer]

nice input there Mickey :) sounds like ur using sygate ;)