4.0 beta testers: Problems using tcp/ip or HTTP applications
 

I'm beta testing 4.0 and so far tcp/ip socket applications, and those that are capable of HTTP (such as Webmessenger) fail to work.

I get "could not establish connection" in webmessenger, and for tcp/ip or HTTP apps such as wlirc,

"could not open tunnel - failed' in socket
"could not connect java.io.IOException: could not open tunnel - failed" in HTTP mode.

I have the BIBS, and IPPP for BIBS service books, and have repeatedly tried to send them to my device, including deleting old and re-registering with the network to no avail.

Anyone have any advice? I'm using the Rogers network, which is apparently capable of tcp/ip socket apps working on 4.0.

Have you configured the APN for Options -> TCP?

No. I know the APN's for private IP and public IP on rogers, neither make a difference..

so there is no APN configured on my device in options -> TCP.

I was unable to get sockets working on Rogers. My guess is that they are not allowing traffic through the port I am using.

Well, i'm trying webmessenger/wlirc/virca..

webmessenger can choose between HTTP sockets or direct tcp/ip.. neither work..

you'd think that the web browsing service book (port 80) would allow HTTP sockets even, but neither work..

WLIRC has the same config settings, neither programs work

I got in contact with a Rogers expert and found some instructions that should fix Rogers MDS problems:

1. Synchronize
2. Backup email
3. WIPE your handheld (i.e. javaloader wipe switch)
4. Reinstall BlackBerryOS 4.x (try to use the latest version you have)
5. Reinstall your software

I'll give that a try. =) That's a last resort but i figured as much that it must be some serious software error..

I will report back as soon as it is done, thanks.

No dice..

i'm running .126,

wiped the device, reinstalled OS, application software, then on a stock device ensured i had the correct freshly sent service books..

webmessenger and mutelnet gave same errors.

Now i'm loading back my databases, and will just trod along without public MDS, waiting for Rogers to offically release 4.0 so I can get some support on it. Every time i spoke to level 2 support on this issue they basically wouldn't do much for me, so i'll just be patient yet again.

I am surely hoping that this will work someday, i'm banking on public MDS for my long term support of the Blackberry platform.. without it, i don't see how i'll stay with it when i can get what i want on other platforms..

This has been resolved. It was not a device problem, network problem. My device needed it's profile re-set on the Rogers network..