> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/home-cloud-user-manual/appendix/ssid-trouble-shooting-naming-rules.md).

# SSID Troubleshooting Naming Rules

There is a management SSID that lets users know the current status when an access point connects to EnGenius Cloud. If an access point has lost its connection to the Internet but still receives power, it will broadcast a management service set identifier (SSID) that can be connected to for administrative tasks.

Connect to the default SSID by completing the following steps: 

1. Physically check that the access point has power. 
2. Check if a known default SSID is being broadcast.
3. If a management SSID is being broadcast, connect your device to it.
4. After connecting, check your gateway IP address to connect to the local status page. If you can't find the gateway IP, please make sure the access point is in NAT mode.

 

## Management SSIDS

**\<EnMGMTxxxx>-SSID\_name>-No\_Eth**

Cause: AP does not have Ethernet connection.

Solution: Check if the Ethernet cable is unplugged.

**\<EnMGMTxxxx>-No\_IP**

Cause: AP cannot get an IP address from DHCP server.

Solution: Check the AP's IP address configuration.

**\<EnMGMTxxxx>-IP\_Conflict**

Cause: AP’s IP address conflicts with another device's IP in the same network.

Solution: Check the AP's IP address configuration.

**\<EnMGMTxxxx>-Gateway\_ERR**

Cause: AP is unable to connect to its default gateway.

Solution: Check the AP's IP address configuration and connectivity to its default gateway.

**\<EnMGMTxxxx>-Proxy\_ERR**

Cause: AP could not access Internet through HTTP/HTTPS proxy.

Solution: Check the AP’s proxy configuration in miscellaneous settings.

**\<EnMGMTxxxx>-DNS\_ERR**

Cause: AP could not resolve the domain name from the DNS server.

Solution: Check the AP's IP address configuration.

**\<EnMGMTxxxx>-Cloud\_ERR**

Cause: Everything seems to be working, but a connection to EnGenius Cloud cannot be established.

Solution: Check EnGenius Cloud server status with EnGenius.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.engenius.ai/home-cloud-user-manual/appendix/ssid-trouble-shooting-naming-rules.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.