[CBR900RR]

OS 4.3 should be out before end of this year and you can put you BB back to the orginal state.

Just uploaded a new version of JL_Cmder!

Now includes the resettofactory command. This command removes the IT policy from the device (OS 4.3+ required). Also note that after the resettofactory command has been run the device must be wiped. Backup your data first!

[tgray]

As FYI.

I pushed a blank ITPOLICY to my BlackBerry 8310 and was UNABLE to change the Firewall setting to Disabled.

I have a new BlackBerry 8310 that has never been on the BES. The device is new and direct from AT&T (not a warranty replacement). The firewall is set to Enabled and I am unable to change it to Disabled.

[John Clark]

Just an IT policy will not change the firewall settings once it's been connected to a BES.

Did you connect your 8310 to the same Desktop Manager that you connect your other 8310 to? If so, it's likely you have the same policy on the new 8310 now.

[tgray]

*Removed my comments because they didn't make any sense.*

Sometimes I just get too excited when I post on here!

[John Clark]

Huh? You lost me.

[toemaytoe]

I've had the same error message for months now but I get it with mobipocket. I haven't been able to use mobipocket for some time. I'm also on their forum but they haven't been able to come up with a solution. I personally think that the problem started with my upgrading of my OS to 4.2 I've noticed problems with several other programs as well. I'm hoping that 4.3 comes out soon and solves these issues. Is there any word on when it will be released?

[tgray]

Well crap.

I ended up replacing my BB because I couldn't get the firewall issue to resolve itself and JiveTalk wouldn't work.

So today I plugged in my BB to my laptop where I had already configured the registry to point to the blank policy.bin file. And what happens?....

It forces the new BB to have an enabled firewall with no way to remove it! GRRRRRR. I should have removed the blank policy.bin! Now I'm screwed again!

[tgray]

Okay...

I downloaded a new copy of the policy.bin file (the one John Clark is hosting). It seemed to be less restrictive than the one that was originally hosted on ig3.net. I followed the instructions John provided and now, thankfully, the split pipe connection value seemed to have fixed my JiveTalk issue for now at least.

Thanks for providing the policy John. I still cannot change my firewall back to disabled yet, but maybe by the time I find the next app that requires it to be enabled, I will have a new device.

[spiggy]

Hi all

Got myself a Jivetalk license afterall, but after some minutes of inactivity, I get an 401 Unauthorised message. Suppose it is related to the proxy, cause when I browse to a new webpage wit the BB browser, all is ok for some minutes again.

I'm after a BES. Can I solve this in the proxy policy ?

Thx. Have a nice weekend...

Peter