Hello. Im having a very strange issue. On 2203 CU4, Im setting up a VDA but it doesnt register. But I look in the registry and the ListOfDDCs is filled out....But thats not the odd part, the odd part is that I do a wireshark and it never tries ANY communication on port 80 against the controller. Hell, there is no communication between the controller and the VDA

Please thread. Other messages were removed. Repost under a thread.

In addition to ListofDDCs, check the other three spots it could possibly be finding the broker setting. AD OU based discovery, GPO, personality.ini (if MCS)?

one thing to try is logon to a VDA and restart Citrix Desktop service. In the application log there will be attempts to register logged with the names of controllers its trying to register against

Using NTLM in BrokerAgent.exe.config? <endpointBehaviors> <behavior name="ControllerEndpointBehaviour"> <clientCredentials> <windows allowNtlm="true" allowedImpersonationLevel="Impersonation" /> </clientCredentials> </behavior> </endpointBehaviors>

Nothing there

What is the eventlog saying when restarting de Desktop Service?

Can't find any controller

and you can ping the controllers?

Yes

Can you post the exact event?

Can you try to run Citrix Health Assistant? Sometimes it can help figure out the cause of the problem.

As Dima mentioned, the event should list the name of the broker it is attempting to reach. Is that the correct controller? From the vda, can you

test-netconnection brokername.fqdn.etc -Port {the port you have configured for VDA}

?

what I suggest is logon to the machine after its already booted and not registered. Then under services restart Citrix Desktop service. In the Application Event Log look for Citrix Desktop Service event 1013. After this event there will be another one, usually a warning also for Citrix Desktop Service. In that warning you will see what controller its trying to register with if any.