Configured the v4 in client mode, it connected to my network, its pingable and I can access the v4 Wi-Fi Robot Controller web page from the desktop.
The problem came up when trying to connect to the v4 from builder. Tried the scan, the v4 chirped when the address was hit, but would not display the address for selection.
The forums mentioned AVAST blocking connection to the v4, so after a few tests I found that the AVAST Web Shield was the problem. As per AVAST forums, I tried the web shield exclusions, scripts exclusions.. , nothing helped.
But found the solution in one of AVAST forums, modify the WebShield.ini in programdata\avast , programdata not programfiles..
Go to (your):\programdata\avast software\avast,
Find WebShield.ini, add the following lines:
Restart PC. You may need to disable avast self defense (Settings - Troubleshooting).
This setting does not disable it, but "downgrades" it to previous technology (meaning local transparent proxy).
With this change , the AVAST WebShield is still running but does not hinder the v4 connections.
Hope this helps.
FYI, am running the latest EZ-B builder on a windows 7 home premium 64 bit machine.