[mjpringles]

Hi Guys,

I upgraded our BES to 5.0 SP2 from version 5.0 SP1 MR2 and all was good.

However I'm now a week on and all my users are screaming that Internet access on the handhelds has stopped working.

They all get a Connection Timed Out message on the handheld.

I have checked that the BES can get to the Internet on the server and I can't see anything in the logs that indicate an obvious problem - that or I'm not looking at the right logs! (I'm checking the MDAT logs)

Email is working fine apart from the usual people on holiday have pending messages queued.

Has anyone else encounter this problem since applying SP2?
Any sugesstions on fault finding this would be greatly received

Thanks

Mike

[RadHaz75]

is the mds-cs service running in windows?
does the bes the users are on still have an mds server associated with them?

[mjpringles]

The MDS Connection Service is running and under MDS Connection Service in component view I can see the instance associated with the BES.

[CyphrMedic]

Under the instance associated does it say connected or standby?

[mjpringles]

Under Instance status it has the status of running

[CyphrMedic]

check your MDAT logs for anything that shouldnt be there.

[mjpringles]

I've checked the MDAT logs and can't see anything out of the normal.
I'm going to build another Windows 2003 server and install BES Monitoring on it - hopefully it will show me what is wrong.

[mjpringles]

Hi Guys,

Well after 4 days of pulling my hair out I have found the solution to the problem!
It turns out that when you install SP2 by default it turns on the following options:

Use Scalable HTTP
Use Scalable Socket Connections

If these two settings are enabled it turns out that BES will not play nicely with WebSense 7.5 and ISA 2004 as a proxy server.

As soon as I turn these two settings off and restarted the MDS services bingo Internet access on the Blackberries starts working again.

Thanks CyphrMedic for you help

[CyphrMedic]

no prob glad you got it working.

[noname]

No wonder, in the Admin Guide it says:-

" By default, the BlackBerry® MDS Connection Service 5.0 SP2 or later uses scalable HTTP, which permits the BlackBerry MDS Connection Service to use fewer system resources and to establish more socket connections at one time than previous versions of the BlackBerry MDS Connection Service. When a BlackBerry MDS Connection Service uses scalable HTTP, it streams data to and from BlackBerry devices instead of storing and forwarding the data. If you want a BlackBerry MDS Connection Service to process data as it did in previous versions of the BlackBerry® Enterprise Server, you can prevent a BlackBerry MDS Connection Service from using scalable HTTP. "

Very bad to just built-in by default, keep all of us in the dark, wasted many support hours and lost many hairs. They should just leave the default as disabled and let us decide the settings. Very similar to my country's "opt out" systems in many of gov policies, we are forcefully default to "opt in" in various policies and if you want out, you gotta take effort to "opt out". Now's that a real life analogy

[incognico]

Thanks, same symptoms, same fix.

[galeb]

I do not want to open a new thread, since I have a similar problem... and here is what I did:
(after I read a lot of posts on the similar matter):
Use Scalable HTTP - set to No
Use Scalable Socket Connections - set to No

Changed the http port on the BES to 8090 (tried with several combination of the proxy settings below, with both default 8080 and 8090 settings)
Tried with:
- no proxy settings,
- direct proxy settings
- proxy pointed to the proxy script

I even had the admin set the firewall (ISA 2006) to bypass the content filter
for anything originating from the IP address of my BES.

No luck, still getting the same error.
I can access the web b using web'n'walk browser (T-mobile carrier).

What am I missing? (hair, I know, I pulled it out... )

Thank you,
Hrvoje

[mjpringles]

Hi Hrvoje,

Stupid question time:

In IT policy under Global have you set Allow Brower to yes and what options have you enabled under Browser?

Regards

mjpringles