Is the controller running on your laptop? Mudcow wrote:I unplugged my laptop from the switch an the AP configured correctly?! Set up internal and/or external DNS as needed. an IP address of the controller, so that when you move the device to another subnet or change the controller IP, APs can find the controller. Then do the set-inform, preferably with an FQDN of the controller vs. Look at your DHCP server for its IP address to make sure it is on the real subnet. Make sure that a device such as a laptop connected to the same port and cable that the AP uses can get an IP address from a DHCP server, then factory-reset the AP. What exact IP address does the AP have? If it truly has the 192.168.1.20 fallback address, it is either not seeing a DHCP server response, or someone set it to that IP address statically. To the OP, you stated, ".but its currently assigned itself 192.168.1.0 address", which is a subnet, not an IP address. He knows the actual IP address but either didn't put it here, or mis-typed it.
This is why I absolutely HATE IT when people who have ALL of the information only give little tidbits and expect others to use a crystal ball to figure out the rest.
He did not say it was on the fallback address, although he did mention the same subnet as the fallback IP. I would do the SSH method, but this can be risky if you adopt to the IP of the controller instead of the FQDN.įirst thing first, why is it assigning the fallback address (192.168.1.20) instead of the subnet you're trying to work on? Does it need a static IP assigned ahead of time? They generally need a DHCP address to adopt like that.
0 kommentar(er)
