![]() Policy is in testing phase, so everything between the GP zone and trusted zone is allowed.Name resolution is fine (both netbios and fqdn names). All related Citrix servers (portal, xenapp servers) are all reachable over GP.That's the file the Citrix client uses to find what resources are available. I can actually download the Citrix config.xml file over GP VPN. ![]() The only difference with GP is that GP clients terminate at the firewall, so traffic has an extra route to the Citrix servers. FAS administration console, using the console user’s account. Using an old style Windows VPN that terminates on one of our DC's, everything is fine. To enable SSO for workspaces with FAS, the FAS administration console and FAS service access the following addresses using the console user’s account and Network Service account, respectively.On the internal LAN everything is fine.I'm starting to think this is a Globalprotect issue, because: I'm getting the error "citrix receiver could not contact the server. The one thing that does not seem to be working is the connection Citrix Receiver (PNAgent legacy version 13.3) makes to our internal Citrix Web Interface / Services site. Look for the one that has citrix in the description, its an updater service. While in task manager, go to the services tab and sort it by 'description'. Open task manager, and end any citrix tasks. I seem to have Globalprotect working fine for access to any internal resource. The pesky Citrix Workspace Updater Service is what got originally in the way.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |