Client cannnot connect to SSID

[ShengxiangZhang67519]

We have two SSIDs. One of them is connected normally. Another guest SSID cannot connect. Prompt that this network cannot be connected.
The following is the log of debug with a client

WLC:3504 

version:8.5.140

AP:2802i

[Leo Laohoo]

---

@ShengxiangZhang67519 wrote:

*DHCP Socket Task: Jan 06 07:21:54.173: 20:68:9d:86:44:6f DHCP   chaddr: 20:68:9d:86:44:6f
*DHCP Socket Task: Jan 06 07:21:54.173: 20:68:9d:86:44:6f DHCP   ciaddr: 0.0.0.0,  yiaddr: 10.204.20.106
*DHCP Socket Task: Jan 06 07:21:54.173: 20:68:9d:86:44:6f DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0
*DHCP Socket Task: Jan 06 07:21:54.173: 20:68:9d:86:44:6f DHCP   server id: 1.1.1.1  rcvd server id: 10.204.20.254

---

I can see the wireless client getting a valid IP address, however, gateway IP address is BLANK/missing.

[ShengxiangZhang67519]

No, the following logs are connected to normal SSID logs. I re-upload a copy

[ShengxiangZhang67519]

I am not sure if it is because of this bug: CSCvk36887.

I configured：config client deauthenticate ，according to the method of this bug. But still useless

[Leo Laohoo]

---

@ShengxiangZhang67519 wrote:

No, the following logs are connected to normal SSID logs. I re-upload a copy

---

Is that all you can provide?  A debug worth <1 second?

[ShengxiangZhang67519]

Yes, please don't look at the putty(1).txt file. This is a problem, I will upload a copy again, please take a look.

[marce1000]

 - Use this tool to have your debugs analyzed , as Leo said the second one is a bit short : https://cway.cisco.com/wireless-debug-analyzer/

  Here is the output for your first file which looks normal at first glance :

20:68:9d:86:44:6f

Connection 1 of 1

•  
•  
• 1
•  
•  

---

Show Time

Show Task

Show Translated

Show Original

Show Prior First Connection

Show All

---

TimeTaskTranslated

Jan 06 07:21:53.931	*apfMsConnTask_1	Client made new Association to AP/BSSID BSSID dc:8c:37:86:28:22 AP COFFE
Jan 06 07:21:53.932	*apfMsConnTask_1	The WLC/AP has found from client association request Information Element that claims PMKID Caching support
Jan 06 07:21:53.932	*apfMsConnTask_1	The Reassociation Request from the client comes with 0 PMKID
Jan 06 07:21:53.932	*apfMsConnTask_1	The Reassociation Request from the client comes with 0 PMKID
Jan 06 07:21:53.932	*apfMsConnTask_1	Client is entering the 802.1x or PSK Authentication state
Jan 06 07:21:53.932	*apfMsConnTask_1	Client has successfully cleared AP association phase
Jan 06 07:21:53.932	*apfMsConnTask_1	WLC/AP is sending an Association Response to the client with status code 0 = Successful association
Jan 06 07:21:53.935	*Dot1x_NW_MsgTask_7	Client will be required to Reauthenticate in 1800 seconds
Jan 06 07:21:53.935	*Dot1x_NW_MsgTask_7	WLC/AP is sending EAP-Identity-Request to the client
Jan 06 07:21:53.965	*Dot1x_NW_MsgTask_7	WLC/AP is sending EAP-Identity-Request to the client
Jan 06 07:21:53.988	*Dot1x_NW_MsgTask_7	Client sent EAP-Identity-Response to WLC/AP
Jan 06 07:21:54.112	*Dot1x_NW_MsgTask_7	RADIUS Server permitted access
Jan 06 07:21:54.113	*Dot1x_NW_MsgTask_7	Client will be required to Reauthenticate in 1800 seconds
Jan 06 07:21:54.113	*Dot1x_NW_MsgTask_7	4-Way PTK Handshake, Sending M1
Jan 06 07:21:54.140	*Dot1x_NW_MsgTask_7	4-Way PTK Handshake, Received M2
Jan 06 07:21:54.141	*Dot1x_NW_MsgTask_7	4-Way PTK Handshake, Sending M3
Jan 06 07:21:54.149	*Dot1x_NW_MsgTask_7	4-Way PTK Handshake, Received M4
Jan 06 07:21:54.149	*Dot1x_NW_MsgTask_7	Client has completed PSK Dot1x or WEP authentication phase
Jan 06 07:21:54.150	*Dot1x_NW_MsgTask_7	Client has entered DHCP Required state
Jan 06 07:21:54.170	*dtlArpTask	Client has entered RUN state
Jan 06 07:21:54.171	*dtlArpTask	Received DHCP ACK, assigning IP Address 10.204.20.106
Jan 06 07:21:54.172	*DHCP Socket Task	Received DHCP request from client
Jan 06 07:21:54.172	*DHCP Socket Task	Sending DHCP Request to DHCP Server 10.204.20.254 through gateway 10.204.20.1 requesting 10.204.20.106 on VLAN 200
Jan 06 07:21:54.173	*DHCP Socket Task	Received DHCP ACK from DHCP server

[ShengxiangZhang67519]

please don't look at the putty(1).txt file. This is a problem, I will upload a copy again, please take a look.

[Leo Laohoo]

Kindly raise a TAC Case.  

The debug is another <1 second debug output.  

What happens if you run this command: 

config client deauthenticate 20:68:9d:86:44:6f

[ShengxiangZhang67519]

I reopened a discussion

[ShengxiangZhang67519]

After configuring config client deauthenticate 20:68:9d:86:44:6f, there is no effect. The SSID still cannot connect. Tip: Unable to connect to this network

[Leo Laohoo]

20:68:9d:86:44:6f

What OS is this client running on?  If Android, what exactly is it running on?

Is this happening to one wireless clients or multiple wireless clients? 

Can the wireless client(s) authenticate to an SSID with Open authentication &/or PSK?

[ShengxiangZhang67519]

There are various clients, windows, android, ios, etc.

[Leo Laohoo]

---

@ShengxiangZhang67519 wrote:

There are various clients, windows, android, ios, etc.

---

Can the wireless client(s) authenticate to an SSID with Open authentication &/or PSK?

[ShengxiangZhang67519]

I have set up open authentication, but I still can’t connect to this network.And there are three or four others who can connect.