Hi,

I'm runnning win XP sp2 on a dell latitude d800 with zonealarm pro 6.0.667.000

I had a couple of glitches during install similar to those reported in other threads, but everything installed ok in the end and could connect via sqlplus, db instance verified as up and running.

Clicking on "Go to database start page" from the start menu, brought up logon page and if incorrect details entered it gives error message (as it should), but if you enter correct credentials it just comes back to logon page.

Turning off ZA Pro and repeating process, I can logon OK and get to home page. As far as I can see, I've allowed all oracle XE related services and apps access to trusted and internet zones.

Any ideas? I don't want to leave firewall disabled, and turning it on/off to use XE is impractical too.

I have the same problem - keeps going to the login prompt if ZonaAlarm is running, works fine if I shut it down. I enabled cookies for the local site (127.0.0.1) but that didn't make a difference.

Paul

Hi,

I have done some research and found a working solution (for me).

I have downloaded the latest version 6.1.737.000 (english version).

First I installed just the basic (free) version of ZoneAlarm, no problems there. XE worked just fine.

Then I upgraded to ZoneAlarm Pro and immediately I had the problems as described above.

The problem is definitely due to blocked cookies from localhost.
There are numerous posts on their support forum regarding this issue:
http://forum.zonelabs.org/zonelabs/search?q=cookie+localhost

It seems to be a bug in ZoneAlarm Pro. It identifies the cookies as 3rd party cookies and therefore blocks them. Adding 127.0.0.1, localhost or the local ip address to the site list (privacy tab) won't work either.

The only way I got this working was to set the following configuration options:

Privacy > Cookie Control => OFF

Privacy > Ad Blocking => OFF

Does this workaround work for you as well?

~Dietmar.

Dietmar - vielen danke!

That sorted it out.

Dietmar,

I am also running ZA 6.1.737 - while your solution does work, I don't se it as being any more viable or convenient than just shutting down ZA while I log onto XE. From the threads you pointed out, I think we all need to complain loudly to ZoneLabs to get them to fix this.

ZoneAlarm Workaround II

Mark, your suggestion worked out!

I changed the privacy settings back to Cookie Control: HIGH and Ad Blocking: HIGH.

Then I restarted the browser and accessed XE via

http://192.168.0.5:8080/htmldb  or

http://daust2.opal-consulting.de:8080/htmldb

Both worked (local ip address and fully qualified name)!

Only http://127.0.0.1 and http://localhost have problems.

Suprisingly, when I used 192.168.0.5 this ip address would get automatically added by ZoneAlarm to the list of exceptions for the cookie control (Privacy > Tab Site List).

Now we all should be happy camper once again .

~Dietmar.

P.S.: But I am still suprised that ZoneLabs hasn't fixed the problem since it seems to be known for a year by now and many many people have problems with this (Zope, PHP, ...)

Hi,

check the threads on the ZoneLabs support site, seems to be a well known issue as well

http://forum.zonelabs.org/zonelabs/board/message?board.id=access&message.id=20909#M20909
http://forum.zonelabs.org/zonelabs/search?type=Message&q=Cisco+VPN&page_size=20

Regards,
~dietmar.

In the current beta 3 there is a check whether cookies are enabled or not.
If they are not enabled, an error message is displayed.

This is good!!!

I haven't checked with ZoneAlarm pro yet but the problem should still persist since the default URL is http://127.0.0.1:8080/ which is (unfortunately) not recognized by ZoneAlarm to be the local machine.

At least this gives us a hint as to what we have to look for (i.e. cookies).

Using the url with the local hostname or the ip address directly should work as described earlier.

~Dietmar.