[rodnig1]

Ok, this one is kind of weird, and im confused.

i recently upgraded to BES 5.0.2 from 4.1.7 for Exchange 2003 sp2, both running on separate 2003 sp2 32bit enterprise OS.

before we upgraded, we had no issues with web browsing, from the handhelds, or from the server itself. Now, i am running into issues with web browsing on the handhelds, as well as the server(obviously related). its an intermittent problem, meaning that if i am trying to search for something on google, i will sometimes get a time out error. if i refresh it a few times, it will go through. then randomly, it will fail again... same thing over and over.

i have tried this with changing the http sockets, and enabling/disabling the scalable http.

this is really a weird one....

[freakinvibe]

Are you using a http proxy?

[rodnig1]

sorry, should have included that. we do not have a proxy configured,

but, in the Priority Universal resource locater is has this: .*://.*(:\d*)?(/.*)*(\?.*)?

[freakinvibe]

Upgrading BES versions does not influence the browsing experience you have on the server directly. Which browser are you using on Win2003 Server, Internet Explorer?

Having no proxy, are you saying the BES server has an official IP address, or is there a router with NAT inbetween?

[rodnig1]

thats why it is weird. we seriously had no issues with browsing the web before the upgrade of the bes.

the bes has a static ip address, and there is no actual router in between, only a layer 3 switch with VLANS for inter segment routing in our network.

[freakinvibe]

Could be many things, DNS, bad packets etc. You probably have to use a network sniffer to find out what causes the timeouts. I still think it is coincidence that the server browser experience has changed with the upgrade. Maybe something else happened at the same time?

I guess you have already seen this KB (as you have already changed scalable http):

KB23933-After a BlackBerry Enterprise Server update, BlackBerry smartphone users are unable to browse to web sites

[rodnig1]

yes, i have already been through that kb, and made those changes