
Antek12

I can see the EZ-B v4 but no connections : below report from Windows I have Win 7 64.
List of visible networks: 2 item(s) total, 2 item(s) displayed BSS Type PHY Security Signal(RSSI) Compatible SSID
Infra g No 99 Yes EZ-B v4 2F11 List of preferred networks: 2 item(s) Profile: EZ-B v4 2F11 SSID: EZ-B v4 2F11 SSID length: 12 Connection mode: Infra Security: No Set by group policy: No Connect even if network is not broadcasting: No Connectable: No Reason: 0x00028001 Profile: DO_122455 SSID: DO_122455 SSID length: 9 Connection mode: Infra Security: Yes Set by group policy: No Connect even if network is not broadcasting: No Connectable: No Reason: 0x00028002 Information for Connection ID 2 Connection started at: 2015-01-02 14:51:37-362 Auto Configuration ID: 2 Profile: EZ-B v4 2F11 SSID: EZ-B v4 2F11 SSID length: 12 Connection mode: Infra Security: No Pre-Association and Association Connectivity settings provided by hardware manufacturer (IHV): No Security settings provided by hardware manufacturer (IHV): No Profile matches network requirements: Success Pre-association status: Success Association status: Fail 0x00038002 Association reason code: 0x00000001
Regards Antoni
Its sorted. For programing I use my other laptop, For play I use Nexus 7 and for connection from outside I use m server (with windows home server 2012). It may look complicated but it works.
Correction my server is with Windows Home Server 2011 Vail ( I am planning to replace it with Windows Server 2012 R2 Essentials)
Even with setting static IP's (actually, I think made worse) there is a problem with the EZ-B in client mode. It is not disabling (or fully disabling) the DHCP Server when switching from AP to Client mode, so if you have more than one EZ-B, or if you have other 2.4ghz WiFi devices (802.11n or 802.11g) when they request an IP address from the network, all currently running EZ-B's will send a DHCP offer, along with your router.
This can absolutely cause an issue. Other devices may not gain internet access and the EZ-B's that start after the first one may not get the IP address you are expecting.
(I have confirmed this with Wireshark captures. Whenever a device on the 802.11n network requests an IP address, all of the EZ-B's respond with offers. This is very bad for a network, and could explain all the strange symptoms people have reported with network problems, particularly when there are multiple EZ-B's except for the known HP/Compaq issue in AP mode, and the Avast issue in all modes).
Alan