Well I've tried almost everything I can see through the program, even went to help which said to reset my firewall. Nothing changed the fact that I get this error:

"Jivetalk has tried to initiate a connection inside and outside of the firewall. This is prevented by your firewall or check your IT policy" but I have set Jivetalk to allow for all settings, even reset my firewall, and did a soft reset. I cannot get it to work.

Any ideas?

Do you have an IT policy from your corporate BES?

Options > Security > General Settings > scroll to bottom, what "Services" are present?

Oops, forgot to mention..no IT policy, not on BES.

I'm on BIS, self-owned device, never any previous IT policies either. :(

Then do this (if you checked security like suggested and no IT Policy is there):
--make certain your firewall is set correctly and permissions ALSO in Options > Advanced > Applications > Jive Talk > Edit permissions, etc. set as you need. Make sure your firewall is still disabled.
--pull the battery of the BB to reboot
-- try again. Sometimes certain settings are in the memory cache and do not reset until a reboot.

Otherwise, deleted JT and reload from start.

Well on firewall, it says enabled w/ a small lock icon near it. I don't know why, I was never on a BES.

I deleted and reinstalled JT, and still the same damn error. I even let it set its own parameters for everything

checked again in security -> settings -> services

it says: *** no services ***

bump because Cingular/ATT doesn't have a clue as to why i have a locked firewall with no it policies listed, and neither does RIM...they just sent me a policy.bin and said i should clean wipe & put this policy in the folder just like the walkthrough says here.

thing is, i tried this already with the policy.bin from here on bbf, and it didn't work.

so I guess no one has any other ideas?

What gives you that idea?




Honestly, at this point, you may need to wipe the device and reload your OS to get rid of whatever is causing the issue.

I did wipe it, and reloaded everything. Still locked firewall with nothing in services, so I called and requested warranty exchange, should be here in two days.

got the new BB, still has a lock on firewall setting. wtf?

does any1 else have this lock as well? go to options, security, firewall. let me know if your able to change default option.

I've been looking on the 'stack as well, people are having this problem more and more frequently. I've had two Curves' so far, both with the same stupid forced firewall.

should I just give up? or will reloading the OS fix this?

policy.bin did not. new device through warranty exchange did not. i'm just ready to give up but opera 4 beta won't work nor will send file feature in jivetalk.

I hope you didn't install policy.bin on the new BlackBerry (i.e. you deleted the policy.bin before connecting USB cable to the new BlackBerry). If you did, you just lost some featuers on your BlackBerry permanently. Such as the ability to use Bluetooth keyboards.

policy.bin is a last resort only, and actually damages the capabilities of "virgin" BlackBerries.

so why do they give it out like that?

RIM/ATT needs to get their damn act together, how the hell are 25% of curve's being sent out with perma-locked firewalls? AND NO FOR THE 1000TH time, neither phones were on BES!

all of my other Curve using buddies have unlocked firewalls except for me. this is getting really really annoying, and i'm honestly thinking about just getting rid of this device.

Did you ever get this resolved? I'm one of those guys with a BRAND NEW 8310 with the little red lock on Firewall. No IT Policy - Brand new BIS device. I've never used a policy removal tool as I've never had a policy on here.

I've even checked if BIS can do this, and the answers I've gotten are "no".

If you have made any progress, no matter how difficult, I need to get this resolved. Thanks for your help!

For my Curve 8310 w/ AT&T...

As info, I downloaded the one for “OS 4.3 or OS 4.2 (8100 Pearl, 8800 Series, 8300 Series, 8700 Series with 4.2 OS)” from your website. This is the one causing me problems.

I then tried installing the one “OS 4.1, versions 4.1.0.309 Or Later (8703, 8707, Other Models - Check Your OS)” and it works fine.