Discussion in 'other firewalls' started by Nail, Aug 2, 2006.
126.96.36.199 beta full of bugs....;(
can anyone give link to jpf 188.8.131.52 beta?
Here we go:
But it will run only limited, because the internal lisenz expired today,
I had to reinstall Beta 15. Done so, and unusable. It's not interception any traffic, even the service and sys files are loaded. Absolute unusable
I used JPF 184.108.40.206 for some time now without any problems. However version 220.127.116.11 does not seem to work for me. Neither an upgrade nor a clean install could prvent that JPF completely blocks my network cards. The wireless card can not be found by the software any more and the normal lan card does not react in any way, e.g. can not be disabled. Network communication of any kind seems to be impossible. After log on the computer is very slow for a couple of minutes and after that time seems to be working normally, execpt for the network connections.
I had to go back to v18.104.22.168 but during unistalltion of 22.214.171.124 got stuck too. I had to shut down the computer per power button.
Maybe there is a kind of driver conflict or something similar. I have a VAIO Laptop with the centrino chipset, Intel 2200BG wireless card and Intel Pro 1000 LAN card, 2 GB RAM, Windows XP SP2 with current hotfixes.
The problem seams to be the new Network driver (NDIS miniport) which is not accepted by Windows XP.
Network - Lan - Properties
Even if i accept everything, after a reboot it comes again when i check the Network Properties.
It seams that Jetico recocnizes traffic as i can see because of the lamp icon in the configuration tab, but the network traffic tab shows everything as 0.
Jetico is not intercepting traffic.
Strange thing is that it worked some time before, but i had to restore an image and install Jetico 15 again, as Beta 10 does not work anymore.
Thanks Tommy. .
After I installed 126.96.36.199, I could not play Blizzard Entertainment's StarCraft. When the computer launched the game, the screen went dark and could not return to the desktop. Once I shut down the firewall, the game worked again.
In addition, Jetico asked me to let starcraft.exe gain indirect access to network and I accepted it. I think it is related to the issue.
Jetico 15 has big problems because of the new Network driver (NDIS miniport).
In my case the service is running, but after the GUI connects to the server exe, Jetico stops intercepting traffic. Only spontaniously blocking regarding my config.
Jetico askes for each process for indirect access twice when such acces is acomplished by the proccess. First time for a Hash caclulation, second for the access itself. Most applications do so. This should not the problem.
- Is your Jetico servic started?
- Does the Network traffic tab shows anything?
Yes, Jetico service is running. It was running when I tried to launch StarCraft too. And, the Network traffic tab has been working fine.
Do you mean that Jetico will ask for StarCraft for indirect access for the second time and I have to allow it to resolve my problem?
At the first time, when I experienced the problem, I shut down Jetico, launched the game, switched back to the desktop, and launched Jetico. I saw Jetico asking for StarCraft for indirect access. I aceepted it and thought that the problem was gone. However, it did not work. After a reboot, I went to the Indirect Access to Network table and saw there was a rule for StarCraft. Then, I shut down Jetico, launched the game, switched back to the desktop, and launched Jetico to see if anything happened. Jetico did not ask me anything.
The problem is that Beta 15 is so proplematic, that it is hard to tell what's the reason for failure. You are one of the lucky guys that had Jetico Beta 15 running. So for now, there is no solution i am aware of.
Finaly after checking whatever i got Beta 15 to run smooth as it should. In my case the catroot2 folder was broken, which has influence on the WfP and crypto sevice. This resulted into a uncomplete install of the NDIS driver of Beta 15. My god, i don't have a clue how this foler got broken and corrupted.
As it is official on the homepage i post it here:
2-November-2006 version 188.8.131.52 beta released.
[-] Crash on checking application activity fixed.
[-] Hangup and configuration file corruption after multiple drag'n'drop operations fixed.
Jetico Personal Firewall for Windows 2000/XP/2003/XP 64bit/2003 64 bit - 3625 kB
Services up, runs smooth and without problems. One bug still exist regarding the HASH of some applications. Could be triggered in my case by SSM and could be general related to third party security applications which hook or ad threads to processes like SSM.
This is normally the HASH for 'system'
I get windows error same as beta 15, when installing, (NOT A BSOD).
Had to install in Safe Mode again.
Everything else is working smooth with no other problems.
What kind of Windows error did you get?
It is from the BestCrypt Self Extractor.
If I uninstall and reinstall in normal mode I do not get the error.
184.108.40.206 beta is ready. Critical bugs fixed:
* Zero applications hash fixed.
* Hangup on playing video files (direct access to memory) fixed.
* System crash on UDP communications fixed.
* JPF network monitor driver crash fixed.
* More verbose popup questions in default configuration.
Unfortunately, x64 still hangs on popup messages.
Up and running so far without problems.
No problems on installation with Jetico 220.127.116.11
Everything is running smoothly.
Problems with 18.104.22.168:
My PC freezes after start-up and request for install global-hook or indirect access. Every restart the process is different and I need to turn off my PC on power switch.
I've got strange popup for Oprea requesting send(0) to remote address 0.0.0.0. In the log it appeared like: send to port 0, from local address 0.0.0.0 to remote address 0.0.0.0 and no mather what I pressed it apperaed again. I needed to restart my PC to stop this popup. I will ry to reproducee it, but it happened once.
Maybe the problem appears on dual core processors, because my notebook has Core 2 Duo. OS is Win XP Pro SP2.
Still a problem on my W2k setup with the Jetico2 server failing.
Installed onto XP o.k.
Jetico picked up the indirect access by NOD to Firefox
But shutdown of XP hung. With logging, I found this was due to explorer unable to "exit network",..... its a pity there is no "exit network" rule (which may confuse), anyway, allowing explorer "access to network" solved this slight problem.
Made a totally new installation from ground zero (perhaps it was really a time, after 3 years...) and had one conflict with Jpfv2 20017.
Jpfv2 was first software installed after WinXP. After that all other software installed ok, but video drivers. I have Ati Radeon X800 and tried to install Omega drivers (different versions) and newest Catalyst but all installations crashed the computer with BSOD at very start in actual driver install. I was able to install drivers only after uninstalling Jpfv2. And after that reinstalled Jpfv2 and everything went ok.
Besides that problem, everything seems to work nicely...
There seems to be an incompatibility between the Microsoft Virtual Machine protocols and the Jetico 22.214.171.124/17 protocols. When both are enabled for a network card on my system the card is completely blocked from the network after I reboot. It does not even get an internal address. or is identified correctly via ipconfig.
When I boot the system with Jetico deactivated, log in and then activate the Jetico protocol everything seems to work fine. The same is true when I deactivate the Virtual Machnie protocols, no problems with booting while Jetico protocol is active in this case.
However VMWare protocols do not seem to be a problem in my configuration.
Can anybody confirm this?
Have you enabled the "Debug" rules within Jetico2, to see if packets or programs are being blocked? (You will find a rule in each table, to "allow all" with logging, enable the rules, and reboot, if you still have a problem then there is a conflict, if you can connect after boot o.k., then check the logs to see what rules/ program access are required. (It is possibly a problem with some windows apps needing indirect access to network)
Separate names with a comma.