[chasdrury]

Hi

I have a BES 5 server on MS Exchange 2007... Everything email and MDS browsing is fine - when users us BB browser they are directed through the company proxy and have to authenticate, no problem. As soon as I turn on HTTP Authentication Support, the access to sharepoint intranet works, with username, domain and password, but then internet access through BB Browser always says authentication fails. The authentication for the proxy server are the same as for the sharepoint, ie their AD details....

If i turn the HTTP Authentication off, sharepoint breaks and internet works...

Help please!!

Chas

[James.Stallings]

When you flip the HTTP authentication switch, the BES is authenticating on behalf of the blackberry device.

If you add a rule to your proxy allowing the BES traffic through then your problem should be solved. However (with this method), you aren't forcing your users to authenticate with the proxy server since all the traffic appears to be originating from the BES so you can't track what users are browsing (I'm not sure if this is important or not in your organization).

If you want to force users to authenticate with HTTP authentication on then check out proxy mapping in the BES 5 admin guide.

[chasdrury]

Thanks - but I already have the proxy mapping for Http:// and https:// going to the proxy server as it works when they have no http authentication enabled...

Chas

[James.Stallings]

Hi Chas,

I'll see if I can replicate the issue in our environment.

[chasdrury]

Thanks James...

I also have another issue now but that's more users and there is another thread for it!

Chas

[pauuu]

I don't know if this will help you or not but the way we have our proxy mappings is to have the http://.* and https://.* as the last proxy listing so that they will work as a catch all for anything that isn't internal.

As the proxy mappings works in a priority order (top to bottom) we simply put any local domains above these listings and set them to direct. This way the user will be prompted to log in for the local domains (i.e the sharepoint site and any intranet pages) and everything else it will look to the proxy server for with the authentication details we have put in.

[chasdrury]

Originally Posted by pauuu

I don't know if this will help you or not but the way we have our proxy mappings is to have the http://.* and https://.* as the last proxy listing so that they will work as a catch all for anything that isn't internal.

As the proxy mappings works in a priority order (top to bottom) we simply put any local domains above these listings and set them to direct. This way the user will be prompted to log in for the local domains (i.e the sharepoint site and any intranet pages) and everything else it will look to the proxy server for with the authentication details we have put in.

Thanks for the tip - that's identical to my set up!

Chas