Connecting to AIR-CAP3702I-Z-K9

[AJNiteOwl]

I have a WAP Cisco Air Cap3702I I have reset to factory settings and I am expecting the device to have an IP address of 192.168.0.100 (following config guide on https://www.youtube.com/watch?v=krSDfvRbWX0) so I can get onto the GUI.  When I turn on (POE) I ethernet cable plug into my local network and DHCP assigns IP of 192.168.1.32.  I can ping the WAP and it replies but can't get onto its GUI (refuses to connect). I have checked Firewall and okay. WAP is booting ok and cycling between green and red so it sees the network. I don't think I need to re-flash, but it is possible it has a custom IOS which I thought would be flushed with factory reset?

Any thoughts?  Thanks NO.

[Kasun Bandara]

configure  ip http server and ip http secure-server commands in CLI. 

[AJNiteOwl]

Where do I configure that? I cannot get into the Cisco WAP as it asks for username and password at address 192.168.1.32?

[Flavio Miranda]

If this Access Point is autonomous mode, then you should be ale to reach HTTP or HTTPS web page. But, chances are this is a capwap AP and then it will not give you any access unless you join it in a WLC.

 Do you have console cable to connecto to AP? If you have, then we can help you.

[AJNiteOwl]

Thanks I understand the HTTP & HTTPS.  Do I need to connect from the PC directly to the Cisco WAP by ethernet cable after I have disconnected the router assigning DHCP addresses from the rest of the internet?  The router then supplies the IP address locally and then allows direct connection from the PC to the HTTP address?

I don't have a console cable but would the factory reset putt the AP into autonomous mode?

Cheers

[Flavio Miranda]

"

I don't have a console cable but would the factory reset putt the AP into autonomous mode?"

Nop. Factory reset only erase the configuration but dont change anything on the AP IOS.  We need to make sure the AP is realy autonomous or you are wasting your time trying to reach the web interface. 

Console cable it the best and maybe only alternative. If you are sure that the AP has an IP address, you can ping it, then you try to access using either HTTP or HTTPS and nothing happen, then good chances are this AP is not autonomous mode.

Did you try to SSH to it. Use Putty and try. SSH would be accepted dont matter which AP mode.

[AJNiteOwl]

Thankyou for that insight as above the IP address is 192.168.1.32 which is given to the AP by the DHCP "server".  It is able to be pinged and Putty can get to username and password but we don't know what those are "blank" and "Cisco" don't work or many of the other suggestions.  Pressing the "mode" button I understood switched between autonomous and (is it) standalone mode. The mode button is also the factory reset button which has already reset the AP and we assume put the AP into autonomous mode. We have tried putting the DHCP server on 192.168.0.1 to try and get the AP to take the address of 192.168.0.100 as shown on the youtube video above (didn't work).

So we will try Putty again and SSH to it.  By using Putty I understand a secure connection is made that does not require a username/password but what I don't understand is how that gets me to the GUI configuration screens?  NOwl