This issue came out of some work that had happened for a client. The initial problem was exchange permissions and the task that resets ACLs for users who are members of protected groups. Prior to this it was possible to log in on the bes administration service on port 3443 on the mail server. However it was not possible to assign devices to users – hence the research into the problem.
However in “fixing” that problem which allowed access to the user mailboxes of the blackberry users – suddenly the web page for the administration of said users was no longer available. Looking in the blackberry log files led me to errors such as “failed to start protocol stack” making me to think that something was perhaps blocking the service from binding to that port (3343) or something similar.
I had a similar problem some time ago when a bes install showed that the port required for BES admin was in use by another bespoke application and it required a change to the configuration to use port 663 – which it has done successfully since then.
Please note that what follows is at your own risk and should only be carried out if you are confident that you can undo this if required. Backup your registry nefore doing anything like this.
However I remembered something about reserved ports and investigated this registry key as follows.
Click Start, click Run, type regedit, and then click OK.
Locate and then click the following subkey:
Right-click ReservedPorts, and then click Modify.
Paste the following at the bottom.
Now restart the server.
Note – in my case the ports
1433-1434 and 3343-3343 were already in the registry key !!!
** These port numbers came from a previous support incident with RIM and may not be appropriate for your server or environment – you may wish to do these one set at a time and reboot in between to check which resolves your issue **
Hope this helps you if you find yourself in the same position.
Postscript …. this article may be whats happening !!