[tankee531]

hi,

I am unable to surf via the blackberry browser. Whatever url I tried, I will get the http error 400 (unknown host). The port number is 80 (<- is this port number correct, if not where to change?)

I am able to surf via WAP which is linked to my telco's GPRS WAP services.

I have the following service book
- WAP Transport SingTel (WAP)
- SingTel IDEAS (Browser Config)
- Blackberry Browser (Browser Config)
- Blackberry (Browser Config)
- Blackberry (IPPP)
- Blackberry (ALP)
- Blackberry (CMIME)
- Blackberry (CICAL)

I used to be able to surf via my old BB device.

what could be wrong? :(

[tankee531]

by the way, I'm on BES and MDS is enabled at the corporate blackberry server.

[mbn]

I get the same thing (actually mine is.... "HTTP Error 400: Bad request The server could not understand the page request, or was unable to process it for some reason. Please try loading a different page.")- I've asked the same question to this and other boards but didn't get a response. Then all of a sudden, last night my Blackberry browser was working, but today, HTTP Error 400 again. This is the same error for any site.

Someone posted that it might have to do with firewalls and filters that your firm is using, but it works for the users with a 7100t, but my cingular device, it does not work. My firm will not spend the $800 for a BB service contract so I'm stuck using the ^%*!! worthless cingular browser until this either resolves itself or we upgrade to BES 4.0 soon, or cingular allows full html browsing. It would be nice if someone who knows what this error is about would share their knowledge...

[Stinsonddog]

I get a 500 error - six months ago I didn't. Call my tech support. They locked down security. So I can't send anything out. Try searching the BB site but I suspect this may be a BES issue.

[tankee531]

well the trouble is that my administrator is also clueless. I took the administration manual from him and read through it myself. The books are so brief and not useful in resolving this issue.

[mbn]

So I finally got someone to issue a ticket for my HTTP Error 400: Bad Request at Blackberry even though we don't have T-support at my cheap ass company with 40 users on the BES. I got bounced to a level 2 guy up in Canada who was pretty helpful despite telling me to go into 'Aboot' to see what version of the handheld software user I was running.

HTTP Error 400 could be due to filters (we use websense) and firewall (we use PIX). There is a known issue with the Blackberry browser running on a handheld higher than 3.8 and Websense - my admins had to jiggle a few things with the firewall to allow different size packets through due to the firewall and/or the filter, but now I am surfing with my Blackberry browser, as it should have been from day one.

It's an odd issue because the users with 7100t's didn't get the error and were surfing freely, but the users on Cingular with 7100g's did. Go figure...

[veeceeonefive]

no one in canada outside of newfoundland says 'aboot', and no one in newfoundland could tech support anything more complicated than a beer bottle.

/me dodges a punch from a newf co-worker who's looking over my shoulder as i write this.

[Thomas]

Hello,
I have the same problem.
Could you tell me exactly which sort of manipulation have made your admin on your FWll.
Sorry for my poor english.
thanks in advance.

Originally Posted by mbn

So I finally got someone to issue a ticket for my HTTP Error 400: Bad Request at Blackberry even though we don't have T-support at my cheap ass company with 40 users on the BES. I got bounced to a level 2 guy up in Canada who was pretty helpful despite telling me to go into 'Aboot' to see what version of the handheld software user I was running.

HTTP Error 400 could be due to filters (we use websense) and firewall (we use PIX). There is a known issue with the Blackberry browser running on a handheld higher than 3.8 and Websense - my admins had to jiggle a few things with the firewall to allow different size packets through due to the firewall and/or the filter, but now I am surfing with my Blackberry browser, as it should have been from day one.

It's an odd issue because the users with 7100t's didn't get the error and were surfing freely, but the users on Cingular with 7100g's did. Go figure...

[rel12561]

I had similar problems. I called tech support and they had me go to service book in options and delete the WAP Transport and mMode (Browser Config).

Then I removed the battery to reset the blackberry and then put it back in, powered up and then select register (can't remember where that was, but it was a pull down menu) but it sent a new service book to replace the two items I removed and eveything worked. I use web client, but maybe this will work for BES too.

[BBTechGuy]

From the good people at WebSense:

http://ww2.websense.com/global/en/Su...ay.php?faq=766

I'd pay particular attention to "url-block url-size <long url size>"

Cheers