Hello,
Sunday, June 1, 2003, 6:43:03 PM, you wrote:
DJ If I shutdown ZoneAlarm, TB works fine. Now, I could think it is a
DJ problem with ZoneAlarm, of course, except that it does not happen
DJ with any other program (that I use) and it didn't happen with the
DJ previous version of TB.
You
On Monday, 2 June 2003, at 7:48:39 a.m., DZ-Jay wrote:
Hello: I recently upgraded from the bat v1.61 to 1.62 and I
encountered a problem (BTW, great program! still evaluating but plan
on registering soon!). If I have ZoneAlarm running and try to do
any TCP operation from The Bat!, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kenneth S. Rhee [KSR] wrote:
KSR You might want to upgrade to ZA 3.x. I have been running the ZA Pro
KSR 3.x and now 4.x beta, and haven't had any problem with it.
This seems to be a cat and mouse thing. Those having problems with the
later versions
Hello Allie,
On Sun, 1 Jun 2003, at 18:23:29 GMT -0500 (6/1/2003, 6:23 PM -0500 GMT
here), you wrote in mid:[EMAIL PROTECTED]:
AM Let's see what happens with v4 when it's released.
I'll watch and see what others experience with v4, but after my
experience with v3 that is about as far as I'll
Some time around 6/1/03 19:10:54, I think I heard Allister Jenks say:
:: It sounds like ZoneAlarm already thinks it knows the program (how
:: would be an interesting question). Have you checked through all the
:: program definitions in ZoneAlarm to see if there is an entry that
:: could be
Hello DZ-Jay,
Sunday, June 1, 2003, 2:48:39 PM, you wrote:
DJ Hello:
DJ I recently upgraded from the bat v1.61 to 1.62 and I
DJ encountered a problem (BTW, great program! still evaluating but plan
DJ on registering soon!). If I have ZoneAlarm running and try to do any
DJ TCP operation
Some time around 6/1/03 18:43:03, I think I heard Allie Martin say:
:: -BEGIN PGP SIGNED MESSAGE-
:: Hash: SHA1
:: - From my personal experience, as well as the experience of quite a few
:: other TB! users, when ZA starts being problematic with TB!, this heralds
:: the onset of other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dz-Jay [DJ] wrote:
DJ I am sorry, but I cannot accept the (now common) solution of
DJ ignoring the problem and trying a different firewall.
You don't have to. I wish you good luck then. :)
I really hope that it continues to be problem free for you
Hello Allie,
Monday, June 2, 2003, 2:16:02 AM, you wrote:
AM Dz-Jay [DJ] wrote:
DJ I am sorry, but I cannot accept the (now common) solution of
DJ ignoring the problem and trying a different firewall.
AM You don't have to. I wish you good luck then. :)
AM I really hope that it continues to be
Hello DZ-Jay,
Sunday, June 1, 2003, 6:13:31 PM, you wrote:
I rolled back to the previous version of TB (1.61) and everything
works fine again.
I started having problems with ZA using TB (1.61). shrug
Thanks,
Terry
Current version is 1.62r
To all of you having problems:
just for the fun of it, enable port 113 tcp incoming (identd
authentication) or set it to reject. Some mail servers might try to query
identd and wait for the timeout when there's no response.
This has helped my with my primary mail server and Kerio PFW.
Roman
11 matches
Mail list logo
