NWA50AX not registered by NCC - used to work perfectly
Freshman Member
AP not detectable by clients even though connected via PoE to EX3300-T0 router.
The router can ping it (using the 192.168.1.1 menu) on the IP adress with success. In the nebula app I can ping a URL with the AP and it says sucess. Updated firmware of router and AP. Followed the AI guide on nebula; SSID settings (enabled, no schedule, WPA2-PSK). I dont understand why it just wont work as it has. LED of AP is blinking green with 3s frequency.
from the monitor eventlog in nebula control center below:
02-10-2024
12:59:19 |
B8:D5:26:FF:66:2C |
User |
Fail login attempt to NWA50AX from ssh (login on a lockout address) [count=4] |
02-10-2024 | 12:59:12 | B8:D5:26:FF:66:2C | User | Fail login attempt to NWA50AX from ssh (login on a lockout address) [count=2] | ||
02-10-2024 | 12:59:07 | B8:D5:26:FF:66:2C | User | Fail login attempt to NWA50AX from ssh (login on a lockout address) [count=3] | ||
02-10-2024 | 12:59:03 | B8:D5:26:FF:66:2C | User | Failed login attempt to NWA50AX from ssh (incorrect password or inexistent username) | ||
02-10-2024 | 12:58:55 | B8:D5:26:FF:66:2C | User | Fail login attempt to NWA50AX from ssh (login on a lockout address) [count=5] | ||
02-10-2024 | 12:58:43 | B8:D5:26:FF:66:2C | User | Fail login attempt to NWA50AX from ssh (login on a lockout address) [count=5] | ||
02-10-2024 | 12:58:41 | B8:D5:26:FF:66:2C | User | Address 183.81.169.238 has been put into lockout state | ||
02-10-2024 | 12:58:29 | B8:D5:26:FF:66:2C | User | Failed login attempt to NWA50AX from ssh (incorrect password or inexistent username) [count=5] | ||
02-10-2024 | 12:58:11 | B8:D5:26:FF:66:2C | User | Fail login attempt to NWA50AX from ssh (login on a lockout address) | ||
02-10-2024 | 12:58:00 | B8:D5:26:FF:66:2C | User | Fail login attempt to NWA50AX from ssh (login on a lockout address) | ||
02-10-2024 | 12:57:47 | B8:D5:26:FF:66:2C | User | Fail login attempt to NWA50AX from ssh (login on a lockout address) | ||
02-10-2024 | 12:57:27 | B8:D5:26:FF:66:2C | User | Fail login attempt to NWA50AX from ssh (login on a lockout address) [count=2] | ||
02-10-2024 | 12:57:16 | B8:D5:26:FF:66:2C | User | Fail login attempt to NWA50AX from ssh (login on a lockout address) | ||
02-10-2024 | 12:56:55 | B8:D5:26:FF:66:2C | User | Fail login attempt to NWA50AX from ssh (login on a lockout address) [count=2] | ||
02-10-2024 | 12:56:46 | B8:D5:26:FF:66:2C | User | Fail login attempt to NWA50AX from ssh (login on a lockout address) | ||
02-10-2024 | 12:56:37 | B8:D5:26:FF:66:2C | User | Address 83.222.191.62 has been put into lockout state | ||
02-10-2024 | 12:56:18 | B8:D5:26:FF:66:2C | User | Failed login attempt to NWA50AX from ssh (incorrect password or inexistent username) [count=2] | ||
02-10-2024 | 12:55:56 | B8:D5:26:FF:66:2C | User | Failed login attempt to NWA50AX from ssh (incorrect password or inexistent username) [count=2] | ||
02-10-2024 | 12:55:45 | B8:D5:26:FF:66:2C | User | Failed login attempt to NWA50AX from ssh (incorrect password or inexistent username) | ||
02-10-2024 | 12:55:21 | B8:D5:26:FF:66:2C | User | Failed login attempt to NWA50AX from ssh (incorrect password or inexistent username) [count=2] | ||
02-10-2024 | 12:43:31 | B8:D5:26:FF:66:2C | User | Failed login attempt to NWA50AX from ssh (incorrect password or inexistent username) [count=2] | ||
02-10-2024 | 12:41:04 | B8:D5:26:FF:66:2C | User | Failed login attempt to NWA50AX from ssh (incorrect password or inexistent username) [count=2] | ||
02-10-2024 | 12:35:45 | B8:D5:26:FF:66:2C | User | Failed login attempt to NWA50AX from ssh (incorrect password or inexistent username) [count=2] | ||
02-10-2024 | 12:20:21 | B8:D5:26:FF:66:2C | User | Failed login attempt to NWA50AX from ssh (incorrect password or inexistent username) [count=2] | ||
02-10-2024 | 12:18:22 | B8:D5:26:FF:66:2C | User | Failed login attempt to NWA50AX from ssh (incorrect password or inexistent username) [count=2] | ||
02-10-2024 | 12:17:56 | B8:D5:26:FF:66:2C | User | Failed login attempt to NWA50AX from ssh (incorrect password or inexistent username) | ||
02-10-2024 | 12:17:55 | B8:D5:26:FF:66:2C | User | Failed login attempt to NWA50AX from ssh (incorrect password or inexistent username) | ||
Accepted Solution
-
After checking the device diagnostic info, we found that this AP has a hardware issue. Please reference this FAQ to submit an RMA request.
Zyxel Melen0
Zyxel Employee
All Replies
-
What's your issue? Seems like your NWA50AX has been registered in your Nebula organization.
Zyxel Melen0 -
I cant use the AP. Its SSID is not visible by clients. LED is blinking green.
0 -
Could you enable Zyxel support access so I can check the AP status? Please reference the FAQ below to enable it.
Zyxel Melen0 -
ok. Done.
Name of organisation: Villa Bergengren
Name of site: Villa Bergengren
0 -
After checking the device diagnostic info, we found that this AP has a hardware issue. Please reference this FAQ to submit an RMA request.
Zyxel Melen0
Categories
- All Categories
- 415 Beta Program
- 2.4K Nebula
- 151 Nebula Ideas
- 98 Nebula Status and Incidents
- 5.7K Security
- 271 USG FLEX H Series
- 274 Security Ideas
- 1.4K Switch
- 74 Switch Ideas
- 1.1K Wireless
- 42 Wireless Ideas
- 6.4K Consumer Product
- 250 Service & License
- 389 News and Release
- 84 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.6K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 74 Security Highlight
