This message was deleted.
# citrix-vad
s
This message was deleted.
m
Maybe it can be related to the connection path to the vda . If there is a cloud connector far away from vda ? users will go through. So were the vda are registered on ? Directly with rendez vous protocol or with a cloud connector then where the cloud connector is located.
n
Hi Mathiue, thanks for the feedback. it works fine when users are using the VDA (cloud) that is connected to the cloud via the connector, but does not when they VDA (Cloud) is connected to on premise delivery controllers.
m
You have to have in mind the connection path, in cloud user connect to the Citrix cloud "storefront" enumerate then go to the vda using the cloud connector ( as a Citrix gateway) then go to the vda. I guess you don't have an on premise Citrix gateway. So I think user still going through the cloud connector (in cloud) then take an VPN/express route to the vda located on prem. So. Long trip. It can explain. To solve add a cloud connector on premise
Sorry vda still on cloud ?
n
So the site where they are having the issue, the DDC and SF is on-premise but the VDA is in Azure.
The site where they don't have the issue, the VDA is in Azure, and the access layer and control plan are Citrix Cloud services.
m
In the non working scenario, user access to the on prem storefront?
Then enumerate there and access the vda?
If it is this scenario, you should investigate about the network route user take to reach the vda
From on prem to azure cloud
You probably go through a VPN or an express route and maybe the link is too small
n
in the Non-working scenerio they use on prem storefront
they are using express routes
m
You need to focus your attention around the bandwidth and this express route performance
j
So two different brokering points. Are the policies different across cloud/on-prem?