ICA Proxy does not work when Configured Workspace App is used.

[Bril licenses]

If i connect to the NS portal and launch an App with workspace, the connections are proxied by NS as it is expected to.

however, if I configure the Workspace App and launch the Virtual Apps from the Workspace later the ICA connections are not proxied by NS.

instead the client establishes a direct connection with storefront and XenApp servers on port .

 

this info can be verified from the Citrix Workspace connection center as well from Wireshark.

take a look at the attached file which shows difference in the connection properties.

1) when the app is launched after connected to the portal from a browser

2)when the app is launched directly from the start menu or from Workspace app one its is configured.

 

in both cases I am using workspace app.

Another interesting fact is that once I disable all the communication in firewall and only allow 443 to the NS gateway, it works as expected

[CarlStalhood]

What Internal Beacon is configured in StoreFront Console? If you want Workspace app to use Gateway, then make sure the Internal Beacon is not reachable by the Workspace app client.

[Bril licenses]

Hi Carl,

 

thanks you dear for the quick response.

the internal beacon is the storefront URL and it reachable from the clients.

 

does this also explain the reason that when i use the Workspace App to connect to Gateway URL it asks for Authentication twice.

once for the NS and one for the SF.

 

What is the impact of me not having anything in internal beacon?

[CarlStalhood]

You can set it to a fake address to force Workspace app users to use the Gateway.

[Bril licenses]

thanks Carl.. if you have any docs on SF internal Beacons and external beacons kindly share.

 

[CarlStalhood]

In StoreFront console, on the top right click Manage Beacons.

 

If the Internal Beacon is not reachable, then Workspace app will go to the Citrix Gateway instead of directly to StoreFront.