eEye Digital Security

This issue happened occurred a couple of weeks ago after an update to the client and after my brother in law used this computer.  I have Blink on another system that has been working fine.  My guess is that there was some sort of pop up message while he was using the computer and he answered it wrong and is blocking all internet traffic.  I just can't find that setting.  Either that, or something in the update that happened at about the same time is causing this problem.

Did you try a fresh reset of the configuration (this will wipe any firewall rules and restore it to what Blink had when you first installed it) by going to the "Tools" menu and then selecting "Reset Configuration"?

Exact same thing happened to me.  A reboot corrected the problem.  Doesn't make sense though.

I have been fighting this same thing for a few days now. From what I can tell, everything works fine when the computer is first turned on - only after the computer has been running for several hours (sometimes idle) do I see this problem. It appears that Blink is denying all outgoing network traffic, regardless of Application Rules. I know this to be the fact because of the event logs - they show the TCP requests and the action as denied.

In my case, at least, Firefox would not connect to anything unless I enabled the "Allow outgoing TCP connections to port 80 / 443" system firewall rule. Same thing for Thunderbird - I had to create custom system rules to allow outgoing TCP traffic to the ports the email client is using. True, a reboot corrected the problem, but only for a few hours until the problem resurfaced. The other alternative is to turn off the firewall, which I am not ready to do.

The problem with enabling the "Allow outgoing TCP connections to port 80 / 443" system rule is that it seems to overide any application rules. Basically, with that system rule enabled I no longer receive prompts when an application is attempting to connect to the Internet. Reseting to default configuration did not help, in my case.

If you ask me, this is a problem with eEye's latest update. Hopefully they can fix it so that I can crank my settings back up to full strength.

We are still trying to find out where the problem is. Please contact me at lnicula@eeye.com and will continue the troubleshooting.

 I just had a similar problem on an XP, SP3 machine.  No access unless I turned off blink. 

On a Win2K machine blink was using all of one CPU & wouldn't respond to any keyboard commands.  Plus a weird problem that I believe to be blink-related re-occurred (happend before on trying to get the version 3.x to 4.x upgrade installed): on rebooot after blink notice that update would be installed on reboot, Win2K machine showed hourglass for perhaps 30 seconds on the login (username & pw dialog).  Then let me on.  Last time this wait grew progressively longer until machine wouldn't take keyboard input - but Linux on same machine worked fine.  I have to use Win sometimes, ended up reinstalling Win on a new disk.

Like a previous post, I believe this is "upgrade" related.