This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Connect 2.0 Automated Provisioning with Logon Disclaimer

I couldn't find if this was asked already or noted as a known issue.

If we have logon disclaimer enabled in firewall, the automated provisioning fails. Is this something that will be addressed in a future build? If not, can we get this updated in the help that in order for the auto provisioning to succeed you need to ensure x,y,x are enabled/disabled in the firewall.

Thanks,

John

This thread was automatically locked due to age.

Top Replies

emmosophos over 4 years ago in reply to axsom1 +2 suggested

Hello axsom1, Thank you I was able to replicate it. However talking with DEV, they mentioned this is a known issue. I will need to find the ID, and can I share it with you! Regards,

Parents

0 emmosophos over 4 years ago

Hello axsom1,

Thank you for contacting the Sophos Community!

What is the error you get when you are doing this?

Is this something that can be reproduced?

Regards,

Emmanuel (EmmoSophos)

Technical Team Lead, Global Community Support
Sophos Support Videos | Product Documentation | @SophosSupport | Sign up for SMS Alerts
If a post solves your question use the 'Verify Answer' link.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 emmosophos over 4 years ago

Hello axsom1,

Thank you for contacting the Sophos Community!

What is the error you get when you are doing this?

Is this something that can be reproduced?

Regards,

Emmanuel (EmmoSophos)

Technical Team Lead, Global Community Support
Sophos Support Videos | Product Documentation | @SophosSupport | Sign up for SMS Alerts
If a post solves your question use the 'Verify Answer' link.
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 axsom1 over 4 years ago in reply to emmosophos

emmosophos

Just get a "Failed to load connection" error. Nothing else logged on client.

To re-produce, enable logon disclaimers in the firewall.

Thanks,

John
Cancel
Vote Up 0 Vote Down

Cancel
0 emmosophos over 4 years ago in reply to axsom1

Hello axsom1,

Thank you I was able to replicate it.

However talking with DEV, they mentioned this is a known issue. I will need to find the ID, and can I share it with you!

Regards,

Emmanuel (EmmoSophos)

Technical Team Lead, Global Community Support
Sophos Support Videos | Product Documentation | @SophosSupport | Sign up for SMS Alerts
If a post solves your question use the 'Verify Answer' link.
Cancel
Vote Up +2 Vote Down

Cancel
0 emmosophos over 4 years ago in reply to axsom1

Hello axsom1,

DEV team provided the ID it is being fixed under NC-62813 scheduled to be fixed on 18.0 MR5 no ETA at the moment.

Regards,

Emmanuel (EmmoSophos)

Technical Team Lead, Global Community Support
Sophos Support Videos | Product Documentation | @SophosSupport | Sign up for SMS Alerts
If a post solves your question use the 'Verify Answer' link.
Cancel
Vote Up +1 Vote Down

Cancel