View Single Post
Old 09-07-2009, 02:24 PM   #1 (permalink)
Marc_G
Knows Where the Search Button Is
 
Join Date: Oct 2005
Location: Indiana
Model: 9700
Carrier: ATT--Stick with us and nobody gets hurt
Posts: 40
Post Thanks: 1
Thanked 0 Times in 0 Posts
Default Hidden SSID prevents wifi connection on 8820

Please Login to Remove!

Hi folks,

I've searched many threads here and elsewhere without an answer. Hopefully someone can point me in the right direction. For the life of me, I can't get my blackberry to connect to my network unless I turn on transmission of the SSID. Here are the details:

Just got a new 8820 running OS 4.5.

My home wifi network is running WPA2 with AES encryption and a specific preshared key. I also use MAC address filtering and have entered the BB's MAC into the allowed list.

Normally, I leave the SSID as hidden (not transmitted) for the increase in security that provides. FWIW, I've got a Belkin N+ Gigabit router. All other devices (laptops and an iTouch) work fine in this environment.

If I turn on the SSID broadcast, the blackberry finds the network and connects to it just fine. The minute I turn off SSID broadcast, the BB loses the connection. Nothing I can do brings it back. Even manually entering the network name and re-entering the PSK does not help. It fails to find or connect to the network.

To be clear, I've tried setting up the network while SSID is on, which works, but the network fails and won't reconnect after I turn off SSID broadcast.

If I clear out that network name, and use the Manually Add Network, selecting PSK encryption and entering in my proper PSK, I have never been able to connect.

Is there some setting I need to change? Some special process to go through?

To me broadcasting one's SSID for a home network is a serious security risk so I prefer not to do this.

One additional note: originally my router was set to use WPA/WPA2 TKIP/AES. In this mode, the BB never connected, whether or not the SSID was being sent, and the BB never could even see the network in its list. Changing to strict WPA2/AES fixed that situation.

Please help! This is driving me nuts.

Marc
Offline   Reply With Quote