[ARRT Problem] The session is not connecting.

[XcessPak]

Everything works conversion works but session is not connecting.

[jumeder]

Hi @XcessPak, most likely the ARR network traffic is blocked by your firewall and/or router settings. Can you make sure the following ip/port ranges are allowed for TCP and UDP traffic: https://docs.microsoft.com/en-us/azure/remote-rendering/overview/system-requirements#network-firewall

[jakrams]

Closing this issue. Please reopen, if the problem persists.

[XcessPak]

Problem persists

Kind Regards, [Uzair Saeed] Chief Executive Officer XcessPak Suite#201, Safiya Chambers. 19-A Abbot Road Lahore. Cell: 0322-4680661, 042-36360999 Email: @., @.

Sent from my iPhone

On 25-Jul-2022, at 4:38 PM, Jan Krassnigg @.***> wrote:

 Closing this issue. Please reopen, if the problem persists.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[jakrams]

Did you investigate your firewall settings, as mentioned above? This kind of issue is quite common and it's usually due to firewalls.

[XcessPak]

Yes i have sir

Kind Regards, [Uzair Saeed] Chief Executive Officer XcessPak Suite#201, Safiya Chambers. 19-A Abbot Road Lahore. Cell: 0322-4680661, 042-36360999 Email: @., @.

Sent from my iPhone

On 25-Jul-2022, at 4:58 PM, Jan Krassnigg @.***> wrote:

 Did you investigate your firewall settings, as mentioned above? This kind of issue is quite common and it's usually due to firewalls.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[jakrams]

Looking at the telemetry for your session, we see that we get a connection request, but then no UDP packages arrive from your side.

Could you please double check that the necessary ports are allowed for UDP traffic (this is separate from TCP).

[XcessPak]

i have opnened the necessary port i.e 8266 on udp but problem persists.

[XcessPak]

XCESSPAK-MAIN.07-25-2022.19-17-14.etl.zip Please find attached WPA File

[jakrams]

@XcessPak good that you mentioned the port that you opened.

Please have another look at the documentation: https://docs.microsoft.com/en-us/azure/remote-rendering/overview/system-requirements#network-firewall

For SDK versions 0.1.76 and upwards, a different port range is necessary: 49152-65534

Port 8266 was only needed by very old ARR versions.

[XcessPak]

i have opened all the necessary ports for latest version but the problem still remains.

[jakrams]

These ports must be allowed to pass through not only on your PC, but also by all routers in your network. We have seen this issue many times before, and it was always some policy in the network that blocked this traffic. Especially in corporate environments router configurations are usually quite strict. As I mentioned above, we have looked at the telemetry for your session, and we don't see any UDP package arriving from your side.

[jakrams]

@XcessPak could you create another ETL trace, and record it over a longer duration? From what I see, you started the connection, and stopped it after roughly 5 seconds. ARR sessions usually take longer than that to boot up. To have more information to diagnose the issue, I would need a trace that covers the entire duration from the start until the "timeout reached" error message appears.

[XcessPak]

@jakrams here you go XCESSPAK-MAIN.08-01-2022.23-06-29.etl.zip .

[XcessPak]

we have only one router after computer on which we have also opened the ports.

[jakrams]

I'm trying to have a look at the trace, but WPA has trouble opening it:

Opening it with the mentioned /tti option also fails. It's possible that the file got corrupted at some point.

Could you do another recording and make sure that the file can be opened with Windows Performance Analyzer? Since the first trace could be opened correctly, it should generally work.

Sorry for the inconvenience.

Oh and another question: Have you tried the Unity Quickstart app ? It uses a completely different implementation for the connection logic. If that also fails, we can be certain that it is a general problem. If that works, though, we are certain that it is a bug in ARRT. That would help us a lot to diagnose the root cause.

[XcessPak]

yes i will do that certainly in evening. Regarding your second question yes i have tried every other unity app like quickstart tutorial and showcase app all are experiencing the same problem. even i built and installed the showcase desktop app but the problem persists. however in showcase app iam able to access my storage and see my uploaded models but not able to render it as this also says connection timeout.

[jakrams]

Makes sense. The storage and general connection to the ARR service mostly go through REST calls (HTTP) and regular TCP connections. Only once you start to connect to a rendering VM, we need to use UDP packages for the real-time video stream. At the moment I am very much convinced that it is an issue with your network configuration.

Please double and triple-check:

The full range of ports from 49152 to 65534 have to be open for outgoing (and best also for incoming) TCP and UDP traffic everywhere in your network:

• in your Windows Firewall
• in any additional virus scanners that may come with their own firewall
• in your office's WIFI router configuration
• in any secondary router that you may have in between
• and even by your ISP (very unlikely that this is blocked, though, and hard to check)

Also make sure that your firewall doesn't block any IP range that might be vital. See this table. So for example, if you want to connect to West US the IP address range 20.51.9.64/28 also must be open.

A trace can often tell us whether there is such an issue (or something else), but of course it doesn't tell us where along the route packages are blocked.

[jumeder]

Closing due to inactivity - Please reopen as required.

[XcessPak]

I have also opened these ports

Kind Regards, [Uzair Saeed] Chief Executive Officer XcessPak Suite#201, Safiya Chambers. 19-A Abbot Road Lahore. Cell: 0322-4680661, 042-36360999 Email: @., @.

Sent from my iPhone

On 26-Jul-2022, at 2:12 PM, Jan Krassnigg @.***> wrote:

 @XcessPak good that you mentioned the port that you opened.

Please have another look at the documentation: https://docs.microsoft.com/en-us/azure/remote-rendering/overview/system-requirements#network-firewall

For SDK versions 0.1.76 and upwards, a different port range is necessary: 49152-65534

Port 8266 was only needed by very old ARR versions.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[XcessPak]

Yes i have opened all the ports and checked it but still not working

Kind Regards, [Uzair Saeed] Chief Executive Officer XcessPak Suite#201, Safiya Chambers. 19-A Abbot Road Lahore. Cell: 0322-4680661, 042-36360999 Email: @., @.

Sent from my iPhone

On 15-Jul-2022, at 5:10 PM, Julian Meder @.***> wrote:

 Hi @XcessPak, most likely the ARR network traffic is blocked by your firewall and/or router settings. Can you make sure the following ip/port ranges are allowed for TCP and UDP traffic: https://docs.microsoft.com/en-us/azure/remote-rendering/overview/system-requirements#network-firewall

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[jakrams]

@XcessPak we can have another look at the telemetry, maybe we see something that we missed last time.

Could you please:

1. Start a client trace
2. Start a new session.
3. Wait for ARRT to report that it couldn't connect.
4. Stop the client trace.
5. And finally post the trace and the session ID here (maybe also a screenshot of ARRT's log).

Thanks.