PS4 Published App

[snootalope]

So, here in Des Moines, we've had to activate an emergency disaster recovery location and had to move our farm to another location/subnet.

Since doing so, our home office location is having trouble reaching the farm/published desktop.

All the ica clients are set to "TCP/IP with HTTP" for locating the farm.

I have a DNS record set for host "ICA" and it points to our data collector for the farm. We can ping it by host name and IP address.

On the clients, if we try and log on to the published desktop with the locater name set to "ICA" it doesn't work, get a "published desktop cannot be located" message. However, we take ICA out of there and put the IP address of the ICA host, it works just fine.

I've adjusted the ICA keep alive and the "data collector responds to broadcasts" and neither seem to help. I don't get it, I'd think since they can ping the host ICA that it would work without using the IP address of the server...

Anyone got any ideas what I'm missing here?

 

[snootalope]

EDIT! - for whatever reason, I sat at one terminal and kept hitting connect and getting the error.. however, after getting the error about 5 times it finally brought up the login screen. Canceled out and tried it again, got the error 4 or 5 more times and then got the login screen again. ??? bug?

 

[Dublin73]

What are you using for clients... Regular PCs, thin clients? On a problem client, when you run...

PING ICA

what do you get for a reply?