I originally setup my Capsman cap2n using this URL - tutorial. https://www.youtube.com/watch?v=OGFKfyzHnsM

I found it easy to setup and it has been flawless for months.

Today I had some power issues and noticed the wireless devices were all offline. In the past if I rebooted a device by unplugging the PE cable, all I had to do to "wake up the cap2n was to go into Capsman on the capsman controller (Rb2011) and uncheck "enable" and re enable the capsman feature. Today this failed to work. I also could not log into the cap nor could I detect it using Winbox as a neighbor on the mac - it seemed dead. So I reinstalled the O/S using netinstall leveraging the 192.168.0.x subnet as per other tuorials. It installed without incident. I could log on and complete the tuorial from the 192.168.0.x device I used to do the netinstal with. I assumed that since this CAP obtains its IP from DHCP on the 2011 (as it did before) that all I needed to do now was plug it back into the POE line and log on...but I cant see the MAC again...the only way to see it is to set my device ip to 192.168.0.x subnet... obviously im not using that subnet on my lan...

EDIT - I am starting t think this might be a windows 10 compatibility issue with the tools im using. The machine that can connect is windows 7 - The machine that can flash 9/10 times is windows 7... the other machines are windows 10 and they present all kinds of oddities like the netinstall client will send the offer and then the device will not start the progress and in a few second its says ready again... or randonly it will start formatting the hard rive then fail... this never happens ont he windows 7 machine but even on that when I am done and it reboots I cant detect the cap on the network normally and I cant connect using the mac address either. On the windows 10 machine I have all other ports and network interfaces disabled and firewall is off.

The weird thing is that this morning I restored the device again using the CR version of Netinstall and the CR o/s version and I can log in to the device when using that same laptop. The Winbox sees the MAC - and I can logon. The logs reads error relating to reboot without proper shutdown - I assume the NEtinstall does shut down in a nice way ?? but thats the only error. While connected to the same device that I use to flash it I can reboot, shut down - and log back on fine. I can change modes and configure the device but once I plug it into the network (via POE) its never detected again.

Resolved - the root cause was not the Cap2n but rather a dead POE port - the port was supplying power but no ethernet...

I am back on line with the POE injector and another port on my RB2011. ITs not as elegant as a single POE line but its functioning.

Note that I used a fairly long cable on this POE - probably 30 feet - do you think that contributed to the dead port by chance ?