Connecting android tablet when SSID is hidden

[#1]

Simple thing really
I tried not broadcasting my SSID but my better half couldn't connect to the router with her tablet
Is there a simple way round connecting when the SSID isn't broadcast or is this how it is supposed to work

[#2]

Isn't this a case of let her connect, then disable SSID.
I have just tried that on my phone and it connects ok to the hidden SSID.

[#3]

I'm at home today so just hid my SSID but my tablet had the wifi settings saved, it wont connect, not in range apparently. Tried looking in advanced settings but nothing there to get it hooked up. Not of any help to you really but thought I would give it a shot.
Edit would WPS work if you have it?

[#4]

I hid my Router SSID.
Opened Wi-Fi on my Android phone and scanned....my Router SSID not found...as expected.
Clicked More > Add Network
Added the details of my Router SSID, security type and password.
It is now in the list of wi-fi networks and connects.

[#5]

Other devices report a "hidden" network and when selected prompt the user for the SSID & pass phrase.
@Jim,
It might be a matter of rescanning and 're-registering' the connection.

[#6]

thanks all - will have a play this evening

[#7]

Just out of interest, why are you hiding you SSID?

[#8]

to stop my neighbour's devices trying to connect - not deliberately - and failing which mucks up the DHCP table (Billion problem which their engineers are working on)

[#9]

Oh that sounds really bad.  The Billion ought to be going nowhere near the DHCP table (allocating an address) until after getting past the WiFi security layer.  
Might you alternatively fix the issue by establishing MAC address based access controls ... or is the DHCP mucked up by that point as well?

[#10]

I doubt it
This is what happens

[#11]

Would reducing the lease duration help?

[#12]

They are all set to 24 hours
This has been discussed at length in the Billion Forums so please don't waste your time suggesting solutions as there apparently isn't one until Billion get their fingers out

[#13]

OK Jim,  Just thought I was being helpful. 

[#14]

I know that - as usual - you were being helpful 
But in this case you would have been wasting your time 
The reported cases go back to March with this post on 9th April

Quote

Well, over the last few days I've tried the old firmware and the new firmware in various configurationsand I've come to the conclusion that the dhcp handling is seriously awry. When a guest network is enabled the router is just unable to keep track of what leases it has issued as these lines taken from the log show. Apr 9 14:23:35 daemon info syslog: sending OFFER to IP:192.168.2.2, MAC:4c:b1:99:13:7a:26 Apr 9 14:23:35 daemon info syslog: sending OFFER to IP:192.168.2.2, MAC:4c:b1:99:13:7a:26 Apr 9 14:23:36 daemon info syslog: sending ACK to IP:192.168.2.2, MAC:4c:b1:99:13:7a:26 Apr 9 14:23:39 daemon info syslog: sending OFFER to IP:192.168.2.3, MAC:b8:ff:61:97:7b:e1 Apr 9 14:23:39 daemon info syslog: sending OFFER to IP:192.168.2.3, MAC:b8:ff:61:97:7b:e1 Apr 9 14:23:40 daemon info syslog: sending ACK to IP:192.168.2.3, MAC:b8:ff:61:97:7b:e1 Apr 9 14:32:02 daemon info syslog: sending OFFER to IP:192.168.2.4, MAC:b4:52:7e:16:31:cb Apr 9 14:32:02 daemon info syslog: sending ACK to IP:192.168.2.4, MAC:b4:52:7e:16:31:cb Apr 9 14:46:27 daemon info syslog: 192.168.2.1 belongs to someone, reserving it for 3600 seconds Apr 9 14:46:30 daemon info syslog: sending OFFER to IP:192.168.2.2, MAC:5c:f9:38:8b:b6:c6 Apr 9 14:46:30 daemon info syslog: sending OFFER to IP:192.168.2.2, MAC:5c:f9:38:8b:b6:c6 Apr 9 14:46:31 daemon info syslog: sending ACK to IP:192.168.2.2, MAC:5c:f9:38:8b:b6:c6 There is no way that the only active dhcp server should hand out a lease (192.168.2.2) at 14:23:36 to one machine (MAC 4c:b1:99:13:7a:26) and then at 14:46:31 (23 minutes later) hand it out to a different machine (MAC 5c:f9:38:8b:b6:c6). The server's own default should have caused it to reserve 192.168.2.2 for 3600 seconds as can be seen for ip address 192.168.2.1. I am still using the new firmware, but Billion really needs to sort out the dhcp server, one of the points that attracted me to this router was the ability to set up a guest network, but in fact it does not work. Having a guest network is simply leading to ip address conflicts.