[Enable SSL on VDA with NetScaler]

Anjanib,

 

The VDA Event Logs show nothing. They are not receiving any incoming connections, so there is nothing to log.

 

All the traffic stops at the NetScaler and never makes it to the VDA.

 

Yes, I have reviewed the link and can confirm we have SSL setup correctly on the VDA and it's listening on port 443. 

[Enable SSL on VDA with NetScaler]

Update.

 

I corrected the server's certificate to the full FQDN. Same result.

 

Is there some way I can see what the NetScaler is doing while the Receiver is just sitting at the Connecting... prompt? My traces for the destination IP are empty. 

[Enable SSL on VDA with NetScaler]

1 hour ago, Carl Stalhood1709151912 said:

Is NetScaler able to resolve internal DNS?

Yes. From the shell it resolves the VDA FQDN and netbios name. There is also a DNS server configured for the gateway if that matters. 

 

One note on the server's certificate.. It lists only the netbios name (host name) of the VDA as part of a list of alternate names. Not the FQDN. I'm not sure what name is being sent as the target though.

 

I would think this would cause an SSL error if anything but I'm getting no feedback. 

[Enable SSL on VDA with NetScaler]

XenApp 7.15 LTSR

 

I've followed the procedures to enable SSL on my Server 2016 VDA, but when I try to access it externally via NetScaler Gateway, the connection fails (times out) without an error code.

 

443 is open from the NetScaler SNIP to the VDA. As far as I can tell, the connection isn't even being initiated. There is no traffic at all from the NetScaler to the VDA, at least from the NetScaler's perspective. I haven't run Wireshark on the VDA yet. I find this odd because I thought I'd at least see some traffic attempting to connect. It's like the NetScaler doesn't know where to go.

 

Changing the Delivery Group setting back to HdxSslEnabled = False allows it to work again over typical port 2598.

 

I haven't seen any documentation requiring additional NetScaler Gateway configuration to get this to work. So what am I missing?

 

Thanks.

[Occasionally get "Cannot start app" when launching]

Apoorvg,

 

Thanks for the response. We do use "dots and blanks" in our Delivery Controller display names, but this has never been a problem. We are on StoreFront 3.8 so that issue may be resolved in later versions (you mention 3.5). The issue we are seeing with users being unable to launch an app is very rare, random, and short lived. The user can launch the app immediately after getting the error.

 

The other link for CTX134190 seems to fit the problem, but I'm talking about XenApp server VDA not desktops. Power management IS being used, but the Power State is always "Unknown" because the VM is located inside a VMware vApp container. Apparently this is a known issue. But again, it hasn't caused any harm so far since servers don't reboot after use.

 

Any other ideas?

 

Thanks.

[Occasionally get "Cannot start app" when launching]

Occasionally a user will get the popup in StoreFront 3.8 Cannot start app "name" when launching an app. In the Event Log it says

Citrix Store Service Event ID 0

No available resource found for user * when accessing desktop group <app name>. ... 

 

Event ID 28

Failed to launch the resource <Site name.app name> using the Citrix XML Service at address <delivery controller 2>. The XML service returned error: 'no-available-workstation'.

 

The responding delivery controller has a similar event Citrix Broker Service Event ID 1101 "The Citrix Broker Service failed to broker a connection for user * to resource <app name>. The Citrix Broker Service cannot find any available virtual machines."

 

All servers in the group are up and registered. No connectivity issues that I'm aware of. Nothing in the server logs except possibly a connection failure event around the same time. Other users are already logged in and working on all servers. Subsequent launch attempts are immediately successful. The error seems to appear randomly maybe twice a day. Not tied to a specific user or workstation.

 

What other factors could be causing this? We use smart card authentication and have a timeout on the StoreFront. I was wondering if the user was possibly trying to launch from a stale page, but I don't know if it would make it that far in that case.

 

Am I missing something?

 

Thank you.

[Load Balance Windows 2012 R2 Print Servers]

So I have been able to map to a shared printer through the Netscaler and I'm able to print.

 

However, whenever I disable the server that I was connected to when I originally mapped the printer, it does not fail over. Instead I get an error saying make sure that the printer is connected to the network.

 

I can see that the connection correctly failed to the other server because I can get to other resources by the VIP name. But for some reason the mapped printer is not picking up on that.

 

Any ideas?

[Load Balance Windows 2012 R2 Print Servers]

Mark, I'm curious to hear your results.

Please keep me in the loop.

Thanks!

[Load Balance Windows 2012 R2 Print Servers]

Has anyone been able to get this working yet?

 

I'm also looking for a Netscaler load balancing solution for Server 2012 R2 Print Servers.

 

Is there a trick to setting up the shared printers?

 

What ports do you balance?

 

Persistence?

 

Thanks.

[The VDI is not available - The specified storage repository scan failed.]

You have to find the VDIs attached to the VM. Forget those VDIs. Rescan the SR. Reattach those VDIs.

!!! SCAN THE SR FIRST TO MAKE SURE IT DOES NOT ERROR !!!

Go to the Xenserver master host.

Find the disks attached to the VM.
xe vm-disk-list uuid=<VM uuid>

Forget the VDIs. You will see them disappear from the SR. Do not do this unless you can successfully rescan the SR without error.
xe vdi-forget uuid=<uuid of VDI>

Go to the SR and click the Rescan button on the Storage tab.

The VDIs should reappear.

Reattach them to the VM. Boot the VM.