Link to home
Start Free TrialLog in
Avatar of gfsupport
gfsupport

asked on

Cannot load Blackberry Web Desktop Manager website from user machine

Hi Experts,

I am unable to browse to the Blackberry Web Desktop Manager on computer within the network.
I am able to browse to the Blackberry Web Desktop Manager on the server where BES Express 5.0.3 is installed.

I have added the site to the trusted site and have tried as a local admin. I have also reset the IE settings and have installed Firefox.

All of the services (BB, SQL) are started and the server console are working fine.

Please can I have some instruction on what to try as I need to activate a phone through the Blackberry Web Desktop Manager.

Thank you
Avatar of jerseysam
jerseysam
Flag of United Kingdom of Great Britain and Northern Ireland image

Have you ensured that you have given user rights to do so through the Blackberry Admin Service?

See:  http://docs.blackberry.com/en/admin/deliverables/14334/Permit_users_activate_devices_using_WD_432367_11.jsp
Can you reach the site at all or is it that you just can't logon to it?

Can you reach the BB Admin Web Console from a remote computer?

Check the firewall on the BESX server to make sure that port 3443 isn't being blocked.  Typically the URL for the BlackBerry Web Desktop Manager is something like:
https://blackberry.domain.com:3443/webdesktop/login
...though it could also be on 443.  You can see which port by running the BB Server Configuration and looking under the "Administration Service - High Availability" tab > the HTTPS entry, or just by looking at the shortcut that is created on your BESX server.
Avatar of gfsupport
gfsupport

ASKER

Thanks footech:
I am not able to reach the site from any computer on the network. I can from the server and log in.

I am using the same address,
The port is 3443 and I have confirmed this in the BB server configuration
I have turned off the firewall and have allowed port 3443 to allow connections
ASKER CERTIFIED SOLUTION
Avatar of gfsupport
gfsupport

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
finding out which IP address was listening to the port was the key factor in resolving my problem