is this a blockhole problem?
Jan 30 08 6:08 am
qbik team...
in gatekeeper when i right-click a user there is an option to blockhole him or her... but in ENS option blockhole option is not present. i think it's not present becoz im using an old license key, right?
my question is, if i accidentally blockhole a user, how do i unblockhole him? if this is a glitch, pls have it fix on next version. tnx
in gatekeeper when i right-click a user there is an option to blockhole him or her... but in ENS option blockhole option is not present. i think it's not present becoz im using an old license key, right?
my question is, if i accidentally blockhole a user, how do i unblockhole him? if this is a glitch, pls have it fix on next version. tnx
Re: is this a blockhole problem?
Jan 30 08 8:10 pm
Hi,
If you open the ENS there is no IP Blackhole option in your version?
You can upgrade to V6.2.2 with your current licence with the same features as your current version.
If still no luck you could look in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\Components\WinGate Network Driver\IP Ban Table\
All precautions apply about editing the registry!
If you open the ENS there is no IP Blackhole option in your version?
You can upgrade to V6.2.2 with your current licence with the same features as your current version.
If still no luck you could look in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software\WinGate\Components\WinGate Network Driver\IP Ban Table\
All precautions apply about editing the registry!
...
Jan 31 08 1:04 am
nev,
ip blockhole is not present, im on 6.2.2
yes, registry is the only option...but ip blockhole should be or shouldn't be available in old version license? which is which :)
ip blockhole is not present, im on 6.2.2
yes, registry is the only option...but ip blockhole should be or shouldn't be available in old version license? which is which :)
Jan 31 08 10:52 am
Hi
Looks like you spotted a bit of a loop-hole. I think a version 5 or later licence is required for black holeing, but we check it in the GUI, and looks like we omitted to remove the option from the context menu.
So the registry will be the only available option to remove the black hole entry.
Regards
Adrien
Looks like you spotted a bit of a loop-hole. I think a version 5 or later licence is required for black holeing, but we check it in the GUI, and looks like we omitted to remove the option from the context menu.
So the registry will be the only available option to remove the black hole entry.
Regards
Adrien