Not able to register AP to Sophos Central

Hi lordlamer 

Welcome to the Sophos Community!

Do the AP 55's have a "Sophos Central Ready" sticker on the bottom? Where are you getting stuck during the registration process?

Note the following articles:

• Sophos Central: Sophos Wireless network requirements
• Sophos Central Wireless: FAQ

Regards,

Hi Flo,

the AP do not have a sticker like this.

At registration time in the sophos central i got the error: "cannot register access point".

The AP itself gets an ip from dhcp and is pingable.

If i put the AP behind a sophos SG or XG firewall i can see that i was able to manage it with the SG or XG firewall. (but it did not manage the AP with the firewalls! they are not registered)

If i put it behind a normal router i am not able to register it to sophos central.

So are my AP 55's are not sophos central ready?

Frank

Hi Flo,

the AP do not have a sticker like this.

At registration time in the sophos central i got the error: "cannot register access point".

The AP itself gets an ip from dhcp and is pingable.

If i put the AP behind a sophos SG or XG firewall i can see that i was able to manage it with the SG or XG firewall. (but it did not manage the AP with the firewalls! they are not registered)

If i put it behind a normal router i am not able to register it to sophos central.

So are my AP 55's are not sophos central ready?

Frank

Hi lordlamer 

Apologies for this inconvenience.

Your AP's may not be on the latest AP firmware and therefore not currently compatible with Sophos Central.

I would advise to connect your AP's to your SG/XG Firewall, register them, and allow them to update to the latest AP firmware. After this is completed, delete them from the SG/XG Firewall, and try to register them once again to Sophos Central.

For reference:

• Sophos Wireless Access Points: LED power light flash indications

Regards,

Hi,

sophos support told me that they also have the problem and will give me feedback today.

So i will let you know the result.

Frank

Hi,

The latest cloud release which happened on 2nd March would have fixed the issue. 

Best Regards,

-Sathwik