[BESXAdminDMB]

Hi All

I hoping someone on here can help with with this... it's driving me insane!

We are running BES Express 5 SP2 with Exchange 2007 and ISA 2006.

Users can access the internet from their BB's using both the Blackberry Browse and Internet Explorer, however they cannot access our internal Sharepoint sites through the Blackberry Browser. I've been through nearly everything and am still no closer to getting this fixed!

I've enabled 'HTTP Authentication Support Enabled' - (set to Yes)
I've edited the 'krb5.conf' and 'MdsLogin.conf' file so it points to our domain
I've added a new URL to the Proxy Mappings to point directly to one of our internal sites and set it to PAC and added in our PAC file address

However when i try and access the site it fails!

I go to our internal URL using the BB Browser > it prompts for authentication (e.g Username, Password and Domain (already filled out) > Click on Contiune and it fails with HTTP 500 Internal Server Error (Error - The Requested Function is Not Supported)

I've done a network capture off our BES server and can see it hitting our proxy then failing with an IIS error (you are not authorized. access denied).

Looking at our Sharepoint IIS logs, i can't see anything hitting the servers. So i don't think it's a Sharepoint issue.

Can anyone assist with this. This is driving me mad

[BESXAdminDMB]

OK. I've found this article on the Blackberry forums (could not find this by searching on sites... no matter what i typed in)

Cannot post URL's until 15 post!!!! What a stupid rule
Do a search on BlackBerry Knowledge Base for article KB24270

Put simply. If your Sharepoint servers have NTLMv2 enabled, you going no where. BES 4 through to v5 SP2 will not support NTLMv2

"If NTLMv2 session security option is enabled, BlackBerry smartphone users will be unable to authenticate as negotiating extended session security is not currently supported."

I have a call open with RIM to try and find more information. I find it strange that a service like Blackberry will not support NTLMv2 when this has been around since NT4!!!

Hope this helps some people