First question and problem: I think the intent is to be able to connect up to 5 EZB's through ARC. However I've hit a wall trying to connect ARC to two V4 EZB's when they are in AP (Access Point) mode. Using my laptop I've followed directions and connected ARC to the first V4 after establishing a wireless connection through the "Wireless Network Connection" icon on my Win 7 Taskbar. Then when I try to connect wirelessly to the second V4 EZB I lose the wireless connection to the first. My laptop will only let me have more then one wireless connection at a time. What am I missing here?
Second question and problem: With both V4's in Client mode and the Green light blinking (the voice says she's attached to my network), I can only have one EZB powered up at a time and have a successful search of my router for a IP address. If both are powered up and attached to the network ARC cant find an address. Is this normal? I've watched the tutorial several times.
Third Problem: For two nights now after the laptop and robot are powered down the second EZB entry in ARC will not connect to the second EZB board. I have to push the network reset button on EZB and redo the IP search in client mode.

Wow. you got the 4th EZ-B ever made
You'll like that Asus router Dave, I've got two of the Asus N56 routers and they are rock solid.
Just for grins last night I added my 3rd v4 EZB to the mix last night. I thought I'd see if I would have any trouble connecting ARC to a new unit after power down, waiting overnight and power up in the morning.
I also moved my project onto a new laptop (through the EZ Cloud. I love that thing!) making sure I had the latest ARC installed. I then sat down close to the router.
First thing I noticed was the scan for IP addresses was super fast now. Before when I was in the basement and the router was on the main floor the scan would lag. I got all three units to show up in scans and connected to ARC. All three were working nicely and responding. The newly installed EZB was Board 2 (third board down) on the connection list. I then powered down for the night and got some sleep.
With much curiosity I powered everything up this morning. All three EZB v4's cheerfully reported that they had successfully connected to my network. I then started up the laptop and started ARC.
Clicked on connect button for Board 0 - Connected! Clicked on connect button for Board 1 - Did not connect. Clicked on connect button for Board 2 - Did not connect.
I rescanned for each EZB and the only that would show up in a scan was the one (Board 0) that would connect. I looked at the client list in my router and the other two are listed there. So odd.
Well, this at least tells me I should have no problems with the EZB's themselves.
With a little luck the repeater should arrive today and the new router tomorrow. Step by step.
Well, it's been another frustrating evening. I got my Engenius EAP350 AP/repeater in this afternoon and have been trying to set it up all evening. I set it to Repeater Mode and I'm pretty sure I have all the settings right but it just wont connect to my network. tired
It seems real straight forward but I had never set something like this up so I read all of the manual, did a ton of reading on the internet and watched a bunch of Youtube vids.
Basically I just plugged in the EAP350 to my laptop with a LAN cable to access it's web interface and after entering some settings in my network card connection window and entering it's default IP address into Firefox I was in.
I then Changed it to Repeater Mode and waited for it to reconfigure it's self.
Once that was done I changed it's static IP address to match my network's Subnet mask and a ending number that should not interfere with any other device I have on the network: 192.168.2.31 (later I changed this to "Obtain IP Automatically" but that didn't work either). I also made the Gateway IP to match my router's IP: 192.168.2.1
I then went to the Network section and did a Site Survey and picked my home network and entered in my WEP Security info making sure it all matched. I thin clicked "Accept".
After a reboot this should have started the silly thing and allowed me to connect but I could not see it in my Wireless connection list. After going back into the interface (I was able to use the default address) I found that none of the setting s held and were back to default. mad
I disabled all my security, firewalls and antivirus and tried this over a and over making little changes. No go. This shouldn't be this hard. tired It's making me feel like a dope.
I do have a question about this EAP350, I read that Repeater cut the bandwidth in half. Does that mean The EZB and everything running through it will have less room to work? If this is the case would it be better to run in AP mode? There would be a physical cable between the router and the AP and I would expect that the full bandwidth would be available. I could be wrong about all that as my mind is a little addled right now with the recent struggles.
Tomorrow the new router should arrive. Hopefully that will make a difference and I can start making progress.
OK, I think I finally have some answers as to what may be happening here.
First, I haven't yet been able to get the Engenius 350 to connect and work. I've given up for now. My new modem arrived today and I moved on to retiring my old one and installing this new one (mentioned in a earlier post). I did try to get the Engenius 350 to work after I got the router installed but because they both have the same IP address (192.168.1.1) I'm getting a wicked IP address conflict and I cant get into the Engenius 350's software settings. I have no idea at this point how to resolve this conflict. Any help on this would be welcomed.
This new ASUS RT-AC66U Dual-Band Wireless-AC1750 Gigabit Router is a dream. It's quick and right away I saw how responsive and easy to use it is. I also get excellent signal strength where the EZB's and laptop sit. I'm able to see the wireless clients connect and disconnect almost right away with a simple refresh of it's client list screen. Because of this I think I've solved what may be happening:
I have both EZB v4's attached to a power strip and I've been powering them on at the same time. They must connect to my network at virtually the same moment and they even speak "I have successfully connected to your network" in unison. I think the router must see these two connections as one and assigns them both to the same IP address causing a conflict. When I power them up like this I can see their two different MAC addresses assigned to the same IP address in the routers Client list. When I power them up one at a time they are assigned the to original IP addresses that they were assigned when I set them up.
I've been able to reproduce this a few times now. The real test will be keeping everything powered down for a few hours or overnight and see if I can connect to ARC with both EZB's if I power them up at different times.
If this is the case I'll need to find a way for them to be automatically powered up with a delay between them. It may be as simple as that.
Good troubleshooting Dave, strange that with the speed of electrons that one EZB4 would be just a bit faster than the other and not create this IP dilemma.
Two suggestions. First, for the conflict with the extender. You can change the IP address/subnet of the router. See page 63 of the manual (download here: https://www.asus.com/Networking/RTAC66U/HelpDesk_Manual/) to see how to change the IP. I would suggest just changing the 3rd octet (ie, change it from 192.168.1.1 to 192.168.0.1)
The, since you have the MAC addresses of the EZ-B's, you can specify the IP addresses for the DHCP server to assign (this was my initial recommendation, but your old router could not do it). See page 64/65 for instructions. Note, they recommend setting to 192.168.1.xxx, but if you follow my recommendation above to avoid the conflict on the repeater's default address, then you would need to assign addresses in the 192.168.0.xxx subnet.
Alan
Thanks Alan & R-Doc for the inspiration and support.
I may have been a little off in my solution. After a few hours I restarted everything making sure I had a delay in powering up each EZB. Well, once again the second board wouldn't connect to ARC after telling me she was connected to my network. I checked the client list of the router and saw that the one that connected had the original IP address and the one that didn't connect to ARC had been reassigned to an IP address all the way to the other end of the spectrum of numbers (198). So.........
I have taken Alan's advice finally and (after changing the router's ID 92.168.1.1 to 192.168.0.1 I added the two EZB to the list of IP's that the router will always assign.
Tomorrow I'll see if this finally is the answer.