# Establishing a connection between Azure server and Airlink

**URL:** <https://forum.inductiveautomation.com/t/establishing-a-connection-between-azure-server-and-airlink/82432>\
**Category:** General Discussion\
**Created:** [November 28, 2023, 4:18pm UTC](https://forum.inductiveautomation.com/t/establishing-a-connection-between-azure-server-and-airlink/82432 "2023-11-28T16:18:04Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![bmeyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmeyers/32/37453_2.png) [@bmeyers](https://forum.inductiveautomation.com/u/bmeyers)\
**Post date:** [November 28, 2023, 5:06pm UTC](https://forum.inductiveautomation.com/t/establishing-a-connection-between-azure-server-and-airlink/82432/8 "2023-11-28T17:06:54Z")

</div>

I deleted the outbound firewall rule and changed the inbound firewall rule to UDP specific port 17342 and got the same error.

My airlink settings are shown below.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/a/ba17f4c0ba37c1c0178cc173f04f11efd4349051.png)

Is the ack happening on port 17341 as well? Your post in this thread seems to confirm it is happening on the 17341 port so I should swap my outbound firewall rule to 17341.

> [@SMS notification setup](https://forum.inductiveautomation.com/t/sms-notification-setup/11192/2):
>
> This message is telling you that the ACK message the Raven XE sends back to the gateway was not received. This happens on UDP 17341 by default. Your cloud-based setup may or may not make this impossible.

---

_[View the full topic](https://forum.inductiveautomation.com/t/establishing-a-connection-between-azure-server-and-airlink/82432)._