0 commentsISA 2006 and BlackBerry Enterprise Server
I recently was required to install BlackBerry Enterprise Server (BES) on our corporate network. I did the usual configuration following the step that I found on the BB site here.
I then proceeded to make an ISA Firewall Rule that enabled outbound acccess from the bes server (a computer object) to external on port 3101. I also created the corresponding inbound rule on port 3101 as well just to be extra sure.
I followed the steps word for word (or so I thought), and tried syncing a BlackBerry to the servers, and it just timed out on me. So then I went back to the drawing board, and realized that I didn’t setup my permissions on the Active Directory (AD) user accounts properly. So I uninstalled the server, followed the following steps:
And reinstalled the server. Still no avail. I looked into the logs and noticed this line in the BES_DISP logfile:
IPPa] {User Name} Forwarding status to BES Agent (S61887304_001), intTag=5, extTag=1
[30222] (03/20 16:20:19.482):{0×898} {User Name} MTH: contentType=OTAKEYGEN, sizeOTA=216, sizeOTW=216, TransactionId=-941432706, Tag=2
[30310] (03/20 16:20:19.482):{0×898} {User Name} Forwarding internal data to device, contentType=OTAKEYGEN, routing=S61887304, device=301D4AC4, size=258, cmd=0×3, ack=0, TransactionId=-941432706, intTag=8, Tag=2, Submit=1
[30375] (03/20 16:20:19.576):{0×8A0} {User Name} Packet returned as FAILED – could not be delivered to device, Tag=2
After doing some research, I found out that you NEED to have the BES option on your phone which can only be set by your carrier. To find out if you have this or not, just go to options -> advanced settings and see if theres an option for Enterprise Activation anywhere. If there isn’t, that means that you do not have the BES package. To get this, just phone your carrier, and ask them to add BlackBerry Enterprise Services (BES or pronounced B’ezz) to your account and you should be good to go!
Brennan