We were able to find the solution. TCP 4172 traffic was being passed between the F5 and VMWare box but not establishing the UDP session. Only after modifying the access policy of right before the resource assign we put a variable assign of view.proxy_addr = expr {"public IP address"}.
So in turn we have it set-up so that we use two-factor authentication of NT-Login and OTP. That then opens the landing page to the VMWare Pools a user can access.
Thank you all for the valuable input in helping us find the root cause of our issue.