<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hey Ben, sorry to hear about your woes. </div><div><br></div><div>Given that it works sometimes, I'm lead to believe that things are ok on the hardware side. Though, I've not used ubiquity. Can you post the windows dhcp server config or equivalent? Just the portion concerning the available pools and which machines it will talk to. </div><div><br></div><div>Also, what can you say about the machines that fail? Are they getting the 172. zero conf or something else. Can a non-working machine be given ip settings manually or by using a wired connection?</div><div><br></div><div><br><h1 class="char Zyyy U262F" data-text="☯" id="h1-display-char" style="margin: 0.1em 0px; text-rendering: optimizelegibility;"><span style="font-size: 13pt; font-weight: normal;">-j</span></h1><div><p class="MsoNormal" style="margin: 0in 0in 12pt;"><br></p><p class="MsoNormal" style="margin: 0in 0in 0.0001pt;"><span style="background-color: rgba(255, 255, 255, 0);">Right to Life of Michigan<o:p></o:p></span></p><div><p class="MsoNormal" style="margin: 0in 0in 12pt;"><span style="background-color: rgba(255, 255, 255, 0);">Director of Information Services</span></p><p class="MsoNormal" style="margin: 0in 0in 12pt;"><span style="background-color: rgba(255, 255, 255, 0);"><a href="tel:616.446.6492" x-apple-data-detectors="true" x-apple-data-detectors-type="telephone" x-apple-data-detectors-result="2">616.446.6492</a> / </span><a href="mailto:jdenick@rtl.org" style="font-size: 13pt;">jdenick@rtl.org</a></p><h1 class="char Zyyy U262F" data-text="☯" id="h1-display-char" style="margin: 0.1em 0px; text-rendering: optimizelegibility; font-weight: 500;"><span style="font-size: 17px; background-color: rgba(255, 255, 255, 0);">☯</span></h1></div></div><div><h1 class="char Zyyy U2637" data-text="☷" id="h1-display-char" style="text-align: start; margin: 0.1em 0px; text-rendering: optimizelegibility; font-weight: 500;"><span style="font-size: 17px; background-color: rgba(255, 255, 255, 0);">☷</span></h1></div></div><div><br>On Aug 28, 2014, at 1:04 PM, Benjamin Flanders <<a href="mailto:flanderb@gmail.com">flanderb@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div>Short Story:</div><div>My AP's are having issues handing out IP's with DHCP. I am in no way a networking wizard and could use help diagnosing.</div><div><br></div><div>Long Story:</div><div>I installed two ubiquity AP's in the office last month. I started off really liking it, it was cheap, the range was better than the old routers I had, and the controller was nice to work with.</div>
<div><br></div><div>We have a small office with few wireless clients (around 10) and for a few weeks everything was hunky dory. Then people started coming back from vacation and I started having issues.</div><div><br></div>
<div>It seemed that when I get above 9 clients the last clients won't get ip addresses. Sometimes I can get 13 with valid ip addresses. Even clients with valid leases don't get ip addresses if I reset the AP and that client is one of the last to try getting an ip. It isn't consistent, in that sometimes a client connects but then loses it and sometimes a client don't connect but then half hour later it will connect. </div>
<div><br></div><div>I've been working with Ubiquiti (they don't seem all that knowledgeable) and last week they remoted in and we tried a bunch of different settings and even pulling the AP from one side of the office to right next to the other and we couldn't get above 13 clients. </div>
<div><br></div><div>One weird thing that happened during testing is that we had a device that had an ip address then lost it (according to the controller), but the device still had a valid ip address when I looked at the ip settings, so it didn't know it had lost the ip address. With this device I was able to ping our erp server and other ip addresses but I wasn't able to ping the DHCP server, then about 5 minutes later it couldn't ping anything.</div>
<div><br></div><div>They said it looks like an issue with the DHCP server and suggested increasing the address space. My IP lease range isn't full, but I could still increase the pool by about 70 addresses, which I did. Right now when I look at the controller I have 17 clients and only 1 doesn't have a valid ip address, but about half hour ago I had 18 clients and 3 not getting an ip address. So it got better, but still not right.</div>
<div><br></div><div>According to the Ubiquiti forums it seems that others have this issue and there isn't a fix in the forums.</div><div><br></div><div>Some more info:</div><div>My lease pool is 192.168.0.12-200 I have 97 open ip address I could hand out.</div>
<div>My DHCP server is windows 2008 rc2</div><div>The Windows 2008 rc2 is a client on VMware</div><div>The Ubiquiti controller is installed on the same windows server.</div><div>The network consists of cisco switches.</div>
<div>Wired devices have no issue getting ip addresses</div><div><br></div><div>So my questions:</div><div>Does DHCP need a certain % of open addresses in the pool?</div><div>Could it perhaps be an issue of having the Ubiquiti Controller on the same server as the DHCP server? - I could start up a linux server on VMWare and put the controller on that. I'm doing this right now(I just thought of this)</div>
<div>I understand that this is the Linux Group and this could possibly be a windows DHCP issue so is there a local windows group I could go to if you all think windows is the issue.</div><div>Could the Cisco switches be filtering or interfering somehow?</div>
<div><br></div><div>Share and Enjoy<br>Ben</div>
</div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>grlug mailing list</span><br><span><a href="mailto:grlug@grlug.org">grlug@grlug.org</a></span><br><span><a href="http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug">http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug</a></span></div></blockquote></body></html>