Quote:
Originally Posted by Tailor
The wireless is fine, i have it on a circuit i use for testing stuff like this, it has a public IP range so i can elimate any NAT or firewall issues.
i can access the internet fine using the WiFi browser, if i try and browse to https://193.109.81.88 which in theory is exactly what it is trying to do by making a SSL connection to rcp.eu.blackberry.com, then i get a certificate error (because the certificate is for rcp.eu.blackberry.com). This must show it is connection fine. If i browse to https://rcp.eu.blackberry.com then i get no certificate error. (presumably showing that the certificate is trusted)
My device came with 4.3.0.72 so it's interesting that you upgraded to it.
How does your host routing table entry for WiFi compare to mine? |
You say your device came with 4.3.0.72 yet your sig says 4.3.0.67. Mine came with 4.3.0.67 and I upgraded to 4.3.0.72 yesterday.
My Host routing table for WiFi is exactly the same as yours.
In the WiFi Diagnostics. The fact that you have a Black Dot against the Blackberry Infrastructure Connection suggests that it hasn't connected.